You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm doing both qisrc checkout and qisrc sync because the manifest branch may change from one build to another.
When switching manifest branch, qisrc checkout may need to move a repo around.
I noticed that in such a case, it omits to update it. As a consequence, the repo stays on the wrong branch (typically another release branch), and my build fails.
The problem lies in the compute_repo_diff() function, which only adda a repo to the to_update list if it does not move.
This bug is quite bad since qibuild will never recover: running qisrc checkout && qisrc sync again won't help.
If you go and git checkout the repo to the proper branch yourself, then qisrc checkout && qisrc sync will checkout the wrong branch again.
It appears the wrong branch name persists in ${worktree_path}/.qi/git.xml
The moving rep is basicawareness. It should be on master.
I have a buildfarm that does reset the worktree to some branch then builds and runs the tests.
The reset part is done with:
I'm doing both qisrc checkout and qisrc sync because the manifest branch may change from one build to another.
When switching manifest branch, qisrc checkout may need to move a repo around.
I noticed that in such a case, it omits to update it. As a consequence, the repo stays on the wrong branch (typically another release branch), and my build fails.
The problem lies in the
compute_repo_diff()
function, which only adda a repo to theto_update
list if it does not move.This bug is quite bad since qibuild will never recover: running qisrc checkout && qisrc sync again won't help.
If you go and git checkout the repo to the proper branch yourself, then qisrc checkout && qisrc sync will checkout the wrong branch again.
It appears the wrong branch name persists in ${worktree_path}/.qi/git.xml
The moving rep is basicawareness. It should be on master.
The text was updated successfully, but these errors were encountered: