Skip to content

Conversation

strtgbb
Copy link
Collaborator

@strtgbb strtgbb commented May 2, 2025

Changelog category (leave one):

  • CI Fix or Improvement (changelog entry is not required)

Changes:

  • When run against a PR workflow the report now has a table "New Fails in PR"
  • Build report is now linked at the top of the workflow report
  • If a previously failed test passes on rerun, it will no longer show as failed in the report
  • Improved line wrapping of test names in report when in a narrow window
  • Non-PR report now states the branch
  • Grype scan step summaries now have the full image name
  • RunConfig prints a step summary with the report location, a preview becomes available after the first test job completes
  • Many more unstable and broken tests added to broken_tests.json
  • All integration tests now have 8 batches, previously some test were not running due to hitting timeouts
  • Skipped integration tests are properly detected instead of being marked ERROR
  • Broken test marking now works in integration flaky check
  • Fixed bug in broken marking broken integration tests
  • Stress tests have azurite re-enabled and threads reduced
  • Several failing integration tests now have reasonable timeouts

Issues:

  • This is untested with regression fails, but they should be supported.
  • Some fails that should be marked as broken seem to not be, and end up in the table. Fixed.

Skip Jobs

  • Skip All Regression

@strtgbb strtgbb force-pushed the report_new_fails_in_pr branch from 2b83a9c to 2582a4b Compare May 5, 2025 13:37
@strtgbb strtgbb changed the title Report Add Table New Fails in PR Report Add Table New Fails in PR & Fix Tests Not Correctly Marked as Broken May 6, 2025
@strtgbb strtgbb requested review from Enmk and MyroTk May 9, 2025 02:45
@Enmk Enmk merged commit 0217bf4 into antalya May 12, 2025
167 of 170 checks passed
strtgbb added a commit that referenced this pull request May 12, 2025
Report Add Table New Fails in PR & Fix Tests Not Correctly Marked as Broken
@strtgbb strtgbb added the cicd Improvements and fixes to the CICD process label May 23, 2025
@strtgbb strtgbb deleted the report_new_fails_in_pr branch June 6, 2025 13:56
Enmk added a commit that referenced this pull request Aug 6, 2025
By reverting those back to upstream/25.6 variant.
Those are related to the features that were not merged yet and hence fail:
 - integration/test_s3_assume_role/test.py - was added by #688
 - integration/test_mask_sensitive_info/test.py - was added by #675
 - integration/test_s3_cache_locality/test.py - was added by #763
Enmk added a commit that referenced this pull request Aug 6, 2025
By reverting those back to upstream/25.6 variant.
Those are related to the features that were not merged yet and hence fail:
 - integration/test_s3_assume_role/test.py - was added by #688
 - integration/test_mask_sensitive_info/test.py - was added by #675
 - integration/test_s3_cache_locality/test.py - was added by #763
Enmk added a commit that referenced this pull request Aug 6, 2025
By reverting those back to upstream/25.6 variant.
Those are related to the features that were not merged yet and hence fail:
 - integration/test_s3_assume_role/test.py - was added by #688
 - integration/test_mask_sensitive_info/test.py - was added by #675
 - integration/test_s3_cache_locality/test.py - was added by #763
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cicd Improvements and fixes to the CICD process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants