Skip to content

[IMP] runbot: update test tags version bounds on manual parse#1399

Open
d-fence wants to merge 1 commit into
19.0from
19.0-autotags-update-moc
Open

[IMP] runbot: update test tags version bounds on manual parse#1399
d-fence wants to merge 1 commit into
19.0from
19.0-autotags-update-moc

Conversation

@d-fence
Copy link
Copy Markdown
Contributor

@d-fence d-fence commented May 6, 2026

When parsing build errors, it may happen that the error appears in a version lower or higher than the current test tags bounds.

With this commit, when a build error log is manually parsed (via the web interface or the server action), the min and max version bounds of the test tags are updated accordingly to include the new builds versions.

@C3POdoo C3POdoo requested a review from a team May 6, 2026 13:59
@d-fence d-fence requested a review from Xavier-Do May 6, 2026 14:09
Comment thread runbot/models/build_error.py Outdated
if build_error_content.error_id and build_error_content.error_id.test_tags:
errors_to_update |= build_error_content.error_id
for error in errors_to_update:
error._onchange_test_tags()
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The onchange is not safe in this case, because it could actually make the range of covered version slower.

Lets imagine I scan in 19.0, the disable from 18.0 to master

If I have a n error in master and scan it, it will change the min from 18 to 19, renabling the test in 18.0.

Note that the same problem could occur when modifying a test tag

It would be safer to either have a custom logic there, or take the current tags_min_version_id and tags_max_version_id in the onchange.

When parsing build errors, it may happen that the error appears in a
version lower or higher than the current test tags bounds.

With this commit, when a build error log is manually parsed (via the
web interface or the server action), the min and max version bounds
of the test tags are updated accordingly to include the new builds
versions.
@d-fence d-fence force-pushed the 19.0-autotags-update-moc branch from 7ea8a8f to eee5c94 Compare May 13, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants