Payu run str error with rom3

COSIMA Working Group
1

I have been following these instructions to run ACCESS-ROM3 from rest, with all the setup initiated from an interactive payu clone, etc. I’m using payu/1.3.5_0.

Everything goes well until I run payu run, at which point I get the following error:

[ERROR] 'str' object cannot be interpreted as an integer

Traceback (most recent call last):

  File "/containerised_envs/payu/1.3.5_0/lib/python3.10/site-packages/payu/cli.py", line 323, in _execute_command

    func(**args)

  File "/containerised_envs/payu/1.3.5_0/lib/python3.10/site-packages/payu/subcommands/run_cmd.py", line 75, in runcmd

    cpu_q, mem_q = PBS.get_queue_node_shape(queue)

  File "/containerised_envs/payu/1.3.5_0/lib/python3.10/site-packages/payu/schedulers/pbs.py", line 305, in get_queue_node_shape

    data = read_pbsnode_file()

  File "/containerised_envs/payu/1.3.5_0/lib/python3.10/site-packages/payu/schedulers/pbs.py", line 89, in read_pbsnode_file

    check_pbsnode_file(pbsnodes_json_path)

  File "/containerised_envs/payu/1.3.5_0/lib/python3.10/site-packages/payu/schedulers/pbs.py", line 62, in check_pbsnode_file

    timestamp = datetime.fromtimestamp(pbsnodes_json.get("timestamp", 0))

TypeError: 'str' object cannot be interpreted as an integer

The error is quite ominous. Does anyone have an idea what I might be doing wrong?

Note: I followed Step 1 exactly as stated on GitHub, with no additional changes.

2

after a back and forth with an AI coding agent, I was able to fix the problem. it seems like my personal cache was corrupted and putting strings in the PBS timestamp .

e.g. "timestamp": ""
instead of e.g. "timestamp":1788396111

I was able to fix by just moving out of the way my pbsnodes.json and allowing the system to create a new one.

(e.g. mv ~/.cache/pbs/pbsnodes.json ~/.cache/pbs/pbsnodes.json.bad)

marking this as a solution in case someone else have the same problem

3

Thanks for reporting @Wilton_Aguiar, and great you solved it youself. We have an existing issue for this, so it is clearly something that is affecting users and should be fixed.

4

Thank you @Wilton_Aguiar for reporting this!

This bug has now been fixed in payu/1.3.6 (see release post). Please don’t hesitate to reach out if you come across any other questions or issues.