Reset the db before runs #305
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
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.
We were seeing this error:
The issue was related to the renaming of a table
The issue was seen when Pixel ran
reference, then rantest, then ranreferenceagain subsequentlyI think this is because
test, which runs on a newer commit, had the change, but then the nextreferencerun was runs on older commits, didn't yet have them ( in the release reference uses )The reset-db.sh script is quick and causes the schema to be as expected before each run
There's probably a more direct way to reset the db (we tried calling update.php in the mediawiki container) but reset-db.sh is really fast