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
Now that we have a step that runs before tuxsuite (check_cache), we should explore adding another step that checks that any patches we need to apply for that build will apply cleanly. This would make patch application failures appear more obvious and avoid blowing up tuxsuite.
The text was updated successfully, but these errors were encountered:
nathanchance
added a commit
to nathanchance/continuous-integration2
that referenced
this issue
Jan 2, 2025
There is no point in spinning up TuxSuite for a build if any patches
that we need to apply are going to fail to do so. At the beginning of a
build, check if the patches apply to the current repository and
reference. This is done by downloading a tarball of the source, running
'git init' and committing the files, then finally running
'git quiltimport' to make sure that that patches still apply. It would
be simpler to use 'git clone --depth=1' but cloning can be expensive
on the server side and these jobs may run at the same time.
Closes: ClangBuiltLinux#796
Signed-off-by: Nathan Chancellor <[email protected]>
Now that we have a step that runs before
tuxsuite
(check_cache
), we should explore adding another step that checks that any patches we need to apply for that build will apply cleanly. This would make patch application failures appear more obvious and avoid blowing uptuxsuite
.The text was updated successfully, but these errors were encountered: