Build with default UM7 optimisation levels set at the top level #170

manodeep · 2025-11-24T01:10:27Z

Testing for compiler flag updates to SPRs - do not merge (at least yet)

🚀 The latest prerelease access-esm1p6/pr170-22 at f32e5e8 is here: #170 (comment) 🚀

github-actions · 2025-11-24T01:11:03Z

The model version in the ./spack.yaml has not been updated.
You can update it manually.

github-actions · 2025-11-24T01:11:29Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-1 with commit 4c7edae

🖥️ `Gadi` Deployment ❌

github-actions · 2025-11-24T01:27:36Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-1 with commit 4c7edae

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-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/0.22/spack in the access-esm1p6-pr170-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 0.22
access-nri/spack-packages version b3f43b0a5d603039c7dd59c2061a7811dd3fd29b
access-nri/spack-config version 2025.08.000

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

github-actions · 2025-11-24T02:10:29Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-2 with commit 40e0025

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-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-esm1p6-pr170-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 0.22
access-nri/spack-packages version 4b14b379b1f3b459bc23bfe2acfcb8aee8039a84
access-nri/spack-config version 2025.08.000

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

manodeep · 2025-11-24T02:28:25Z

Both the previous two deployments passed !test repro on the config repo - here, and here

github-actions · 2025-11-24T02:44:51Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-3 with commit 2fed6dc

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-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-esm1p6-pr170-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:

access-nri/spack on branch 0.22
access-nri/spack-packages version 1d1c80528ae8155bbf3a85d73a578352bcf26ffc
access-nri/spack-config version 2025.08.000

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

github-actions · 2025-11-24T04:00:15Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-4 with commit c73873c

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-4

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-esm1p6-pr170-4 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 0.22
access-nri/spack-packages version d14e39326e0d9b49d10373835b3acc1b32d2548c
access-nri/spack-config version 2025.08.000

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

github-actions · 2025-11-24T04:31:07Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-5 with commit 959b758

🖥️ `Gadi` Deployment ❌

manodeep · 2025-11-24T05:17:44Z

!redeploy

github-actions · 2025-11-24T05:40:56Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-6 with commit 959b758

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-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-esm1p6-pr170-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:

access-nri/spack on branch 0.22
access-nri/spack-packages version 6df90a2a174b878ba63be85007edf5ce972e8636
access-nri/spack-config version 2025.08.000

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

github-actions · 2025-11-24T08:56:46Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-7 with commit 6a1f7b4

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-7

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-esm1p6-pr170-7 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 0.22
access-nri/spack-packages version f8a39993efcd46591463954d99a781e5b2ee7eed
access-nri/spack-config version 2025.08.000

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

github-actions · 2025-11-24T12:02:22Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-8 with commit 82be501

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-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-esm1p6-pr170-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:

access-nri/spack on branch 0.22
access-nri/spack-packages version b408593fb5b00236bd638b812dfcd9acd3bf6709
access-nri/spack-config version 2025.08.000

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

github-actions · 2025-11-25T10:44:38Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-14 with commit c85b3ed

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-14

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-esm1p6-pr170-14 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 0.22
access-nri/spack-packages version a3b26a5c3ccaca9dd09fcfc56c8c71b79d348d5d
access-nri/spack-config version 2025.08.000

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

github-actions · 2025-11-25T12:12:46Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-15 with commit b0ec7c0

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-15 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-15

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-esm1p6-pr170-15 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 0.22
access-nri/spack-packages version 92ee0dadb1291c971912df0ab4075294fe2992c5
access-nri/spack-config version 2025.08.000

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

manodeep · 2025-11-25T12:16:04Z

The last build with flto still crashes with a segfault (see this).

github-actions · 2025-11-25T20:36:20Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-16 with commit 82657d9

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-16 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-16

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-esm1p6-pr170-16 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 0.22
access-nri/spack-packages version 41c4eb6ca025650c20ad0c8ef5458f869fb8bf92
access-nri/spack-config version 2025.08.000

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

…th qopt-zmm-high and always vectorise

github-actions · 2025-11-26T00:49:03Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-17 with commit cd3f8bc

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-17 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-17

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-esm1p6-pr170-17 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 0.22
access-nri/spack-packages version 2bb07b73f4c201f24e2f189445949e33c730f9b9
access-nri/spack-config version 2025.08.000

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

