fix: do not constrain resources in remote jobs #87
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.
Previously, the jobs resource usage was used to define global resource constraints for the remote job. This is (a) not necessary, since the remote job comes with its own resources anyway, and (b) can cause errors in case of pipe groups, where the consuming job does not yet have e.g. a defined memory usage if the memory is determined at runtime, such that it cannot be considered when calculating the resource constraints for the remote job.