test(parquet): reduce macOS race test memory pressure - #1275
Open
zeroshade wants to merge 1 commit into
Open
Conversation
Avoid retaining gigabyte-sized Parquet output in regression tests, serialize Parquet package tests on constrained macOS ARM64 runners, and correct the CI job labels.
lidavidm
approved these changes
Sep 2, 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
2 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.
Rationale for this change
The macOS test jobs run on 7 GB ARM64 runners and intermittently kill
parquet/filewhile running under the race detector. Two large-value regression tests each write more than 1 GB and retained all encoded output in memory. Package-level parallelism adds further pressure.Example failure: https://github.com/apache/arrow-go/actions/runs/33590782213/job/100362942846?pr=1241
What changes are included in this PR?
bytes.Bufferoutput in the two large-value tests with a counting writer.-p=1) on Darwin to bound package-level memory pressure.Are these changes tested?
go test -race -tags assert ./parquet/file -count=1go test -race -tags assert,noasm ./parquet/file -count=1bash -n ci/scripts/test.shgit diff --checkBoth formerly high-memory tests also passed independently under
-race -tags assert,noasm.Are there any user-facing changes?
No.