Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Show analyze_outcomes step on the BlueOcean view #127

Open
gilles-peskine-arm opened this issue Oct 4, 2023 · 0 comments · May be fixed by #142
Open

Show analyze_outcomes step on the BlueOcean view #127

gilles-peskine-arm opened this issue Oct 4, 2023 · 0 comments · May be fixed by #142
Labels
enhancement New feature or request size-s Estimated task size: small (~2d)
Projects
EPICs for Mbed TLS

Comments

@gilles-peskine-arm
Copy link
Contributor

On Jenkins, on the BlueOcean view, the list of sub-steps of the result-analysis appears as a long list of “Restore files previously stashed”. Those are boring steps we don't care about. There's more than 100 of them, and BlueOcean truncates the list at 100. This causes the one interesting sub-step of result-analysis to be hidden, namely, the one that runs analyze_outcomes.py. Thus, when analyze_outcomes.py fails, this causes a failure of result-analysis that cannot be explained if you only look at BlueOcean and not the classic pipeline view.

Definition of done for this issue: in the BlueOcean view, the report of result-analysis makes the interesting steps visible (both on success and on failure). Whether the individual “Restore files previously stashed” steps are visible at all doesn't matter since those are very unlikely to matter.
@gilles-peskine-arm gilles-peskine-arm added enhancement New feature or request size-s Estimated task size: small (~2d) labels Oct 4, 2023
gilles-peskine-arm added a commit to gilles-peskine-arm/mbedtls-test that referenced this issue Nov 27, 2023
@gilles-peskine-arm
Put the long unstash sequence into its own stage
036cc32 
This improves reporting in BlueOcean, which has a limit of 100 steps.
The outcome stage is >100 boring unstash steps followed by an
interesting step (running analyze_outcomes.py). Due to this long
sequence, the interesting step was not visible on BlueOcean. Fix this
by making unstashes a separate nested stage.

Fix Mbed-TLS#127.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
@gilles-peskine-arm gilles-peskine-arm linked a pull request Nov 27, 2023 that will close this issue
Open
@gilles-peskine-arm gilles-peskine-arm added this to Test cases not executed in EPICs for Mbed TLS May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request size-s Estimated task size: small (~2d)
Projects
EPICs for Mbed TLS
Test cases not executed
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix result analysis reporting Mbed-TLS/mbedtls-test
1 participant
@gilles-peskine-arm