-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Reveal magic, parallel system-testing and system-testing simplification #1780
Conversation
0806628
to
1642549
Compare
DO NOT MERGE: There is still a bug in cirrus, I am in contact with their engineering and working on a fix. They're typically really fast with these things, expect resolution today / early next week. |
PASSES all test. |
@rhatdan thanks for taking a look. There are some not-so-obvious systemic bugs I need to work out. Hence the WIP and DO NOT MERGE. There's no better way to beat on the CI system than from w/in a PR, so there's a bunch of duct-tape in here temporarily. I'll strip all that out when the code is more solid (it's almost there). |
Update: Cirrus bug has been fixed, this PR is ready to go, PTAL. (Assuming happy tests) |
Okay, this is working as designed: Having the magic words in the description caused this run to happen: https://cirrus-ci.com/task/5163575452631040 <-- Failed due to missing system tests (we know this). |
Previously, several magic strings were in place to affect cirrus-ci operations. Two were buried within scripts. One to optionally execute system-tests within a PR. Another to avoid re-building cache-images upon every merge. Move these magic strings out into the open, buy locating their logic up-front in the ``.cirrus.yml`` file. This improves readability and reduces surprise/astonishment at runtime. Signed-off-by: Chris Evich <[email protected]>
Previously it was required to call the verify, unit, and integration scripts in order to build/install dependencies, and libpod. This wastes time during the (optional) system-testing, since the actual unit/integration testing is also happening in parallel. Consolidate only the distribution-specific build steps into the system-testing script. This way, only the required steps are performed in their respective (parallel) tasks. Signed-off-by: Chris Evich <[email protected]>
***CIRRUS: REBUILD IMAGES*** Signed-off-by: Chris Evich <[email protected]>
Removed magic string, rebased and |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Nice work @cevich !
LGTM too |
LGTM |
/lgtm |
Previously, several magic strings were in place to affect cirrus-ci
operations. Two were buried within scripts. One to optionally
execute system-tests within a PR. Another to avoid re-building
cache-images upon every merge.
Move these magic strings out into the open, buy locating their
logic up-front in the
.cirrus.yml
file. This improvesreadability and reduces surprise/astonishment at runtime.
Previously it was required to call the verify, unit, and integration
scripts in order to build/install dependencies, and libpod. This
wastes time during the (optional) system-testing, since the
actual unit/integration testing is also happening in parallel.
Consolidate only the distribution-specific build steps into the
system-testing script. This way, only the required steps are performed
in their respective (parallel) tasks.