Prepare for MazeRunner 3.6.0 #1182
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.
Goal
Prepare for the release of MazeRunner v3.6.0.
Design
MazeRunner v3.6.0 will enforce the presence of the Bugsnag-Integrity and fail tests, unless configured otherwise. This PR relaxes the check for platforms that are not implementing the header.
MazeRunner v3.6.0 also fixes a long standing problem with the
I should receive no requestsstep, meaning that the test harness will now wait for a default time of 30s each time it is used. As this is longer that the time needed in the JavaScript tests, we can prepare for the release by setting the appropriate config value to 15s, if it is available.The fix to the above step has highlighted issues in the Node tests, where the notifier is sending requests that we do not expect. The Node tests are therefore pinned to v3.5.1 and an internal ticket, PLAT-5584, has been raised to fix the Node tests and bring them back to the latest version of MazeRunner.
Changeset
MazeRunner Docker and support files.
Testing
All changes for v3.6.0 are now on the MazeRunner master branch and before creating this PR I configured each platform to run against the master version in order to smoke out any issues. When v3.6.0 is released, this should mean that there are no adverse effects on the JavaScript tests.