Make ruby-core job use a non moving target #8435
Merged
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.
What was the end-user or developer problem that led to this PR?
We originally added this in order to prevent us when making changes to our test setup to break the way ruby-core runs our tests.
However, the way it works now, it breaks too often due to changes in ruby/ruby because of running against a moving unstable target. We still want to find about that kind of breakage, but not on every PR. Our daily jobs achieve that.
What is your fix for the problem, implemented in this PR?
This commit changes the ruby-core job to run against a fixed target (the tag for the latest ruby release), which should still catch the kind of issue we intend to catch here.
Make sure the following tasks are checked