-
Notifications
You must be signed in to change notification settings - Fork 639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjustments for enabling nightly builds #355
Merged
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
…ordLimit from 100000 to 30000 to keep Nightly run time under 60 minutes
…or of 6 instead of a factor of 2 to keep Nightly run time under 60 minutes
…r of 6 instead of a factor of 2 to keep Nightly run time under 60 minutes
… Azure DevOps over the 1 hour time limit allowed
…Reduced amount of pause and run time for concurrency tests to keep the total test time below 1 hour
…ordLimit from 100000 to 30000 to keep Nightly run time under 60 minutes
…ly instances by 50%
…his test runs out of memory on x86
…o stay under the 1 hour job limit in Azure DevOps
…estMockAnalyzer): Reduced maximum nightly iterations by 50%
…prevent them from timing out Azure DevOps.
…mVectorCorruption() to assist with debugging occasional test failures on Linux/macOS
…gDocuments() Reduced size of big documents to keep test time under 1 hour
…: Increased ramBuffer size to offset the fact that LuceneTestCase.AtLeast() was decreased.
…ts to prevent them from going over Azure's 1hr time limit and detect which test(s) limits are problematic
…t 47-55 minutes in order to allow the test results to be uploaded. This will make troubleshooting which tests are taking too long easier.
…ctory(): increased timeout to 30 minutes
…eleaseRace(): Reduced nightly probability by 50% on x86 to keep from timing out
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.
This PR primarily focuses on reducing the nightly limits of the test framework and tests to prevent them from exceeding the 1 hour job limit of the free Azure DevOps account. Timeouts were set up so if a run goes over the limit there will still be time to upload the results in order to identify the offending test(s).
Also, tests were setup for .NET Core 3.1 x86 and .NET Core 2.1 x86 that only run nightly. Logging was also added to assist with debugging issues we are having with file lock failures on Linux and macOS.