fix: windows tests getting stuck and timing out #930
Merged
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.
Please prefix your pull request with one of the following: [FEATURE] [FIX] [IMPROVEMENT].
In raising this pull request, I confirm the following (please check boxes):
My familiarity with the project is as follows (check one):
The windows tests have been getting stuck and timing out recently. The root cause was with how Rclone handled chunked reads for large files, this PR fixes this issue by passing an option to the underlying FUSE emulator that Rclone uses to modify how chunked reads are handled. For more information on this, refer here.
The timeout has also been reduced to 10 minutes, the reasoning for this is that on previous successful windows tests (such as this one) no single test entry has taken more than two minutes to run.
An entry taking more than 10 more than likely suggests that something has gone wrong. This is more of a preventative measure as Linux tests have also failed as a whole in the past due to single entries taking more than 50 minutes (the current duration).