manodeep · 2025-11-26T02:19:19Z

Interestingly, this last build (with these changes to UM7 SPR) crashed with this error:

gc_abort (Processor   192): over-writing due to dim_e_out size
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 192 in communicator MPI_COMM_WORLD
  Proc: [[62655,1],192]
  Errorcode: 9

<snip>

forrtl: error (78): process killed (SIGTERM)
Image              PC                Routine            Line        Source             
libpthread-2.28.s  000015336D23D990  Unknown               Unknown  Unknown
libopen-pal.so.80  000015336A5B9494  opal_progress         Unknown  Unknown
libmpi.so.40.40.7  000015336A69FEC2  Unknown               Unknown  Unknown
libmpi.so.40.40.7  000015336A704481  Unknown               Unknown  Unknown
libmpi.so.40.40.7  000015336A7463EA  Unknown               Unknown  Unknown
libmpi.so.40.40.7  000015336A6BD824  PMPI_Bcast            Unknown  Unknown
libmpi_mpifh_Inte  000015336DE19765  PMPI_BCAST            Unknown  Unknown
um_hg3.exe         0000000001202FFC  mpl_bcast                  59  mpl_bcast.F90
um_hg3.exe         0000000001202E4B  gcg_rvecsumr              218  gcg_rvecsumr.F90

Since the source file only contains 128 lines, and the traceback shows a line number of 218, I made an educated guess that the offending line is this one. (The traceback shows the call to MPL_BCAST after gcg_rvecsumr, and the only such call in gcg_rvecsumr is in that line). edit Of course, the bug could also be elsewhere and the execution just happened to be at that point within gcg_rvecsumr on a different rank

…se, and add unroll

github-actions · 2025-11-26T02:48:38Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-18 with commit 1fcd9c5

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-18 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-18

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-esm1p6-pr170-18 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 0.22
access-nri/spack-packages version 5f91308538ecdd93922fb6bab500e807c4086f37
access-nri/spack-config version 2025.08.000

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

manodeep · 2025-11-26T04:24:06Z

Judging by the size of the output file, build 18 has gone past the stage where build 17 crashed.

manodeep · 2025-11-26T11:31:55Z

All three runs finished with deployment 18, the performance is worse, and the results are not bitwise identical. -fp-model precise is going back in.

github-actions · 2025-11-26T11:34:46Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-19 with commit 1b7cf02

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-19 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-19

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-esm1p6-pr170-19 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 0.22
access-nri/spack-packages version 18e0a1afc22b181c4733f8e198bb1139d5ccd2e1
access-nri/spack-config version 2025.08.000

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

manodeep · 2025-11-26T23:34:49Z

Somewhat surprisingly, deployment 19 is by far the slowest of all the working deployments (throughput ~20.1 years/day). Going back to deployment 12 - which builds with the compiler pragma updates to UM7; and then adding in the source update for disabling bitwise-repro in GCOM4 (this branch which sets GC_FORCE_BITREP to 0 - which the documentation says should have been the case anyway)

github-actions · 2025-11-26T23:55:44Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-20 with commit 618fc8a

🖥️ `Gadi` Deployment ❌

github-actions · 2025-11-27T00:29:20Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-21 with commit 3fc5c5f

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-21 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-21

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-esm1p6-pr170-21 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 0.22
access-nri/spack-packages version d14e39326e0d9b49d10373835b3acc1b32d2548c
access-nri/spack-config version 2025.08.000

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

github-actions · 2025-11-27T02:58:21Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr170-22 with commit f32e5e8

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.11.001 as a Release (when merged).
pr170-22 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr170-22

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-esm1p6-pr170-22 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 0.22
access-nri/spack-packages version d14e39326e0d9b49d10373835b3acc1b32d2548c
access-nri/spack-config version 2025.08.000

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

Build with default UM7 optimisation levels set at the top level

4c7edae

manodeep marked this pull request as draft November 24, 2025 01:10

manodeep temporarily deployed to Gadi Prerelease November 24, 2025 01:11 — with GitHub Actions Inactive

manodeep mentioned this pull request Nov 24, 2025

