Restrict payu versions greater than 1.1.6 - #356
Merged
Merged
Conversation
This is done temporarily for the upcoming workshop training. More recent payu features are not currently needed by benchcab and are causing some issues. E.g. payu requires explicitly specifying the --new-uuid argument to generate a new experiment UUID in [payu 1.3.3][payu-1.3.3] and python 3.9 support was dropped in [payu 1.1.6][payu-1.1.6]. [payu-1.1.6]: https://github.com/payu-org/payu/releases/tag/1.1.6 [payu-1.3.3]: https://github.com/payu-org/payu/releases/tag/1.3.3
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #356 +/- ##
=======================================
Coverage 68.83% 68.83%
=======================================
Files 21 21
Lines 1232 1232
=======================================
Hits 848 848
Misses 384 384 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
SeanBryan51
added a commit
that referenced
this pull request
Aug 18, 2026
I had forgotten there was a necessary change made in [payu 1.1.7][payu-1.1.7] to prepend the container launcher script to the pbs command - this is required by benchcab to function on Gadi. Installing benchcab with python > 3.9 (when using more recent versions of payu) does not break functionality, so it was unnecessary to impose payu < 1.1.6 in #356. Instead, we restrict payu to be < [1.3.3][payu-1.3.3] which introduces the `--new-uuid` requirement which breaks existing functionality. [payu-1.1.7]: https://github.com/payu-org/payu/releases/tag/1.1.7 [payu-1.3.3]: https://github.com/payu-org/payu/releases/tag/1.3.3
SeanBryan51
added a commit
that referenced
this pull request
Aug 18, 2026
I had forgotten there was a necessary change made in [payu 1.1.7][payu-1.1.7] to prepend the container launcher script to the pbs command - this is required by benchcab to function on Gadi. Installing benchcab with python > 3.9 (when using more recent versions of payu) does not break functionality, so it was unnecessary to impose payu < 1.1.6 in #356. Instead, we restrict payu to be < [1.3.3][payu-1.3.3] which introduces the `--new-uuid` requirement which breaks existing functionality. [payu-1.1.7]: https://github.com/payu-org/payu/releases/tag/1.1.7 [payu-1.3.3]: https://github.com/payu-org/payu/releases/tag/1.3.3
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
1 participant
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.
This is done temporarily for the upcoming workshop training. More recent payu features are not currently needed by benchcab and are causing some issues. E.g. payu requires explicitly specifying the --new-uuid argument to generate a new experiment UUID in payu 1.3.3 and python 3.9 support was dropped in payu 1.1.6.