-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick commits from master to managed-service branch #1529
base: managed-services
Are you sure you want to change the base?
Conversation
Update to support luarocks v3 and also refactor Dockerfile to install luarocks and lua-rover directly from source
By default we run the prove task based on the number of available CPU cores. The nprocs test will return the number of available CPU cores in the docker executor VM, however the medium resource class only has access to 3 CPUs. So the prove task will always spawn more workers than the number of available CPU cores, which then causes the CPU to max out during the test and cause random errors.
3ea813d
to
39ebef8
Compare
This is targetting |
My bad, it's targeting |
This is doing far more than backport #1528, intended? |
This is tricky, when we decided to release the new managed-services release, I intentionally just fast forwarded right before all the konflux and luarock/lua-rover changes. But since then we have to
If you are ok with having the CI failing on this branch then I will just cherry-pick the fix alone. Otherwise we need to have back-port everything else except Konflux. WDTY? |
you add those changes to the description and reword the title and I will accept it and review. Deal? |
What
Port the following PR(s) to manged service branch
#1513
#1516
#1518
#1519
#1520
#1524
#1528
This is done mainly to fix issue reported in #1528. Cherry-pick commit instead of fast-foward due to concern raised here #1522 (review)