Skip to content

Syncing from upstream odoo/runbot (19.0-fix-restore-xdo) - #1152

Open
bt-admin wants to merge 6 commits into
brain-tec:19.0-fix-restore-xdofrom
odoo:19.0-fix-restore-xdo
Open

Syncing from upstream odoo/runbot (19.0-fix-restore-xdo)#1152
bt-admin wants to merge 6 commits into
brain-tec:19.0-fix-restore-xdofrom
odoo:19.0-fix-restore-xdo

Conversation

@bt-admin

Copy link
Copy Markdown

bt_gitbot

bepro-odoo and others added 5 commits August 12, 2026 08:22
The start_after / start_before relations only works for build in success.

This was the intended behaviour since the minimal check should prevent
other builds from running, but in some case we want a check to run even
if the dependency failed. For example, we want to run the generation of
a specific test report even if the build failed.

This will be used to generate the coverage of failed builds as well as
the statistics.
When dump_trigger_id is given we expect to stay in the restore batch
case. The error management being in the wrong place, it was possible for
a restore to fallback on the parent when it was not intended.

Also fixes the case where a base_reference_batch_id (base batch) is not
set (base batch)
@Xavier-Do
Xavier-Do force-pushed the 19.0-fix-restore-xdo branch from 7fec1a9 to f1574fa Compare August 13, 2026 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants