Catch EMS variables initialized after reference by joseph-robertson · Pull Request #11409 · NatLabRockies/EnergyPlus

joseph-robertson · 2026-01-29T23:05:46Z

Pull request overview

Fixes Unitialized EMS variable is misused #11360

Description of the purpose of this PR

Pull Request Author

Reviewer

…ter reference does not throw error.

mitchute · 2026-01-30T01:47:14Z

As I understand it, Windows builds don't pick up uninitialized variables, which we treat as errors.

/home/mitchute/Projects/EnergyPlus/tst/EnergyPlus/unit/EMSManager.unit.cc:1065:9: error: unused variable ‘wallSurfNum’ [-Werror=unused-variable]
 1065 |     int wallSurfNum = Util::FindItemInList("WALL", state->dataSurface->Surface);
      |         ^~~~~~~~~~~

rraustad · 2026-01-30T04:04:59Z

I am using Windows 11 and do not get the unused variable warning for wallSurfNum, well, because it is initialized at line 1065 and used at 1068. If there is an issue with EMS initializing a variable before it's used (e.g., site_temp_adj) then this unit test should fail. But it doesn't, it passes with. wallSurfNum = 1, ViewFactorGround = 0.1 and seriousErrorFound = false (i.e., EXPECT_TRUE on line 1076 should be EXPECT_FASLE and line 1068 is correct). So what should happen here? I assume this unit test should check for whether site_temp_adj was initialized before it was used, but I don't see that in this unit test.

joseph-robertson · 2026-01-30T16:35:57Z

This PR is about the EMS variable site_temp_adj, not wallSurfNum. The intent (i.e., 8623d71) was to commit a failing test, to demonstrate that the uninitialized site_temp_adj should throw an error but does not. The test fails on my machine.

joseph-robertson · 2026-01-30T16:55:38Z

tst/EnergyPlus/unit/EMSManager.unit.cc

+        "    Set power_mult = site_temp_adj,                !- Program Line 1",
+        "    Set site_temp_adj = 0.1,                       !- Program Line 2",


Variable site_temp_adj is being initialized after it is referenced. We should expect an error, right?

joseph-robertson · 2026-01-30T16:56:19Z

tst/EnergyPlus/unit/EMSManager.unit.cc

+    int wallSurfNum = Util::FindItemInList("WALL", state->dataSurface->Surface);
+    bool anyRan;
+    EMSManager::ManageEMS(*state, EMSManager::EMSCallFrom::BeginTimestepBeforePredictor, anyRan, ObjexxFCL::Optional_int_const());
+    EXPECT_EQ(state->dataSurface->Surface(wallSurfNum).ViewFactorGround, 0.1);


I intentionally had this line commented out so that we could get to EXPECT_TRUE(seriousErrorFound); down below.

Sure, feel free to do what you need. I won't interfere anymore until you need someone to look. I was just pointing out that the CI linux builds were failing due to to the unused variable, that we treat as an error.

No problem, understood.

… just ManageSimulation.

joseph-robertson · 2026-01-30T22:37:54Z

Pretty sure I have this narrowed down. I think GetEMSInput can set state.dataRuntimeLang->ErlVariable(VariableNum).Value.initialized = true without calling EvaluateExpression first.

joseph-robertson · 2026-01-30T22:42:25Z

tst/EnergyPlus/unit/EMSManager.unit.cc

+
+    internalVarNum = RuntimeLanguageProcessor::FindEMSVariable(*state, "site_temp_adj", 1);
+    ASSERT_GT(internalVarNum, 0);
+    EXPECT_TRUE(state->dataRuntimeLang->ErlVariable(internalVarNum).Value.initialized);


This is the main difference with the first test; why is this suddenly initialized?

joseph-robertson · 2026-02-06T23:21:44Z

Pretty sure I have this narrowed down. I think GetEMSInput can set state.dataRuntimeLang->ErlVariable(VariableNum).Value.initialized = true without calling EvaluateExpression first.

