-
Notifications
You must be signed in to change notification settings - Fork 30
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
fix(ci): run at least compilation and unit tests on few fixed jug_xl #1136
Conversation
The idea here would be for the default platform in the workflow_dispatch to point to the oldest tested environment (e.g. right now jug_xl:23.12-alpha) with at least the liatest tested environment (jug_xl:nightly) included in the build job matrix. |
69ac9bd
to
74d6b70
Compare
@veprbl This now runs at least compilation and unit tests on jug_xl:23.12-alpha in addition to the usual nightly. It's not quite a full systems test, but I think most regressions would be of the kind that lead to failed compilation, not regressions that still compile fine and pass unit tests but somehow don't run beyond that. |
"API rate limit exceeded" and it is not recognizing the renamed jobs of course. If approved, I'll go ahead and change the branch protection settings to use the new names. |
77306d0
to
ce80ffd
Compare
Capybara summary for PR 1136 |
ce80ffd
to
b76b917
Compare
b76b917
to
08d9388
Compare
08d9388
to
2ed7ed6
Compare
2ed7ed6
to
dfd6635
Compare
This reverts commit 0ba6b55.
Co-authored-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
…v.platform/release
bcd3e5e
to
d5d2e67
Compare
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.
Still good
…1136) ### Briefly, what does this PR introduce? This changes the CI philosophy to run the compilation and unit testing on an expanded set of platform versions. It does this for the clang release versions, since fastest. It separates the default CI platform (set as input on workflow_dispatch) from the explicit platform versions sets in the build job matrix (there may be overlap, even by default). ### What kind of change does this PR introduce? - [x] Bug fix (issue: need to test on more versions/platforms; have tests on stable platform by default) - [ ] New feature (issue #__) - [ ] Documentation update - [ ] Other: __ ### Please check if this PR fulfills the following: - [ ] Tests for the changes have been added - [ ] Documentation has been added / updated - [ ] Changes have been communicated to collaborators ### Does this PR introduce breaking changes? What changes might users need to make to their code? No. ### Does this PR change default behavior? No. --------- Co-authored-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
Briefly, what does this PR introduce?
This changes the CI philosophy to run the compilation and unit testing on an expanded set of platform versions. It does this for the clang release versions, since fastest. It separates the default CI platform (set as input on workflow_dispatch) from the explicit platform versions sets in the build job matrix (there may be overlap, even by default).
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No.
Does this PR change default behavior?
No.