Remote execution is only enabled globally if environments aren't used at all #17135
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.
It's now possible to use environments generally, but for the current env target to be set to None, thanks to #16983.
This was resulting in faulty logic that we were treating the
--remote-execution
flag as a global switch for remoting, when really if environment targets are used at all, then we should only use remoting when aremote_environment
target is active.[ci skip-rust]
[ci skip-build-wheels]