It's not in GetEMSInput. It happens somewhere toward the beginning of ManageSimulation (likely in SetupSimulation whose purpose is to "... execute a few time steps of a simulation to facilitate setting up model ..."). I can confirm this by looking at RuntimeLanguageProcessor::FindEMSVariable(state, "site_temp_adj", StackNum); just after SetupSimulation, which shows the EMS variable is indeed initialized (yet EvaluateStack was never called for on the EMS program). Then it looks like the EMSManager::EMSCallFrom::SetupSimulation just below sets the variable back to 0.0.

I'm not totally sure what the fix is here. Perhaps EvaluateStack is being called via SetupSimulation, but with FinishProcessingUserInput=true?

…pSimulation.

joseph-robertson · 2026-02-10T23:44:42Z

testfiles/_ResidentialBase.idf

+  Output:EnergyManagementSystem,
+    Verbose,                    !- Actuator Availability Dictionary Reporting
+    Verbose,                    !- Internal Variable Availability Dictionary Reporting
+    Verbose;              !- EMS Runtime Language Debug Output Level


This test file has a program (BeginZoneTimestepAfterInitHeatBalance) that uses variables which are initialized in another program/subroutine (EndOfSystemTimestepAfterHVACReporting). I.e., initialized after reference.

joseph-robertson · 2026-02-10T23:49:59Z

testfiles/RetailPackagedTESCoil.idf

-    Run CalcBouyancyTerms,   !- <none>
-    SEt Numerator = WindMCT + NatBouyMCT + SumHATroof + QdotCond + SumReliefMCT,  !- <none>
+    Set Numerator = WindMCT + NatBouyMCT + SumHATroof + QdotCond + SumReliefMCT,  !- <none>
    Set Denominator = WindMC + NatBouyMC + SumHAroof + SumIntakeMdotCp,  !- <none>
    Set Troof = Numerator / Denominator,  !- <none>
    IF Ta < 2.0,             !- <none>
    Set Troof = Ta,          !- <none>
    ENDIF,                   !- <none>
    IF Troof < Twb,          !- <none>
    Set Twb = Troof - 0.2,   !- <none>
-    ENDIF;                   !- <none>


Something weird going on in this program. Here Troof is a function of, e.g., NatBouyMCT. Subroutine CalcBouyancyTerms needs Troof, which is used to calculate NatBouyMCT... am I missing something here?

@mitchute Any ideas here?

Agreed. CalcBouyancyTerms should probably be moved above Numerator

joseph-robertson · 2026-02-10T23:53:52Z

src/EnergyPlus/RuntimeLanguageProcessor.cc

