Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@catalinaperalta reported an issue with
Analyze
unexpectedly failing due to inability to find the relevant artifact. The source turned out to be Build_Extended failing.The reason behind Build_Extended failing doesn't actually matter. What matters is that due to the job condition governing
Analyze
, we would runAnalyze
even ifBuild_Extended
(its sole dependency) failed! IfBuild_Extended
fails, then the artifactpackages_extended
, whichAnalyze
REQUIRES to be present, won't exist named aspackages_extended
! If the artifact doesn't exist, it can't be downloaded inAnalyze
, and we get failures that complain about being unable to locate the wheel.Simply change the condition to
succeeded()
, which will delay the job run untilBuild_Extended
passes.