Db/push to regressions latest #621
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…test and previous
…sqllogictest_tester job
…ns.sh}: Remove unneeded gunk
…ssions.sh}: Update regressions-tip-latest whenever we run the release job
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
idea here is to maintain two shallow branches used to help with the
sqllogictest-testerjenkins job. whenever we run thereleasesjob, we update branchregressions-tip-latestto the latest release results and also updateregressions-tip-previousto be whatregressions-tip-latestwas...Decided to have two branches since we may not always get fixing a regression right away, and this gives us a little time to do so...