-
Notifications
You must be signed in to change notification settings - Fork 7
Crossout rework #1119
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
base: antalya-25.8
Are you sure you want to change the base?
Crossout rework #1119
Conversation
7d13673 to
f5d8e68
Compare
|
A major issue with the new implementation is that since crossout reason is not uploaded to the database, and a test fail can match multiple rules, the report cannot be 100% certain of the reason a test was crossed out. The crossout system does log the reason, it's appended to the test logs for stateless, and for integration tests a dedicated log file is written. |
bc05ec3 to
ab9b0b2
Compare
fda8856 to
1aa8304
Compare
make sure to use short test name with log extraction
update report to handle new known fails format allow message to be optional again fix broken tests report when there are no fails fixes and debug logging more debugging more debugging and fix not_message handling more debug and fix report fix broken tests report when check_types unspecified support opening logs with invalid chars in extract_fail_logs debugging missing integration tests logs fix get_log_paths returning compressed files use regex to match sanitizer timeouts
update broken_tests.yaml
288619a to
00487dd
Compare
Changelog category (leave one):
Tasks
Note that pattern matching on test names makes it more difficult to exclude tests that upstream has designated as BROKEN from the report. However, at this time, there is only one such upstream test.
CI/CD Options
Exclude tests:
Regression jobs to run: