Skip to content

Add -fprofile-generate flag to compiler options for dev-MC_8km_jra_ryf for 780-dev-MC_8km_jra_ryf-2 - #267

Draft
chrisb13 wants to merge 2 commits into
mainfrom
266-profile-generator-8km
Draft

Add -fprofile-generate flag to compiler options for dev-MC_8km_jra_ryf for 780-dev-MC_8km_jra_ryf-2#267
chrisb13 wants to merge 2 commits into
mainfrom
266-profile-generator-8km

Conversation

@chrisb13

@chrisb13 chrisb13 commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

Do not MERGE.

Following chat with @manodeep adding profile flags, see ACCESS-NRI/access-om3-configs#1611


🚀 The latest prerelease access-om3/pr267-1 at 1d75e33 is here: #267 (comment) 🚀


🚀 The latest prerelease access-om3/pr267-2 at bf779a4 is here: #267 (comment) 🚀

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr267-1 with commit 1d75e33

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.003 as a Release (when merged).
  • pr267-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr267-1

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/1.1/spack in the access-om3-pr267-1 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:

  • access-nri/spack on branch 1.1
  • ACCESS-NRI/upstream-spack-packages version access/v1.1
  • access-nri/access-spack-packages version 2026.08.005
  • access-nri/spack-config version 2026.08.001

If the above was not what was expected, commit changes to the manifest in this PR, or propose changes to build-cds config/settings.json.

@manodeep

manodeep commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

@chrisb13 Profiling info commit pushed - deployment build going on now

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr267-2 with commit bf779a4

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.003 as a Release (when merged).
  • pr267-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr267-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/1.1/spack in the access-om3-pr267-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:

  • access-nri/spack on branch 1.1
  • ACCESS-NRI/upstream-spack-packages version access/v1.1
  • access-nri/access-spack-packages version 2026.08.005
  • access-nri/spack-config version 2026.08.001

If the above was not what was expected, commit changes to the manifest in this PR, or propose changes to build-cds config/settings.json.

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.

2 participants