+                    if ((!state.dataGlobal->DoingSizing && !state.dataGlobal->KickOffSimulation && !state.dataEMSMgr->FinishProcessingUserInput) ||
+                        (!(thisErlVar.SetByGlobalVariable || thisErlVar.SetByInternalVariable))) {


The basic idea here is to do what we were doing before, unless the uninitialized variable is either a global/internal variable. If it isn't global/internal, set seriousErrorFound = true. If it is, let it slide.

Seems like a reasonable approach.

github-actions · 2026-02-11T00:06:24Z

⚠️ Regressions detected on ubuntu-24.04 for commit `f4e0687`

Regression Summary

EDD: 2
EIO: 1
ESO Big Diffs: 1
MTR Big Diffs: 1
Table Big Diffs: 1
Table String Diffs: 1

github-actions · 2026-02-11T00:29:54Z

⚠️ Regressions detected on macos-14 for commit `f4e0687`

Regression Summary

EDD: 2
EIO: 1
ESO Big Diffs: 1
MTR Big Diffs: 1
Table Big Diffs: 1

github-actions · 2026-02-11T23:27:02Z

⚠️ Regressions detected on ubuntu-24.04 for commit `d1a8173`

Regression Summary

EDD: 7
EIO: 1
ESO Big Diffs: 1
MTR Big Diffs: 1
Table Big Diffs: 1
Table String Diffs: 2
Table Small Diffs: 1

github-actions · 2026-02-11T23:29:55Z

⚠️ Regressions detected on macos-14 for commit `d1a8173`

Regression Summary

EDD: 7
EIO: 1
ESO Big Diffs: 1
MTR Big Diffs: 1
Table Big Diffs: 1
Table Small Diffs: 1
Table String Diffs: 1

… throw.

mitchute · 2026-02-17T16:57:57Z

testfiles/_ResidentialBase.idf

  EnergyManagementSystem:ProgramCallingManager,
    central_ac_and_furnace_airloop_0_duct_program calling manager,  !- Name
-    EndOfSystemTimestepAfterHVACReporting,  !- EnergyPlus Model Calling Point
+    BeginZoneTimestepBeforeInitHeatBalance,  !- EnergyPlus Model Calling Point


Why the change?

Without this IDF file change, and with the fix in this PR, you'd see ATTIC_UNVENTED_1_DUCT_LEAKAGE_IMBALANCE_INFIL_PROGRAM,Line 3,SET QDUCTS = QDUCTS + CENTRAL_AC_AND_FURNACE_AIRLOOP_0_DUCTIMBALLKEXHFANEQUIVDZ, *** Error: EvaluateExpression: Variable = 'QDUCTS' used in expression has not been initialized! *** , During Warmup, Occurrence info=DENVER CENTENNIAL GOLDEN N ANN HTG 99% CONDNS DB, 12/21 00:00 - 01:00 in the EDD file and the simulation fatals.

EnergyManagementSystem:Program, attic_unvented_1_duct_leakage_imbalance_infil_program, !- Name Set Qducts = 0, !- Program Line 1 Set Qducts = Qducts - central_ac_and_furnace_airloop_0_DuctImbalLkSupFanEquivDZ, !- Program Line 2 Set Qducts = Qducts + central_ac_and_furnace_airloop_0_DuctImbalLkExhFanEquivDZ, !- <none> Set attic_unvented_1_duct_leakage_imbalance_infil_flow_act = (@Abs(Qducts)); !- <none>

Qducts is initialized on line 1. On line 2 the throw is skipped; central_ac_and_furnace_airloop_0_DuctImbalLkSupFanEquivDZ is uninitialized but doesn't fatal since central_ac_and_furnace_airloop_0_DuctImbalLkSupFanEquivDZ is a global variable. Then on line 3 Qducts is uninitialized (because of the preceding program line), and fatals since Qducts is not a global variable.

So basically the change in the above PCM from EndOfSystemTimestepAfterHVACReporting to BeginZoneTimestepBeforeInitHeatBalance causes both central_ac_and_furnace_airloop_0_DuctImbalLkSupFanEquivDZ and central_ac_and_furnace_airloop_0_DuctImbalLkExhFanEquivDZ to initialize so that program line 2 and 3 above don't leave Qducts uninitialized.

mitchute

Looks good. I'll let you decide on what to do regarding this: https://github.com/NatLabRockies/EnergyPlus/pull/11409/changes#r2790815597

…CalcBouyancyTerms.

joseph-robertson · 2026-02-18T17:03:07Z

Looks good. I'll let you decide on what to do regarding this: https://github.com/NatLabRockies/EnergyPlus/pull/11409/changes#r2790815597

With this change, we can have CalcBouyancyTerms above Numerator. In either case the MODELFLATROOFMICROCLIME,Line 9,SET TROOF = NUMERATOR / DENOMINATOR, *** Error: EvaluateExpression: Divide By Zero in EMS Program! *** goes away, but this change seems more minimal.

Edit: Actually this change leads to the following in the ERR file:

+   ** Warning ** Calculated Humidity Ratio Invalid (PsyWFnTdbTwbPb)
+   **   ~~~   **  Routine=Unknown, Environment=CHICAGO ANN HTG 99.6% CONDNS DB, at Simulation time=01/21 06:10 - 06:20
+   **   ~~~   **  Dry-Bulb= -18.61 Wet-Bulb= -20.62 Pressure= 99063.00
+   **   ~~~   ** Calculated Humidity Ratio= -1.8069E-004, will recalculate Humidity Ratio using Relative Humidity .01% (and Dry-Bulb and Pressure as shown)

I'll just revert to the original program, and initialize Troof = 0.0. 00da99c

github-actions · 2026-02-18T17:17:21Z

⚠️ Regressions detected on ubuntu-24.04 for commit `79da40f`

Regression Summary

EDD: 7
EIO: 1
ERR: 1
ESO Big Diffs: 1
MTR Big Diffs: 1
Table Big Diffs: 1
Table String Diffs: 2
Table Small Diffs: 1

github-actions · 2026-02-18T17:19:39Z

⚠️ Regressions detected on macos-14 for commit `79da40f`

Regression Summary

EDD: 7
EIO: 1
ERR: 1
ESO Big Diffs: 1
MTR Big Diffs: 1
Table Big Diffs: 1
Table String Diffs: 2
Table Small Diffs: 1

…tialize Troof along with the other global vars.

github-actions · 2026-02-18T20:21:38Z

⚠️ Regressions detected on ubuntu-24.04 for commit `ed75617`

Regression Summary

EDD: 7
EIO: 1
ESO Big Diffs: 1
MTR Big Diffs: 1
Table Big Diffs: 1
Table String Diffs: 2
Table Small Diffs: 1

github-actions · 2026-02-18T20:24:08Z

⚠️ Regressions detected on macos-14 for commit `ed75617`

Regression Summary

EDD: 7
EIO: 1
ESO Big Diffs: 1
MTR Big Diffs: 1
Table Big Diffs: 1
Table String Diffs: 2
Table Small Diffs: 1

joseph-robertson · 2026-02-18T21:05:04Z

testfiles/_ResidentialBase.idf

  EnergyManagementSystem:ProgramCallingManager,
    central_ac_and_furnace_airloop_0_duct_program calling manager,  !- Name
-    EndOfSystemTimestepAfterHVACReporting,  !- EnergyPlus Model Calling Point
+    BeginZoneTimestepBeforeInitHeatBalance,  !- EnergyPlus Model Calling Point


Perhaps the changes could instead be:

central_ac_and_furnace_airloop_0_duct_program calling manager: EndOfSystemTimestepAfterHVACReporting -> EndOfSystemTimestepBeforeHVACReporting

attic_unvented_1_duct_leakage_imbalance_infil_program calling manager: BeginZoneTimestepAfterInitHeatBalance -> EndOfSystemTimestepAfterHVACReporting

infil_program calling manager: BeginZoneTimestepAfterInitHeatBalance -> EndOfSystemTimestepAfterHVACReporting

@shorowit?

After some local testing/diffing, it appears this approach causes a slightly larger regression than EndOfSystemTimestepAfterHVACReporting -> BeginZoneTimestepBeforeInitHeatBalance for central_ac_and_furnace_airloop_0_duct_program calling manager.

So I suppose the question is whether we want to avoid regression or whether we think there's actually an issue in how the programs are set up.

We can handle regressions if they are justified.

Sorry, I've been out of the office. I will take a look at this soon.

…tion marks for some error statements.

…rands global to avoid regressions.

joseph-robertson · 2026-02-20T18:03:59Z

testfiles/_ResidentialBase.idf

+  EnergyManagementSystem:GlobalVariable,
+    Qducts,    !- Erl Variable 1 Name
+    Qsupply,   !- Erl Variable 2 Name
+    Qexhaust;  !- Erl Variable 3 Name


So we can avoid EvaluateExpression errors during setup.

joseph-robertson · 2026-02-20T18:04:24Z

testfiles/HospitalBaselineReheatReportEMS.idf

+  EnergyManagementSystem:GlobalVariable,
+    A,  !- Erl Variable 1 Name
+    B,  !- Erl Variable 2 Name
+    C,  !- Erl Variable 3 Name
+    D,  !- <none>
+    E,  !- <none>
+    F,  !- <none>
+    G,  !- <none>
+    H,  !- <none>
+    I,  !- <none>
+    J,  !- <none>
+    K,  !- <none>
+    L,  !- <none>
+    M,  !- <none>
+    N,  !- <none>
+    O,  !- <none>
+    P,  !- <none>
+    Q,  !- <none>
+    R,  !- <none>
+    S,  !- <none>
+    T,  !- <none>
+    U,  !- <none>
+    V,  !- <none>
+    W,  !- <none>
+    X,  !- <none>
+    Y,  !- <none>
+    Z,  !- <none>
+    AA,  !- <none>
+    BB,  !- <none>
+    CC,  !- <none>
+    DD,  !- <none>
+    EE,  !- <none>
+    FF,  !- <none>
+    GG,  !- <none>
+    HH,  !- <none>
+    II;  !- <none>


So we can avoid EvaluateExpression errors during setup.

joseph-robertson · 2026-02-20T18:04:37Z

testfiles/RetailPackagedTESCoil.idf

+    DeltaT,                  !- Erl Variable 2 Name
+    ratioT,                  !- Erl Variable 3 Name


So we can avoid EvaluateExpression errors during setup.

github-actions · 2026-02-20T18:29:22Z

⚠️ Regressions detected on macos-14 for commit `98089b8`

Regression Summary

EDD: 7

github-actions · 2026-02-20T18:32:29Z

⚠️ Regressions detected on ubuntu-24.04 for commit `28bae0c`

Regression Summary

EDD: 7

github-actions · 2026-02-20T18:37:29Z

⚠️ Regressions detected on macos-14 for commit `28bae0c`

Regression Summary

EDD: 7

…/EnergyPlus into fix-ems-var-init-after-ref

mitchute · 2026-02-23T23:09:59Z

This looks like a good set of cleanups. We'll merge this next, assuming tests all are consistent with previous results.

github-actions · 2026-02-23T23:39:25Z

⚠️ Regressions detected on macos-14 for commit `8b146cb`

Regression Summary

EDD: 7

github-actions · 2026-02-24T00:12:41Z

⚠️ Regressions detected on ubuntu-24.04 for commit `8b146cb`

Regression Summary

EDD: 7

mitchute · 2026-02-24T14:28:31Z

All good here. Merging.

joseph-robertson added 2 commits January 29, 2026 16:00

Add failing EMS unit test to demonstrate that variable initialized af…

8623d71

…ter reference does not throw error.

Formatting.

ead50b6

joseph-robertson self-assigned this Jan 29, 2026

fix uninitialized var

65966b8

mitchute added the Defect Includes code to repair a defect in EnergyPlus label Jan 30, 2026

joseph-robertson commented Jan 30, 2026

View reviewed changes

Add test to show difference between calling ManageEMS individually vs…

d039752

… just ManageSimulation.

joseph-robertson commented Jan 30, 2026

View reviewed changes

joseph-robertson added 8 commits February 9, 2026 10:08

Add AlwaysFindSeriousError to EMS manager data struct.

69e2e71

Update EvaluateStack to use new AlwaysFindSeriousError.

c1c2bee

Update ManageSimulation to use new AlwaysFindSeriousError around Setu…

68543c1

…pSimulation.

Clean up new EMS variable unit tests.

cf65f57

Check for global variable instead of forcing error find.

9f9c099

Check for internal variable as well.

590e0ad

Formatting in new unit test.

836fd7e

Temporary debugging changes in some testfiles.

b0bb17c

joseph-robertson commented Feb 10, 2026

View reviewed changes

joseph-robertson added 2 commits February 11, 2026 15:55

Set Type and Error only if serious error found.

bf8e227

Minor calling point changes in a few testfiles.

9817171

joseph-robertson added 2 commits February 12, 2026 12:10

Remove extra EMS output from idf test files.

4d1b4aa

Add summary comments to EvaluateExpression around uninitialized error…

0ed3853

… throw.

joseph-robertson marked this pull request as ready for review February 16, 2026 18:22

joseph-robertson requested a review from mitchute February 16, 2026 18:24

Merge branch 'develop' into fix-ems-var-init-after-ref

fc9f8d1

mitchute reviewed Feb 17, 2026

View reviewed changes

For RetailPackagedTESCoil.idf, try moving only the Troof block above …

7ab44a1

…CalcBouyancyTerms.

Revert program changes in RetailPackagedTESCoil.idf; instead just ini…

00da99c

…tialize Troof along with the other global vars.

joseph-robertson commented Feb 18, 2026

View reviewed changes

joseph-robertson added 3 commits February 20, 2026 10:58

Elaborate EvaluateExpression explanation; add unrelated closing quota…

d60fe2c

…tion marks for some error statements.

Revert sample file calling point changes; instead, make offending ope…

58cddd5

…rands global to avoid regressions.

Merge branch 'develop' into fix-ems-var-init-after-ref

fa13d1c

joseph-robertson commented Feb 20, 2026

View reviewed changes

mitchute added 2 commits February 23, 2026 15:42

Merge branch 'develop' into fix-ems-var-init-after-ref

250d892

Merge branch 'fix-ems-var-init-after-ref' of github.com:NatLabRockies…

e729a79

…/EnergyPlus into fix-ems-var-init-after-ref

mitchute approved these changes Feb 23, 2026

View reviewed changes

mitchute merged commit 82a12e2 into develop Feb 24, 2026
13 of 14 checks passed

mitchute deleted the fix-ems-var-init-after-ref branch February 24, 2026 14:28

joseph-robertson mentioned this pull request Feb 26, 2026

EMS calling point BeginNewEnvironment not run during "Setup Simulation" #11440

Open

		" Set power_mult = site_temp_adj, !- Program Line 1",
		" Set site_temp_adj = 0.1, !- Program Line 2",

		if ((!state.dataGlobal->DoingSizing && !state.dataGlobal->KickOffSimulation && !state.dataEMSMgr->FinishProcessingUserInput) \|\|
		(!(thisErlVar.SetByGlobalVariable \|\| thisErlVar.SetByInternalVariable))) {

		DeltaT, !- Erl Variable 2 Name
		ratioT, !- Erl Variable 3 Name

Conversation

joseph-robertson commented Jan 29, 2026

Pull request overview

Description of the purpose of this PR

Pull Request Author

Reviewer

Uh oh!

mitchute commented Jan 30, 2026

Uh oh!

rraustad commented Jan 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

joseph-robertson commented Jan 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

joseph-robertson commented Jan 30, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

joseph-robertson commented Feb 6, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

joseph-robertson Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Feb 11, 2026

⚠️ Regressions detected on ubuntu-24.04 for commit f4e0687

Uh oh!

github-actions bot commented Feb 11, 2026

⚠️ Regressions detected on macos-14 for commit f4e0687

Uh oh!

github-actions bot commented Feb 11, 2026

⚠️ Regressions detected on ubuntu-24.04 for commit d1a8173

Uh oh!

github-actions bot commented Feb 11, 2026

⚠️ Regressions detected on macos-14 for commit d1a8173

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mitchute left a comment

Choose a reason for hiding this comment

Uh oh!

joseph-robertson commented Feb 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 18, 2026

⚠️ Regressions detected on ubuntu-24.04 for commit 79da40f

Uh oh!

github-actions bot commented Feb 18, 2026

⚠️ Regressions detected on macos-14 for commit 79da40f

Uh oh!

github-actions bot commented Feb 18, 2026

⚠️ Regressions detected on ubuntu-24.04 for commit ed75617

Uh oh!

github-actions bot commented Feb 18, 2026

⚠️ Regressions detected on macos-14 for commit ed75617

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

rraustad commented Jan 30, 2026 •

edited

Loading

joseph-robertson commented Jan 30, 2026 •

edited

Loading

joseph-robertson Feb 10, 2026 •

edited

Loading

⚠️ Regressions detected on ubuntu-24.04 for commit `f4e0687`

⚠️ Regressions detected on macos-14 for commit `f4e0687`

⚠️ Regressions detected on ubuntu-24.04 for commit `d1a8173`

⚠️ Regressions detected on macos-14 for commit `d1a8173`

joseph-robertson commented Feb 18, 2026 •

edited

Loading

⚠️ Regressions detected on ubuntu-24.04 for commit `79da40f`

⚠️ Regressions detected on macos-14 for commit `79da40f`

⚠️ Regressions detected on ubuntu-24.04 for commit `ed75617`

⚠️ Regressions detected on macos-14 for commit `ed75617`

⚠️ Regressions detected on macos-14 for commit `98089b8`

⚠️ Regressions detected on ubuntu-24.04 for commit `28bae0c`

⚠️ Regressions detected on macos-14 for commit `28bae0c`

⚠️ Regressions detected on macos-14 for commit `8b146cb`

⚠️ Regressions detected on ubuntu-24.04 for commit `8b146cb`