The coolant critical tier, with its catalog test

mirror of https://github.com/openglow-org/forgefirm.git synced 2026-09-27 08:41:13 -07:00

forgectrl pin a1875a8: cool_temp_critical_c (default 38 C) is the fail
tier above the coolant ceiling's pause: at or over it in a run session the
verdict is CRITICAL (fire blocked, hold, no resume this job), the fault
ends with the session, the settings API keeps it above the ceiling, and
its top turns the gate off.

Catalog: cooling.critical-tier (auto, 45 tests), driven through the
settings API like cooling.gate-off: a critical line at the ceiling is
refused (and undone should it ever be accepted); with the ceiling, the
resume gate and the critical line all under the coolant's temperature a
session reads CRITICAL rather than OVERTEMP with no resume and the reason
naming the tier and the coolant; after the session the ceiling alone
holds (OVERTEMP); with the critical line at its top the gate is off
(gates_off, the run-start log line) and the ceiling alone pauses;
restored, OK with nothing off. Four unit cases against a scripted engine.
_after_session takes the condition to wait for.

Docs: COOLING (verdict table, section 5, the settings table, the quick
reference), BRINGUP item 19 and the catalog count, the CAMPAIGN-LOG
paragraph for the fan-fault session rule on dev image 20260822145201.

This commit is contained in:

ScottW514

2026-08-22 11:41:18 -04:00

parent c1591e4f69

commit f51140e528

6 changed files with 304 additions and 9 deletions

									
										meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc
									
		+1
		-1
	
												View File
												
				@@ -2,5 +2,5 @@

				# only SRCREV and PV here - the image manifest leaves *-pin.inc out of the

				# layer content hash because the component entry already identifies the

				# pinned source (forgefirm-image-manifest.bbclass).

				SRCREV = "d51dbdbcc6b3a12d2f7963eb94514ce52493645f"

				SRCREV = "a1875a8113b45c42e252caa3e4b409c1ba4b39fe"

				PV = "0.1.0"