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 could be a little tricky. For child builds the model is that we do not look at dep status when starting the build. I will work on some test cases for this, but probably not this sprint!
Fixes#11428.
It is possible for a dep to have child builds, and vice-versa. When
a dep has child builds, we want to avoid those child builds being run
twice in the scenario that the dep is also referred to directly (though
the presence of complex dependencies like this may be a red flag for our
dependency map, but that's a separate problem...)
This test does not currently fix the problem, but it starts the
exploration process.
For the
debug-deps
test, it would be nice to have an action that verifies that a child action is skipped if it was already run due to dependency mode.So, a setup like...
parent:
Of course, a more likely case is where the first 'dependency' there is triggered by a different dependency that happens to depend on
dep/child
.Originally posted by @jahorton in #11410 (review)
The text was updated successfully, but these errors were encountered: