forgefirm

2 Commits

Include renames

Author SHA1 Message Date

Author	SHA1	Message	Date
ScottW514	520d62ac05	forgetest tests: the confirmed trims of the tool's own unit tests The cases that tested a mock, a timer, a wording or a table, or that replayed a judgment a host test already holds, leave forgetest/tests. What catches a false PASS, keeps the bench safe, or guards the gate stays. - test_baseline: the fake sysfs tree is a mixin with no test_ methods, so ExtensionFreeTests and BaselineModeTests no longer re-run BaselineTests' 25 cases (133 runs, now 45). CoolPublishTests, the lamp-fade cases and TransientNotLeftoverTests go; PositionDeadbandTests keeps a reading past the band and an unreadable reading, both never excused. Both latch-relock cases stay. - test_fixture: MdnsTests, the three timing cases, the probe's log wording, and nine prompt-routing variants go. A live test never runs unattended, the arm-press opt-in, the short-press edge, the presence press handing over the arm press, and the arm notice dropping at the press stay (35 cases, now 21). - test_cloud_suite: three false-PASS guards stay: the latch open at a dark print's button, a lid stop that is not edge-driven, the kernel refusing the resume. The guards for the latch unlocking in the hold and a paused print resuming left with their catalog tests in `6a434bb`. The rest go, with the harness pieces and the hunt-lid fixture only they read (41 cases, now 3). - test_cooling_suite: GateOffTests, CriticalTierTests, FanGateTests and FansQuietTests go with their harness; the flow verdict's log reads stay: only the text after the offset, never an older verdict before it (the flow-under-load false-PASS guard), a rotated log read whole. - test_queue: RunClockTests and three ordering cases go, and refusals are judged by a reason given, not its words; both live acknowledgment cases stay. - test_takeover_position: the six cases that judge the head and move nothing stay. - test_camera_home_return: the five cases where the head must not move stay, and so do the three that check the hand-back jog's direction and distance (homed, unhomed with the counters not counted twice, after cloud mode): a wrong sign or a double count drives the head into the gantry stops (15 cases, now 8). - test_server: the keep-alive and ETag cases, the takeover and scope half of the bench case, and the page's self-contained asserts (test_page.py's) go. - test_operator: the wording cases, the fixture case (test_fixture.py's) and JournalTests go. - test_mode: the supervisor timeout table goes. - test_takeover_client: the listener, the offline service back, the online client without the hunt, and GRBL under no marker stay. - test_responsiveness: PageTests and ImplementationCostTests go; the log cache keeps appends, a partial line, a replaced file and a fresh list, and the fingerprint cache a changed manifest and one with no content hash. - test_bench_registry: GfbenchTests and two description and argument pins go. - test_installer: the log-format and TLS-wording cases and InstallerShapeTests go; the die case checks the reason is in the log, not its format. - test_image: KernelIdentTests and the registration pin go. Each file's __main__ guard now ends the file, and the docstrings say what each still proves. Proof: each of the fifteen files passes under Linux as forgetest-ci discovers it, and pyflakes reports nothing new in them. Acceptance: none; test-only.	2026-10-13 20:29:25 -04:00
ScottW514	ef2390f7d4	forgetest: a takeover hands back the cloud client it found In cloud mode forgectrl's start at the end of a takeover starts a cloud client, and what that client is comes only from gfcloud's one-start markers, which the client that starts reads and takes down. The takeover started it bare: the online client, with the service's connect-time hunt. Seen on the bench with exthost.armed-freeze, which runs its print under the offline service and puts the setup record back under a takeover: the machine came back online in cloud mode, the hunt homed the head at 14:21:01, the run's result was written at 14:21:02, and the service sent a head move at 14:21:08, after the run had ended, where the next test's switch to GRBL mode would have cut it off. It also broke the harness's own rule that every cloud client start it makes comes up without the hunt. The takeover now reads, on entry, whether the running cloud client is the offline service: the client itself holds the listening socket at /run/gfcloud-offline.sock (hw.listens_on reads /proc/net/unix and the process's own descriptors, so a socket file another process left behind does not count). forgectrl's start is made under the no-hunt marker in cloud mode, and under the offline marker as well when the offline service was found. After the start the client that came up must listen on the offline socket within 60 s; a miss is recorded on the run's baseline capture and the post pass turns it into a leftover ("cloud client at the takeover end", not restored: a cloud test starts the client it needs), which fails the run. A marker no client read (the gate, standby, a fault) is taken down, so a later start never comes up under it. The judge never breaks the exit path. Proof: forgetest's unit tests pass on the host (481 OK). The new tests/test_takeover_client.py drives a real enter and exit against the fake forgectrl, a fake /proc, and an init script that plays gfcloud's start: the offline service comes back offline, an online client after it fails the run, a start that never happened takes the markers down, an online client comes back without the hunt, a stale socket file is not the offline service, GRBL mode starts under no marker. Negative controls: without the markers four of them fail, without the judge three. Bench drill on the bench reference with this package from /tmp: GRBL mode, the offline service started as enter_offline starts it (pid 4834), a takeover; the client forgectrl brought back (pid 4898) read both markers, logged "OFFLINE service", listened on the socket, and in the 10 s after had no web session, no hunt, and no motion. The bench was then handed back to GRBL mode as found. Acceptance: runner.py, baseline.py and hw.py are in no test's fingerprint, so no result moves; the catalog test that exercises the change is exthost.armed-freeze, whose takeover now fails the run unless the offline service comes back.	2026-09-25 10:45:24 -04:00

520d62ac05

forgetest tests: the confirmed trims of the tool's own unit tests

The cases that tested a mock, a timer, a wording or a table, or that
replayed a judgment a host test already holds, leave forgetest/tests.
What catches a false PASS, keeps the bench safe, or guards the gate
stays.

- test_baseline: the fake sysfs tree is a mixin with no test_ methods,
  so ExtensionFreeTests and BaselineModeTests no longer re-run
  BaselineTests' 25 cases (133 runs, now 45). CoolPublishTests, the
  lamp-fade cases and TransientNotLeftoverTests go; PositionDeadbandTests
  keeps a reading past the band and an unreadable reading, both never
  excused. Both latch-relock cases stay.
- test_fixture: MdnsTests, the three timing cases, the probe's log
  wording, and nine prompt-routing variants go. A live test never runs
  unattended, the arm-press opt-in, the short-press edge, the presence
  press handing over the arm press, and the arm notice dropping at the
  press stay (35 cases, now 21).
- test_cloud_suite: three false-PASS guards stay: the latch open at a
  dark print's button, a lid stop that is not edge-driven, the kernel
  refusing the resume. The guards for the latch unlocking in the hold
  and a paused print resuming left with their catalog tests in 6a434bb.
  The rest go, with the harness pieces and the hunt-lid fixture only
  they read (41 cases, now 3).
- test_cooling_suite: GateOffTests, CriticalTierTests, FanGateTests and
  FansQuietTests go with their harness; the flow verdict's log reads
  stay: only the text after the offset, never an older verdict before it
  (the flow-under-load false-PASS guard), a rotated log read whole.
- test_queue: RunClockTests and three ordering cases go, and refusals
  are judged by a reason given, not its words; both live
  acknowledgment cases stay.
- test_takeover_position: the six cases that judge the head and move
  nothing stay.
- test_camera_home_return: the five cases where the head must not move
  stay, and so do the three that check the hand-back jog's direction and
  distance (homed, unhomed with the counters not counted twice, after
  cloud mode): a wrong sign or a double count drives the head into the
  gantry stops (15 cases, now 8).
- test_server: the keep-alive and ETag cases, the takeover and scope
  half of the bench case, and the page's self-contained asserts
  (test_page.py's) go.
- test_operator: the wording cases, the fixture case (test_fixture.py's)
  and JournalTests go.
- test_mode: the supervisor timeout table goes.
- test_takeover_client: the listener, the offline service back, the
  online client without the hunt, and GRBL under no marker stay.
- test_responsiveness: PageTests and ImplementationCostTests go; the
  log cache keeps appends, a partial line, a replaced file and a fresh
  list, and the fingerprint cache a changed manifest and one with no
  content hash.
- test_bench_registry: GfbenchTests and two description and argument
  pins go.
- test_installer: the log-format and TLS-wording cases and
  InstallerShapeTests go; the die case checks the reason is in the log,
  not its format.
- test_image: KernelIdentTests and the registration pin go.

Each file's __main__ guard now ends the file, and the docstrings say what
each still proves.

Proof: each of the fifteen files passes under Linux as forgetest-ci
discovers it, and pyflakes reports nothing new in them.

Acceptance: none; test-only.

2026-10-13 20:29:25 -04:00

ScottW514

ef2390f7d4

forgetest: a takeover hands back the cloud client it found

In cloud mode forgectrl's start at the end of a takeover starts a cloud
client, and what that client is comes only from gfcloud's one-start
markers, which the client that starts reads and takes down. The takeover
started it bare: the online client, with the service's connect-time
hunt. Seen on the bench with exthost.armed-freeze, which runs its print
under the offline service and puts the setup record back under a
takeover: the machine came back online in cloud mode, the hunt homed the
head at 14:21:01, the run's result was written at 14:21:02, and the
service sent a head move at 14:21:08, after the run had ended, where the
next test's switch to GRBL mode would have cut it off. It also broke the
harness's own rule that every cloud client start it makes comes up
without the hunt.

The takeover now reads, on entry, whether the running cloud client is
the offline service: the client itself holds the listening socket at
/run/gfcloud-offline.sock (hw.listens_on reads /proc/net/unix and the
process's own descriptors, so a socket file another process left behind
does not count). forgectrl's start is made under the no-hunt marker in
cloud mode, and under the offline marker as well when the offline
service was found. After the start the client that came up must listen
on the offline socket within 60 s; a miss is recorded on the run's
baseline capture and the post pass turns it into a leftover ("cloud
client at the takeover end", not restored: a cloud test starts the
client it needs), which fails the run. A marker no client read (the
gate, standby, a fault) is taken down, so a later start never comes up
under it. The judge never breaks the exit path.

Proof: forgetest's unit tests pass on the host (481 OK). The new
tests/test_takeover_client.py drives a real enter and exit against the
fake forgectrl, a fake /proc, and an init script that plays gfcloud's
start: the offline service comes back offline, an online client after
it fails the run, a start that never happened takes the markers down,
an online client comes back without the hunt, a stale socket file is not
the offline service, GRBL mode starts under no marker. Negative
controls: without the markers four of them fail, without the judge
three. Bench drill on the bench reference with this package from /tmp:
GRBL mode, the offline service started as enter_offline starts it (pid
4834), a takeover; the client forgectrl brought back (pid 4898) read
both markers, logged "OFFLINE service", listened on the socket, and in
the 10 s after had no web session, no hunt, and no motion. The bench was
then handed back to GRBL mode as found.

Acceptance: runner.py, baseline.py and hw.py are in no test's
fingerprint, so no result moves; the catalog test that exercises the
change is exthost.armed-freeze, whose takeover now fails the run unless
the offline service comes back.

2026-09-25 10:45:24 -04:00