bvolpato opened a new pull request, #39295:
URL: https://github.com/apache/beam/pull/39295

   Fixes #39267.
   
   Java 21 GCP IO precommit tests fail for two independent reasons:
   
   * `BeamRowToStorageApiProtoTest` initializes microsecond logical types from 
wall-clock values that can contain nanosecond precision.
   * Apache Arrow direct-memory access requires the `java.nio` package to be 
open.
   
   This change uses fixed, microsecond-aligned values for affected logical 
types and opens `java.nio` for GCP IO test tasks, matching Beam's Arrow module 
configuration.
   
   Validation:
   
   * Java 21 full GCP IO unit suite and Spotless check
   * Java 21 targeted Beam row and Arrow regression tests
   * Java 17 targeted Beam row and Arrow regression tests
   * GCP IO test Checkstyle
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [x] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable. This will automatically add a link to the 
pull request in the issue. If you would like the issue to automatically close 
on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead.
    - [x] `CHANGES.md` update not needed for a test-only fix.
    - [x] Apache Individual Contributor License Agreement not needed for this 
small contribution.
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to