Repository navigation
Test temp file creation with both LowMemory and MaxPerformance - #192
Merged
Merged
Conversation
The temp file test now runs once for each profile, so MaxPerformance is covered again alongside LowMemory.
drasmart
approved these changes
Oct 5, 2026
This file contains hidden or 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
3 participants
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.
#191 moved the temp file test to LowMemory after the test JVM died on
Windows runners with MaxPerformance. That failure was intermittent, so
this runs the test with both profiles to see whether MaxPerformance is
stable on its own.
If the MaxPerformance test keeps failing on Nightly, we drop it from
this PR and open an issue instead.