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
This distro is going EoL in July, but fix the test anyways for better future-proofing.
What happens is that the task fails to execute because there is no working directory support on Amazon Linux 2, so the build fails. However, in that case the background task which waits for the sentinel file to be written will run forever. Ensure that we cancel the background task in cases where the build has completed.
// Kick the target callbacks so that our target-level diagnostics get emitted in the right context in the case of an early build failure due to task construction errors.
/// - status: Overall build operation status to override the build result with. This can be used when the operation was aborted (the build could not run to completion, e.g. due to discovery of a cycle) or cancelled and wants to propagate that status regardless of the status of the individual build tasks in the underlying (llbuild) build system. `nil` will use the status based on the result status of the tasks in the underlying llbuild build system.
54
54
/// - delegate: The task output delegate provided by the \see buildStarted() method.
// Helper method to emit information to the CAPTURED_BUILD_INFO_DIR. This is mainly to be able to gracefully return after emitting a warning if something goes wrong, because not being able to emit this info is typically not serious enough to want to abort the whole build.
@@ -367,8 +368,9 @@ package final class BuildOperation: BuildSystemOperation {
367
368
368
369
// If task construction had errors, fail the build immediately, unless `continueBuildingAfterErrors` is set.
369
370
if !request.continueBuildingAfterErrors && buildDescription.hadErrors {
0 commit comments