Update PIO from pio2_6_2 to pio2_6_5

[billsacks]

I did this update by simply copying the ParallelIO repository (checked
out at pio2_6_5) to here, and then deleting the .git directory. I
confirmed that, prior to this update, there were no diffs from the
ParallelIO repository (at pio2_6_2), so it is safe to do the update in
this simple manner.

Changes here:

• pio2_6_3: Merge pull request #1982 from alperaltuntas/bugfix_debug: fix minor bugs in pio_nc4.c
• pio2_6_4: Bug fix release. Fixes issues with large datasets and with autoconf/cmake configure option.
• pio2_6_5: Updated for compatibility with netcdf-c 4.9.3 and cygwin.

Resolves #353

[billsacks]

@jedwards4b @theurich @oehmke - FYI

I have run testing on my Mac and all tests pass. It looks like, at least for some PIO updates in the past, we have run full nightly testing on a branch before merging. The changes here look fairly minimal, though, so my feeling is that that seems unnecessary here. @theurich or @oehmke - any feelings on whether to do that or just merge and check the regular nightly testing the next day?

[oehmke]

If the changes are pretty minimal, I’m ok with just merging them and checking them the next day. (Just keep an eye on the 4 platforms worth of tests that automatically run on develop now and make sure they look ok.)

…

On Feb 24, 2025, at 2:21 PM, Bill Sacks ***@***.***> wrote: billsacks left a comment (esmf-org/esmf#359) @jedwards4b @theurich @oehmke - FYI I have run testing on my Mac and all tests pass. It looks like, at least for some PIO updates in the past, we have run full nightly testing on a branch before merging. The changes here look fairly minimal, though, so my feeling is that that seems unnecessary here. @theurich or @oehmke - any feelings on whether to do that or just merge and check the regular nightly testing the next day? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned. <https://github.com/jedwards4b> <https://github.com/theurich> <https://github.com/oehmke> <https://github.com/theurich> <https://github.com/oehmke> <#359 (comment)> <https://github.com/notifications/unsubscribe-auth/AE6A7U33IXU43BKJHMEY3RD2ROEM3AVCNFSM6AAAAABXZA6FYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZZGY3TMMZVHE> billsacks left a comment (esmf-org/esmf#359) <#359 (comment)> @jedwards4b <https://github.com/jedwards4b> @theurich <https://github.com/theurich> @oehmke <https://github.com/oehmke> - FYI I have run testing on my Mac and all tests pass. It looks like, at least for some PIO updates in the past, we have run full nightly testing on a branch before merging. The changes here look fairly minimal, though, so my feeling is that that seems unnecessary here. @theurich <https://github.com/theurich> or @oehmke <https://github.com/oehmke> - any feelings on whether to do that or just merge and check the regular nightly testing the next day? — Reply to this email directly, view it on GitHub <#359 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE6A7U33IXU43BKJHMEY3RD2ROEM3AVCNFSM6AAAAABXZA6FYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZZGY3TMMZVHE>. You are receiving this because you were mentioned.