Fix result analysis reporting #142
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gilles-peskine-arm
added
bug
gilles-peskine-arm
changed the title
No behavior change. Signed-off-by: Gilles Peskine <[email protected]>
gilles-peskine-arm
force-pushed
the
dev/gilles-peskine-arm/result-analysis-reporting
branch
3 times, most recently
from
9bc7fb5
to
25a4dea
Compare
For visibility on BlueOcean, ensure that the unstash steps are in
their own stage. This way they don't hide other steps despite
BlueOcean truncating the step list at 100 elements.
Nest stages { parallel { stages {} } } even though there is a single
element in the parallel dispatch, because BlueOcean doesn't separate
nested sequential stages inside of sequential staging.
Signed-off-by: Gilles Peskine <[email protected]>
gilles-peskine-arm
force-pushed
the
dev/gilles-peskine-arm/result-analysis-reporting
branch
from
25a4dea
to
0493b31
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change the place where we run result analysis. The logic is now shared between PR testing and release testing, so there's less repeated code. Result analysis is now covered by the same reporting of results on GitHub or over email, so this fixes #120.
Also tweak the staging of result analysis to fix #127.
CI runs on ec59ea0:
development, good: internaldevelopment, good: internaldevelopment, test failures: internaldevelopment, tests pass but outcome analysis fails: TODOdevelopment, good: OpenCIdevelopment, test failures:OpenCIdevelopment, tests pass but outcome analysis fails: TODO