mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-28 09:11:11 -07:00
The service-protocol half of the cloud catalog on its own test: the cloud client restarted as gfutilities' emulator under the /run/gfcloud-emulate marker signs in, passes the firmware check, opens the WebSocket, answers the connect-time hunt and the image requests with the dev image's canned frames, and runs a print from the app through the real download path to ':completed' - nothing moves, nothing arms, and only the app has to be driven, by a person or an agent through the prompt API. The real client is restarted afterward and its hunt waited out. session_live now knows the emulator's session is not the machine's, so enter_cloud restarts it rather than reusing it; restart_client is the one restart the offline and emulator entries share. The dev image adds python3-gfutilities-emulator (the fixtures, packaged on their own in meta-openglow); forgefirm-app moves to 12ad3b1 (gfcloud --emulate). Catalog: 44 tests, 27 auto / 9 operator / 8 live; the new test covers the gfutilities service layer and examples/, which step 4 will take off the other cloud tests. Replays over the prompt script; contract and BRINGUP updated. A layer change (the dev image recipe): everything re-requires on the next image.
13 lines
660 B
PHP
13 lines
660 B
PHP
# forgefirm-app pin (python3-gfhardware repository, forgefirm-app/ tree).
|
|
# Bump deliberately (AUTOREV is not reproducible); keep 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). The python3-gfhardware recipe in
|
|
# meta-glowforge-bsp pins the same repository; move both together.
|
|
SRCREV = "12ad3b19166082c93b497a722cbb7a2fb91f810d"
|
|
|
|
# Bump PV with every SRCREV move: the hash-derived package version is not
|
|
# monotonic on its own and buildhistory QA fails the build when it sorts
|
|
# backwards.
|
|
PV = "0.1.18+git"
|