Checking for bitwise repro with updated UM7 compiler flags + code ACCESS-NRI/access-esm1.6-configs#285

Open

14 tasks

Update to UM7 with fp-model=precise instead of strict

40e0025

manodeep temporarily deployed to Gadi Prerelease November 24, 2025 01:54 — with GitHub Actions Inactive

Use the updated arch flags for UM7

2fed6dc

manodeep temporarily deployed to Gadi Prerelease November 24, 2025 02:26 — with GitHub Actions Inactive

Deploying with unroll for UM7

c73873c

manodeep temporarily deployed to Gadi Prerelease November 24, 2025 03:40 — with GitHub Actions Inactive

Deploying with the qopt-zmm-high flag

959b758

manodeep had a problem deploying to Gadi Prerelease November 24, 2025 04:06 — with GitHub Actions Failure

Deploy with vectorise-everyrthing compiler flag

6a1f7b4

manodeep temporarily deployed to Gadi Prerelease November 24, 2025 08:37 — with GitHub Actions Inactive

Removing unroll but keeping the vectorisation options

82be501

manodeep temporarily deployed to Gadi Prerelease November 24, 2025 11:32 — with GitHub Actions Inactive

Deploying with unroll-aggressive but no vectorisation flags

1077f04

manodeep temporarily deployed to Gadi Prerelease November 24, 2025 12:07 — with GitHub Actions Inactive

Deploy with flto - fingers crossed!

b0ec7c0

manodeep temporarily deployed to Gadi Prerelease November 25, 2025 11:49 — with GitHub Actions Inactive

Deploy without flto, unroll and opt-prefetch=5

82657d9

manodeep temporarily deployed to Gadi Prerelease November 25, 2025 20:20 — with GitHub Actions Inactive

Compile without $fp-model-precise, unroll and opt-prefetch$, and wi…

cd3f8bc

…th qopt-zmm-high and always vectorise

manodeep temporarily deployed to Gadi Prerelease November 26, 2025 00:29 — with GitHub Actions Inactive

Since previous build crashed, remove qopt-zmm-high and always vectori…

1fcd9c5

…se, and add unroll

manodeep temporarily deployed to Gadi Prerelease November 26, 2025 02:29 — with GitHub Actions Inactive

Add fp-model precise back in

1b7cf02

manodeep temporarily deployed to Gadi Prerelease November 26, 2025 11:16 — with GitHub Actions Inactive

Going back to deployment 12, and adding the disabled repro for GCOM4

618fc8a

manodeep had a problem deploying to Gadi Prerelease November 26, 2025 23:37 — with GitHub Actions Failure

Ughhh typo in the commit hash

3fc5c5f

manodeep temporarily deployed to Gadi Prerelease November 27, 2025 00:00 — with GitHub Actions Inactive

Revert back the change to gcom4 - force-bit-rep is OFF by default

f32e5e8

manodeep temporarily deployed to Gadi Prerelease November 27, 2025 02:48 — with GitHub Actions Inactive

Build with default UM7 optimisation levels set at the top level #170

Are you sure you want to change the base?

Build with default UM7 optimisation levels set at the top level #170

Uh oh!

Conversation

manodeep commented Nov 24, 2025 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Nov 24, 2025

Uh oh!

github-actions bot commented Nov 24, 2025

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Nov 24, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Nov 24, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Nov 24, 2025

Uh oh!

github-actions bot commented Nov 24, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Nov 24, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Nov 24, 2025

🖥️ Gadi Deployment ❌

Uh oh!

manodeep commented Nov 24, 2025

Uh oh!

github-actions bot commented Nov 24, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Nov 24, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Nov 24, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Nov 25, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Nov 25, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Nov 25, 2025

Uh oh!

github-actions bot commented Nov 25, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Nov 26, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Nov 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Nov 26, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Nov 26, 2025

Uh oh!

manodeep commented Nov 26, 2025

Uh oh!

github-actions bot commented Nov 26, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

manodeep commented Nov 26, 2025

Uh oh!

github-actions bot commented Nov 26, 2025

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Nov 27, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Nov 27, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

Reviewers

manodeep commented Nov 24, 2025 •

edited by github-actions bot

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

manodeep commented Nov 26, 2025 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️