Skip to content

Conversation

@JhanSrbinovsky
Copy link
Collaborator

@JhanSrbinovsky JhanSrbinovsky commented Dec 2, 2025


🚀 The latest prerelease access-am3/pr15-8 at c293780 is here: #15 (comment) 🚀

@JhanSrbinovsky JhanSrbinovsky linked an issue Dec 2, 2025 that may be closed by this pull request
@github-actions
Copy link

github-actions bot commented Dec 2, 2025

🚀 Attempted to deploy access-am3 Prerelease pr15-1 with commit 22cccaf

🖥️ Gadi Deployment ❌

@JhanSrbinovsky
Copy link
Collaborator Author

got to here but fails deployment - cant make out the reason. sources in spack.yaml are the commit HASHES of the HEAD(s) of both UM and JULES. Cant see error due to source code anyway. @CodeGat @chrisb13 @ccarouge

@chrisb13
Copy link

chrisb13 commented Dec 2, 2025

H'm at a glance, looks like your path names are too long?

Traceback (most recent call last):
  File "/g/data/vk83/prerelease/apps/spack/0.22/spack/lib/spack/spack/main.py", line 1069, in main
    return _main(argv)
  File "/g/data/vk83/prerelease/apps/spack/0.22/spack/lib/spack/spack/main.py", line 1022, in _main
    return finish_parse_and_run(parser, cmd_name, args, env_format_error)
  File "/g/data/vk83/prerelease/apps/spack/0.22/spack/lib/spack/spack/main.py", line 1052, in finish_parse_and_run
    return _invoke_command(command, parser, args, unknown)
  File "/g/data/vk83/prerelease/apps/spack/0.22/spack/lib/spack/spack/main.py", line 649, in _invoke_command
    return_val = command(parser, args)
  File "/g/data/vk83/prerelease/apps/spack/0.22/spack/lib/spack/spack/cmd/install.py", line 351, in install
    install_with_active_env(env, args, install_kwargs, reporter_factory)
  File "/g/data/vk83/prerelease/apps/spack/0.22/spack/lib/spack/spack/cmd/install.py", line 420, in install_with_active_env
    env.install_specs(specs_to_install, **install_kwargs)
  File "/g/data/vk83/prerelease/apps/spack/0.22/spack/lib/spack/spack/environment/environment.py", line 1950, in install_specs
    PackageInstaller([spec.package for spec in specs], install_args).install()
  File "/g/data/vk83/prerelease/apps/spack/0.22/spack/lib/spack/spack/installer.py", line 2169, in install
    raise InstallError(f"{fail_fast_err}: {str(exc)}", pkg=pkg)
spack.installer.InstallError: Terminating after first install failure: Cannot replace b'/g/data/vk83/prerelease/apps/spack/0.22/release/linux-rocky8-x86_64_v4/intel-2021.10.0/gmake-4.4.1-iguc3vqkmaqjtjqxnfvsvjaebbo4fqkt' with b'/g/data/vk83/prerelease/apps/spack/0.22/restricted/ukmo/release/linux-rocky8-x86_64_v4/intel-2021.10.0/gmake-4.4.1-iguc3vqkmaqjtjqxnfvsvjaebbo4fqkt' because the new prefix is longer. To fix this, compile with more padding (config:install_tree:padded_length), or install to a shorter prefix.

Someone like @anton-seaice or @harshula can perhaps confirm or suggest a workaround?

@JhanSrbinovsky
Copy link
Collaborator Author

have some paths been changed since last anyone successfully built here? I could change spack to build from original tags but IDK that this would help.

@chrisb13
Copy link

chrisb13 commented Dec 3, 2025

Okie doke, I've ping'd some additional folks..

@manodeep
Copy link

manodeep commented Dec 3, 2025

Here are the two filenames - clearly the second name is longer than the first.

b'/g/data/vk83/prerelease/apps/spack/0.22/release/linux-rocky8-x86_64_v4/intel-2021.10.0/gmake-4.4.1-iguc3vqkmaqjtjqxnfvsvjaebbo4fqkt'
b'/g/data/vk83/prerelease/apps/spack/0.22/restricted/ukmo/release/linux-rocky8-x86_64_v4/intel-2021.10.0/gmake-4.4.1-iguc3vqkmaqjtjqxnfvsvjaebbo4fqkt'

The solution is to (probably) add the padded_length setting that the error message recommended, perhaps around this line

@chrisb13
Copy link

chrisb13 commented Dec 3, 2025

fyi @JhanSrbinovsky, @CodeGat is on the case!

@CodeGat
Copy link
Member

CodeGat commented Dec 3, 2025

@JhanSrbinovsky @chrisb13 I believe the issue is fixed. There was an issue with path substitution from buildcaches, but after I deleted the buildcache it worked again. Future pushes will work, but let me know if there are issues.
(@manodeep I tried adding padded_length to the config but that resulted in the same error (but with a very long placeholder path)

@JhanSrbinovsky
Copy link
Collaborator Author

!redeploy

@JhanSrbinovsky
Copy link
Collaborator Author

Thanks Tommy

@github-actions
Copy link

github-actions bot commented Dec 3, 2025

🚀 Attempted to deploy access-am3 Prerelease pr15-2 with commit 22cccaf

🖥️ Gadi Deployment ❌

@github-actions
Copy link

github-actions bot commented Dec 3, 2025

🚀 Attempted to deploy access-am3 Prerelease pr15-2 with commit 22cccaf

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.10.000 as a Release (when merged).
  • pr15-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr15-2

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-am3-pr15-2 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

github-actions bot commented Dec 3, 2025

🚀 Attempted to deploy access-am3 Prerelease pr15-3 with commit 0c0fb8f

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.10.000 as a Release (when merged).
  • pr15-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr15-3

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-am3-pr15-3 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@JhanSrbinovsky
Copy link
Collaborator Author

@CodeGat - FYI

dummy push from my local checkout. - worked :)

!redeploy and GUI re-run didn't work. co-pilot suggested error was with paths again and possibly spack update or something

I suspect it won't happen again now, the gears have turned and all the right pieces picked up so it'll probably be fine. I'll run a !redploy now to check. if you don't hear from me its all good

thanks also @chrisb13 @manodeep et al

@JhanSrbinovsky
Copy link
Collaborator Author

!redploy

@github-actions
Copy link

🚀 Attempted to deploy access-am3 Prerelease pr15-4 with commit 720328c

🖥️ Gadi Deployment ❌

@JhanSrbinovsky
Copy link
Collaborator Author

was pushing to a hook
!redeploy

@JhanSrbinovsky
Copy link
Collaborator Author

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-am3 Prerelease pr15-5 with commit 720328c

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.10.000 as a Release (when merged).
  • pr15-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr15-5

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-am3-pr15-5 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@JhanSrbinovsky
Copy link
Collaborator Author

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-am3 Prerelease pr15-6 with commit 720328c

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.10.000 as a Release (when merged).
  • pr15-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr15-6

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-am3-pr15-6 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link

🚀 Attempted to deploy access-am3 Prerelease pr15-7 with commit faf5b4d

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy access-am3 Prerelease pr15-8 with commit c293780

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.10.000 as a Release (when merged).
  • pr15-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr15-8

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-am3-pr15-8 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

test urban-dev merger

5 participants