Commit id tracking suboptimal.

Bug #1510230 reported by Robert Bruce Park on 2015-10-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CI Train [cu2d]
Fix Released
Robert Bruce Park

Bug Description

Consider this scenario:

1. User runs build job on a silo.

2. Train records commit ids on all MPs in the silo.

3. Source package creation fails due to merge conflict.

4. User resolves conflict, rebuilds silo.

5. Train says "no new commits, skipping" even though the package was never actually built.

I guess the commit ids are being written to disk too soon, would be better to move that until later, maybe during upload phase or so.

Robert Bruce Park (robru) wrote :

OK, i made the train write the revid after successful merging, so this should be resolved.

Changed in cupstream2distro:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers