Skip to content

Conversation

@strtgbb
Copy link
Collaborator

@strtgbb strtgbb commented Nov 3, 2025

Changelog category (leave one):

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

Tasks

  • Address code smell in report generation
  • Fix crossout message matching when an integration log has multiple fails
  • Switch broken_tests format from json to yaml
  • Support pattern matching on test names
  • Support matching multiple possible fail messages
  • Exclude all time related sanitizer fails, while including all sanitizer trap related fails
  • Update report to read the new config
  • Tweak report path so that runs on the same commit do not overwrite each other

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:

  • Fast test
  • Integration Tests
  • Stateless tests
  • Stateful tests
  • Performance tests
  • All with ASAN
  • All with TSAN
  • All with MSAN
  • All with UBSAN
  • All with Coverage
  • All with Aarch64
  • All Regression
  • Disable CI Cache

Regression jobs to run:

  • Fast suites (mostly <1h)
  • Aggregate Functions (2h)
  • Alter (1.5h)
  • Benchmark (30m)
  • ClickHouse Keeper (1h)
  • Iceberg (2h)
  • LDAP (1h)
  • Parquet (1.5h)
  • RBAC (1.5h)
  • SSL Server (1h)
  • S3 (2h)
  • Tiered Storage (2h)

@github-actions
Copy link

github-actions bot commented Nov 3, 2025

Workflow [PR], commit [00487dd]

@strtgbb strtgbb added cicd Improvements and fixes to the CICD process antalya-25.8 labels Nov 3, 2025
@strtgbb strtgbb force-pushed the crossout_rework branch 2 times, most recently from 7d13673 to f5d8e68 Compare November 4, 2025 14:44
@strtgbb
Copy link
Collaborator Author

strtgbb commented Nov 4, 2025

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.
To fix the report, the tests would need to produce a unified, machine-readable record of crossouts or enable the text_context_raw field in the database..

@strtgbb strtgbb force-pushed the crossout_rework branch 4 times, most recently from bc05ec3 to ab9b0b2 Compare November 6, 2025 14:46
@strtgbb strtgbb marked this pull request as ready for review November 6, 2025 14:48
@strtgbb strtgbb force-pushed the crossout_rework branch 2 times, most recently from fda8856 to 1aa8304 Compare November 6, 2025 22:52
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

antalya-25.8 cicd Improvements and fixes to the CICD process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants