rb/d15-rig-agent
225
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
1e182a44e4 |
qemu: agent-test.sh counts a zombie child as killed (CI containers reap nothing)
ci / patches-apply (push) Successful in 1m1s
ci / test (pull_request) Successful in 9s
ci / kernel-build (pull_request) Skipped
ci / quality (pull_request) Successful in 28s
ci / mcdc (push) Successful in 35s
ci / bench (push) Successful in 7s
ci / test (push) Successful in 12s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / badges (push) Skipped
ci / qemu-tools (push) Successful in 2m21s
ci / bench (pull_request) Successful in 7s
ci / mcdc (pull_request) Successful in 35s
ci / kernel-symbols (push) Successful in 4m10s
ci / quality (push) Successful in 29s
ci / prune-artifacts (pull_request) Skipped
ci / qemu-tools (pull_request) Successful in 2m6s
ci / patches-apply (pull_request) Successful in 1m8s
ci / badges (pull_request) Skipped
ci / kernel-symbols (pull_request) Successful in 3m49s
Run 10403: under a CI job container's non-reaping PID 1 the script child the deadline killed stays a zombie, and kill -0 still found it. The check now reads the process state from /proc. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BdKQBQkJkq4zE7iPFMkAhS |
||
|
|
bbc91618f8 |
qemu: agent-test.sh passes shellcheck (SC2016 on the guest-side script)
ci / quality (push) Successful in 34s
ci / badges (push) Skipped
ci / bench (pull_request) Successful in 1m5s
ci / prune-artifacts (pull_request) Skipped
ci / quality (pull_request) Successful in 35s
ci / badges (pull_request) Skipped
ci / test (push) Successful in 8s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / mcdc (push) Successful in 34s
ci / bench (push) Successful in 5s
ci / qemu-tools (push) Failing after 50s
ci / patches-apply (push) Successful in 21s
ci / test (pull_request) Successful in 20s
ci / mcdc (pull_request) Successful in 55s
ci / qemu-tools (pull_request) Failing after 49s
ci / patches-apply (pull_request) Successful in 1m29s
ci / kernel-build (pull_request) Skipped
ci / kernel-symbols (push) Successful in 4m52s
ci / kernel-symbols (pull_request) Successful in 5m54s
The qemu-tools job (run 10385) failed shellcheck on the single-quoted script the test hands the agent: its expansions belong to the agent's shell, so the info finding is disabled on that line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BdKQBQkJkq4zE7iPFMkAhS |
||
|
|
579ac260ca |
qemu: rig agent, a framed guest shell on its own serial port (flare-edge M9 soak-lite)
ci / test (push) Successful in 10s
ci / patches-apply (push) Successful in 25s
ci / quality (push) Successful in 36s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 4m38s
ci / mcdc (push) Successful in 37s
ci / bench (push) Successful in 6s
ci / qemu-tools (push) Failing after 15s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / test (pull_request) Successful in 9s
ci / prune-artifacts (pull_request) Skipped
ci / mcdc (pull_request) Successful in 34s
ci / bench (pull_request) Successful in 20s
ci / kernel-build (pull_request) Skipped
ci / qemu-tools (pull_request) Failing after 57s
ci / patches-apply (pull_request) Successful in 1m16s
ci / kernel-symbols (pull_request) Successful in 2m14s
ci / badges (pull_request) Skipped
ci / quality (pull_request) Successful in 2m51s
run.sh --agent SOCK adds a third pci-serial after ctl and rs485 (their ttyS order is unchanged) and warden.agent on the command line. Stage-2 init then runs warden_agent (rootfs/etc/warden-lib.sh) on that port with echo off: `@run ID SECS B64` runs a script and answers <<BEGIN ID>>, the base64 of its output and <<END ID RC>>; `@chunk` pieces get past the 4095-byte cooked line; a script past its deadline is killed with its process group and answers 124 (the panel BusyBox has no timeout). It is the guest channel of flare-edge tools/soak/rig-qemu.py, which needs bus reads and writes, the clock and /proc inside the gate image. Rig rootfs only: no panel image carries it. Tests: qemu/tests/agent-test.sh (sh and busybox sh, in CI) and new run-sh-args-test.sh cases (agent last, warden.agent only with the flag). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BdKQBQkJkq4zE7iPFMkAhS |
||
|
|
0232823855 |
Merge pull request 'qemu: wait for the UI test hook to answer a ping before the first override (flare-edge#2602)' (#39) from rb/ln-hook-ready into rebuild
ci / prune-artifacts (push) Skipped
ci / test (push) Successful in 9s
ci / mcdc (push) Successful in 17s
ci / bench (push) Successful in 11s
ci / kernel-build (push) Skipped
ci / patches-apply (push) Successful in 46s
ci / quality (push) Successful in 1m39s
ci / badges (push) Skipped
ci / qemu-tools (push) Successful in 3m42s
ci / kernel-symbols (push) Successful in 7m49s
|
||
|
|
61ecfac844 |
qemu: wait for the UI test hook to answer a ping before the first override (flare-edge#2602)
ci / quality (pull_request) Successful in 1m43s
ci / badges (pull_request) Skipped
ci / test (push) Successful in 11s
ci / prune-artifacts (push) Skipped
ci / quality (push) Successful in 26s
ci / qemu-tools (push) Successful in 4m32s
ci / kernel-symbols (push) Successful in 5m22s
ci / bench (push) Successful in 11s
ci / mcdc (push) Successful in 21s
ci / kernel-build (push) Skipped
ci / badges (push) Skipped
ci / patches-apply (push) Successful in 54s
ci / mcdc (pull_request) Successful in 18s
ci / bench (pull_request) Successful in 15s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / patches-apply (pull_request) Successful in 40s
ci / qemu-tools (pull_request) Successful in 2m3s
ci / kernel-symbols (pull_request) Successful in 3m59s
ci / test (pull_request) Successful in 26s
Right after boot the UI is still taking the broker's retained replay under its per-tick bus budget, so a hook request queued behind it missed wthctl's 5 s bound and its own 5 s message expiry: the failsafe-ack flow's first override was lost, or applied with its reply lost. qmp.py now sends a run's first hook request only after the hook has answered a ping. ping changes nothing, so it is retried while the bridge reports no answer, up to HOOK_READY_S (90 s); the override itself goes out once. A hook that never answers stays a fatal step with its own message. Three offline tests in test_qmp_drive.py; removing the wait fails them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
ff3d1de088 |
Merge pull request 'qemu: let a job without the cross compiler use a prebuilt panel BusyBox (flare-edge#2210)' (#38) from rb/ln-rig-busybox-prebuilt into rebuild
ci / bench (push) Successful in 13s
ci / mcdc (push) Successful in 32s
ci / test (push) Successful in 9s
ci / kernel-build (push) Skipped
ci / kernel-symbols (push) Successful in 1m52s
ci / prune-artifacts (push) Skipped
ci / patches-apply (push) Successful in 32s
ci / quality (push) Successful in 1m13s
ci / badges (push) Skipped
ci / qemu-tools (push) Successful in 6m10s
|
||
|
|
8fc32976a5 |
qemu: clear the two shellcheck notes in the prebuilt BusyBox check (flare-edge#2210)
ci / mcdc (push) Successful in 34s
ci / kernel-build (push) Skipped
ci / quality (push) Successful in 46s
ci / bench (push) Successful in 12s
ci / test (push) Successful in 9s
ci / test (pull_request) Successful in 24s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / patches-apply (pull_request) Successful in 21s
ci / prune-artifacts (push) Skipped
ci / patches-apply (push) Successful in 41s
ci / bench (pull_request) Successful in 6s
ci / mcdc (pull_request) Successful in 29s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 1m48s
ci / qemu-tools (push) Successful in 5m39s
ci / quality (pull_request) Successful in 1m44s
ci / badges (pull_request) Skipped
ci / qemu-tools (pull_request) Successful in 3m42s
ci / kernel-symbols (pull_request) Successful in 6m55s
CI's shellcheck 0.9.0 failed qemu-tools on #38: SC2015 on the `[ -f ] && [ = ] || { ... }` refusal in qemu_get_busybox (now an if), and SC2012 on the `ls | head` that picks a patch to edit in busybox-panel-test.sh (now find | sort | head). No behaviour change. Refs flare-edge#2210 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
0c98a6018f |
Merge pull request 'qemu: build the panel's own BusyBox for the rig (flare-edge#2210)' (#37) from rb/ln-rig-busybox into rebuild
ci / quality (push) Successful in 1m17s
ci / badges (push) Skipped
ci / test (push) Successful in 9s
ci / patches-apply (push) Successful in 47s
ci / bench (push) Successful in 9s
ci / mcdc (push) Successful in 19s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / qemu-tools (push) Successful in 4m4s
ci / kernel-symbols (push) Successful in 6m39s
|
||
|
|
820af4baaa |
qemu: let a job without the cross compiler use a prebuilt panel BusyBox (flare-edge#2210)
ci / test (push) Successful in 7s
ci / bench (push) Successful in 9s
ci / mcdc (push) Successful in 22s
ci / patches-apply (push) Successful in 50s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / qemu-tools (push) Failing after 27s
ci / quality (push) Successful in 1m17s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 7m7s
ci / test (pull_request) Successful in 9s
ci / bench (pull_request) Successful in 11s
ci / mcdc (pull_request) Successful in 13s
ci / patches-apply (pull_request) Successful in 54s
ci / qemu-tools (pull_request) Failing after 11s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / quality (pull_request) Successful in 1m27s
ci / badges (pull_request) Skipped
ci / kernel-symbols (pull_request) Successful in 4m10s
The flare-edge flow jobs get the rig BusyBox from the image build job's artifact and have no cross compiler, so RIG_BUSYBOX=panel, which always ran build-busybox.sh, could not be used there. - qemu/lib.sh: qemu_busybox_panel_inputs, one sha256 over the source pin and every committed input under qemu/busybox/ (no compiler). With RIG_BUSYBOX=panel and BUSYBOX set, qemu_get_busybox takes that binary only when BUSYBOX.inputs equals the value for this tree; otherwise it fails closed. The source pin moved here from build-busybox.sh. - qemu/build-busybox.sh writes <binary>.inputs next to the binary (also on the up-to-date path) and removes a stale one before a rebuild. - busybox-panel-test.sh: missing, foreign and matching .inputs, a missing binary, and a config or patch edit changing the inputs. - CI qemu-tools: a panel initramfs from the prebuilt binary. Refs flare-edge#2210 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
37037926df |
qemu: build the panel's own BusyBox for the rig (flare-edge#2210)
ci / quality (push) Successful in 2m25s
ci / badges (push) Skipped
ci / mcdc (push) Successful in 29s
ci / prune-artifacts (push) Skipped
ci / test (push) Successful in 13s
ci / bench (push) Successful in 10s
ci / patches-apply (push) Successful in 24s
ci / kernel-build (push) Skipped
ci / mcdc (pull_request) Successful in 21s
ci / bench (pull_request) Successful in 17s
ci / test (pull_request) Successful in 14s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / qemu-tools (push) Successful in 4m32s
ci / kernel-symbols (push) Successful in 4m28s
ci / patches-apply (pull_request) Successful in 57s
ci / qemu-tools (pull_request) Successful in 3m8s
ci / kernel-symbols (pull_request) Successful in 6m42s
ci / quality (pull_request) Successful in 2m19s
ci / badges (pull_request) Skipped
The rig runs busybox.net's 1.31.0 multiarch binary, not the image's 1.37.0 with its applet config, so a script calling an applet or option the panel lacks (#1903 setpriv --reuid, #2002 stat, #1349 flock -w) passes in the rig and breaks on a panel. - qemu/busybox/panel.config: the image's config, rebuilt from Buildroot 2025.02.8 busybox.config plus 0001-busybox-applets.patch, resolved for 1.37.0 as Buildroot does. patches/: Buildroot's 11 busybox patches. rig.fragment: static link and BusyBox's own passwd readers only. applets.txt and help.txt: the bench a capture (image 417a66b). - qemu/build-busybox.sh: pinned 1.37.0 source, fails on any Kconfig rewrite of the config, an applet list other than the panel's, or a dynamic binary. - qemu/lib.sh: RIG_BUSYBOX=panel selects it (default stays multiarch); the bounded verified download is now qemu_fetch_verified. - warden.shell uses warden_console_shell: cttyhack where it exists, else setsid -c on the console tty (the panel's BusyBox has no cttyhack). - CI: offline tests in qemu-tools, a build there checked against every applet's --help from the panel through qemu-user, and a second boot smoke with the panel initramfs in kernel-build. Refs flare-edge#2210 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
4d30c3083b |
Merge pull request 'kernel: keep the arm32 vDSO clock off the virtual counter (#35)' (#36) from rb/ln-vdso-phys-counter into rebuild
ci / test (push) Successful in 8s
ci / mcdc (push) Successful in 29s
ci / patches-apply (push) Successful in 22s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / quality (push) Successful in 1m15s
ci / bench (push) Successful in 16s
ci / badges (push) Skipped
ci / qemu-tools (push) Successful in 4m1s
ci / kernel-symbols (push) Successful in 4m5s
|
||
|
|
b4596ed737 |
kernel: keep the arm32 vDSO clock off the virtual counter (#35)
ci / test (push) Successful in 31s
ci / bench (push) Successful in 14s
ci / mcdc (push) Successful in 26s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / quality (push) Successful in 1m18s
ci / badges (push) Skipped
ci / bench (pull_request) Successful in 10s
ci / patches-apply (push) Successful in 52s
ci / qemu-tools (push) Successful in 3m26s
ci / kernel-symbols (push) Successful in 5m12s
ci / test (pull_request) Successful in 8s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / badges (pull_request) Skipped
ci / qemu-tools (pull_request) Successful in 2m59s
ci / mcdc (pull_request) Successful in 19s
ci / patches-apply (pull_request) Successful in 52s
ci / quality (pull_request) Successful in 1m15s
ci / kernel-symbols (pull_request) Successful in 6m57s
On the RV1106 the boot firmware does not enter the kernel in HYP mode and leaves CNTVOFF non-zero. The DT timer node lists no virtual-timer PPI, so the kernel keeps time on the physical counter, while the arm32 vDSO always reads the virtual one: on bench a clock_gettime() ran 738.9 s ahead of the kernel clock (pure offset, -0.1 ppm over 30 s) and every absolute deadline taken from it expired minutes late (flare-edge#2319, the #2311 reset loop). New patch 82-arch-timer-vdso-phys-counter.patch: - rv1106.dtsi and rv1106-warden-m2.dts: the timer node carries arm,cpu-registers-not-fw-configured. The kernel keeps the physical timer it uses today, and arch/arm/kernel/vdso.c drops the vDSO clock symbols, so libc goes straight to the syscall. - arm_arch_timer.c: on arm32, a kernel on the physical counter without HYP mode sets the counter's vdso_clock_mode to VDSO_CLOCKMODE_NONE, the safety net for a device tree without the property. QEMU -M virt (virtual PPI present) is unchanged. tests/arch-timer/check-vdso-counter.py checks both guards in the patched tree; CI's patches-apply job runs it and its 12 regression cases. Fixes #35 Refs flare-edge#2319 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
4ff7c19537 |
Merge pull request 'qemu: ui-drive waits for the chain start on an init-chain boot (flare-edge#2295)' (#34) from rb/ln-init-chain-wait into rebuild
ci / test (push) Successful in 28s
ci / bench (push) Successful in 14s
ci / qemu-tools (push) Successful in 1m44s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / mcdc (push) Successful in 28s
ci / patches-apply (push) Successful in 47s
ci / quality (push) Successful in 1m28s
ci / kernel-symbols (push) Successful in 4m57s
ci / badges (push) Skipped
|
||
|
|
a9f2b9b26a |
qemu: ui-drive waits for the chain start on an init-chain boot (flare-edge#2295)
ci / test (pull_request) Successful in 24s
ci / mcdc (pull_request) Successful in 17s
ci / badges (push) Skipped
ci / test (push) Successful in 9s
ci / qemu-tools (push) Successful in 1m27s
ci / bench (pull_request) Successful in 5s
ci / mcdc (push) Successful in 12s
ci / bench (push) Successful in 5s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / patches-apply (push) Successful in 43s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / patches-apply (pull_request) Successful in 24s
ci / quality (pull_request) Successful in 2m35s
ci / kernel-symbols (pull_request) Successful in 5m7s
ci / quality (push) Successful in 1m28s
ci / qemu-tools (pull_request) Successful in 1m36s
ci / badges (pull_request) Skipped
ci / kernel-symbols (push) Successful in 5m2s
ui-drive.sh --init-chain boots with warden.initchain, where sbin/init starts the UI through the panel's S99lvgl and prints "init: chain started N script(s)"; the direct-start line "init: starting warden-ui" is never printed. ui-drive.sh still waited for that line, so the first flare-edge "QEMU UI shipped init chain" run (job 99350) gave "warden-ui never started" after 180 s on a chain that had booted cleanly. The wait moves to qemu/tests/ui-start.sh (sourced by ui-drive.sh and ui-shot.sh): wait_ui_started picks the marker by mode and, on a chain boot, fails at once on WARDEN-QEMU-INITCHAIN-EMPTY or a failed S99lvgl instead of at the deadline. Tests: new qemu/tests/ui-start-test.sh (27 checks, in CI): every marker is the one sbin/init or warden-lib.sh prints in that mode, the job 99350 console counts as started in chain mode, empty and failed chains fail fast, a dead VM and a silent console fail with their own messages, and both drivers wait through the helper. The old ui-drive.sh fails 4 checks. Fixes flare-edge#2295 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
6e51f1a0e5 |
Merge pull request 'qemu: ui-drive --init-chain and the assert_ui_chain verb (flare-edge#2210)' (#33) from rb/ln-init-chain-boot into rebuild
ci / test (push) Successful in 27s
ci / bench (push) Successful in 5s
ci / mcdc (push) Successful in 14s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / patches-apply (push) Successful in 22s
ci / qemu-tools (push) Successful in 2m58s
ci / quality (push) Successful in 58s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 7m35s
|
||
|
|
333c237949 |
Merge remote-tracking branch 'origin/rebuild' into rb/ln-init-chain-boot
ci / test (push) Skipped
ci / mcdc (push) Skipped
ci / bench (push) Skipped
ci / qemu-tools (push) Skipped
ci / kernel-symbols (push) Skipped
ci / patches-apply (push) Skipped
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / quality (push) Skipped
ci / badges (push) Skipped
ci / bench (pull_request) Successful in 20s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / quality (pull_request) Successful in 42s
ci / test (pull_request) Successful in 15s
ci / mcdc (pull_request) Successful in 1m3s
ci / kernel-symbols (pull_request) Successful in 5m24s
ci / qemu-tools (pull_request) Successful in 1m58s
ci / patches-apply (pull_request) Successful in 31s
ci / badges (pull_request) Skipped
|
||
|
|
f46a3519aa |
Merge pull request 'qemu: boot the UI through the panel shipped init chain (flare-edge#2210)' (#32) from rb/ln-init-chain into rebuild
ci / test (push) Successful in 17s
ci / qemu-tools (push) Successful in 3m14s
ci / patches-apply (push) Successful in 50s
ci / bench (push) Successful in 6s
ci / mcdc (push) Successful in 23s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / quality (push) Successful in 37s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 2m3s
|
||
|
|
f04a31dc06 |
qemu: ui-drive --init-chain and the assert_ui_chain verb (flare-edge#2210)
ci / qemu-tools (push) Successful in 3m26s
ci / test (push) Successful in 25s
ci / bench (push) Successful in 18s
ci / mcdc (push) Successful in 32s
ci / quality (push) Successful in 35s
ci / badges (push) Skipped
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / patches-apply (push) Successful in 24s
ci / kernel-symbols (push) Successful in 5m45s
ui-drive.sh --init-chain DIR lays the panel's scripts over the rootfs (ROOTFS_OVERLAY) and boots with warden.initchain; it refuses a missing directory or one without etc/init.d/S99lvgl before anything is built. qmp.py assert_ui_chain [ACCOUNT] reads the guest over the control channel (@procs, @cat) and fails unless exactly one warden-ui and one warden-ui-run loop run, the UI's real, effective, saved and filesystem uids are all the account's (never 0), the safe-mode flag is absent and /tmp/warden-ui.log holds no exit or refusal of warden-ui-run. tests/scripts/init-chain-ui.txt runs it at about T+120 s. Tests: UiChainVerb in test_qmp_drive.py (12 cases, among them the #1903 case: no UI, safe mode, three exits); 6 of 6 mutants caught. rootfs-overlay.sh gains the three ui-drive.sh --init-chain checks. Refs flare-edge#2210 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
a4bbfbd83b |
qemu: boot the UI through the panel's shipped init chain (flare-edge#2210)
ci / prune-artifacts (push) Skipped
ci / patches-apply (push) Successful in 24s
ci / bench (pull_request) Successful in 16s
ci / test (push) Successful in 24s
ci / mcdc (push) Successful in 29s
ci / kernel-build (push) Skipped
ci / test (pull_request) Successful in 10s
ci / quality (push) Successful in 39s
ci / badges (push) Skipped
ci / mcdc (pull_request) Successful in 30s
ci / bench (push) Successful in 10s
ci / qemu-tools (push) Successful in 3m16s
ci / qemu-tools (pull_request) Successful in 2m34s
ci / kernel-symbols (pull_request) Successful in 1m54s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / patches-apply (pull_request) Successful in 55s
ci / quality (pull_request) Successful in 1m36s
ci / badges (pull_request) Skipped
ci / kernel-symbols (push) Successful in 4m24s
The rig's stage-2 init starts /usr/bin/warden-ui directly as root, so it never ran S03warden-accounts, S99lvgl or warden-ui-run: no privilege drop, respawn loop or safe mode was exercised, and the BusyBox setpriv bug of flare-edge #1903 left every rebuild image without a UI while CI was green. - mkimage.sh: ROOTFS_OVERLAY lays a directory of panel files over the rootfs of both slots, modes kept. Only etc/ and usr/ at its top, no symlinks; a refused overlay writes no image. - sbin/init: with warden.initchain on the command line it runs /etc/init.d/S00-S09 before the bus and S10-S99 after the payload daemons, in place of the direct UI start (warden_init_chain in warden-lib.sh). The splash handover is marked done and warden-ui-run gets "-b fbdev". A chain boot without scripts prints WARDEN-QEMU-INITCHAIN-EMPTY and starts no UI. - warden_rig_bus_owners: when the accounts exist, cred/ui belongs to warden-ui and the cred directory to group warden-bus, as S10bus does. - Tests: init-chain-test.sh (19 checks, also under busybox sh) and rootfs-overlay.sh (17 scenarios, images read back with debugfs), both in CI. Refs flare-edge#2210 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
7d5686e287 |
Merge pull request 'qemu: PAYLOAD_DIR lets one run boot its own payload set' (#31) from rb/ln-hook-payload into rebuild
ci / qemu-tools (push) Successful in 1m32s
ci / test (push) Successful in 21s
ci / mcdc (push) Successful in 23s
ci / patches-apply (push) Successful in 21s
ci / badges (push) Skipped
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / bench (push) Successful in 17s
ci / quality (push) Successful in 1m25s
ci / kernel-symbols (push) Successful in 4m58s
|
||
|
|
de1b973aa4 |
Merge remote-tracking branch 'origin/rebuild' into rb/ln-hook-payload
ci / test (pull_request) Successful in 33s
ci / kernel-build (pull_request) Skipped
ci / patches-apply (pull_request) Successful in 44s
ci / mcdc (push) Skipped
ci / bench (push) Skipped
ci / test (push) Skipped
ci / patches-apply (push) Skipped
ci / kernel-build (push) Skipped
ci / qemu-tools (push) Skipped
ci / kernel-symbols (push) Skipped
ci / prune-artifacts (push) Skipped
ci / quality (push) Skipped
ci / badges (push) Skipped
ci / mcdc (pull_request) Successful in 26s
ci / bench (pull_request) Successful in 9s
ci / quality (pull_request) Successful in 2m10s
ci / prune-artifacts (pull_request) Skipped
ci / qemu-tools (pull_request) Successful in 2m36s
ci / badges (pull_request) Skipped
ci / kernel-symbols (pull_request) Successful in 4m29s
|
||
|
|
bd4eb5c201 |
Merge pull request 'qemu: drive a flow override step through the UI test hook' (#29) from rb/ln-hook-override into rebuild
ci / mcdc (push) Successful in 29s
ci / quality (push) Successful in 1m45s
ci / badges (push) Skipped
ci / test (push) Successful in 9s
ci / bench (push) Successful in 17s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / kernel-symbols (push) Successful in 4m51s
ci / qemu-tools (push) Successful in 1m8s
ci / patches-apply (push) Successful in 56s
|
||
|
|
eebfd23a96 |
qemu: test_qmp_drive.py removes its temp dirs (Fixes #30)
ci / mcdc (push) Successful in 13s
ci / bench (push) Successful in 5s
ci / prune-artifacts (push) Skipped
ci / test (push) Successful in 10s
ci / qemu-tools (push) Successful in 1m22s
ci / kernel-build (push) Skipped
ci / patches-apply (push) Successful in 48s
ci / quality (push) Successful in 57s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 4m7s
Every temp dir the module makes (a drive's out dir per run_script, the console and QMP socket dirs) now lands under one root per run, removed at exit; a run used to leave about 40 dirs in $TMPDIR. TempDirs runs one test of each kind in a child under a fresh TMPDIR and checks it is empty after. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
06b86e68b4 |
qemu: payload-dir.sh uses if blocks (shellcheck SC2015)
ci / test (push) Successful in 19s
ci / bench (push) Successful in 13s
ci / quality (push) Successful in 1m35s
ci / badges (push) Skipped
ci / mcdc (push) Successful in 14s
ci / qemu-tools (push) Successful in 2m47s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / patches-apply (push) Successful in 39s
ci / kernel-symbols (push) Canceled after 4m16s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
9998182ef5 |
qemu: PAYLOAD_DIR lets one run boot its own payload set
ci / kernel-build (push) Canceled after 0s
ci / quality (push) Canceled after 0s
ci / badges (push) Canceled after 0s
ci / test (push) Canceled after 0s
ci / mcdc (push) Canceled after 0s
ci / bench (push) Canceled after 0s
ci / qemu-tools (push) Canceled after 0s
ci / kernel-symbols (push) Canceled after 0s
ci / patches-apply (push) Canceled after 0s
ci / prune-artifacts (push) Canceled after 0s
mkimage.sh copies PAYLOAD_DIR (default qemu/payload) into /usr/bin of both slots and fails closed when it is not a directory; ui-drive.sh checks for warden-ui in the same directory. flare-edge boots the hook set (production payload plus the test-flavor UI and wthctl) for a flow that pins documents while the other flows of a batch keep reading qemu/payload (flare-edge#2054). qemu/tests/payload-dir.sh builds the images on a copy of qemu/ and reads both rootfs slots back with debugfs; wired into CI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
dd15eac1a8 |
qemu: drive a flow's override step through the UI test hook
ci / kernel-build (push) Skipped
ci / patches-apply (push) Successful in 59s
ci / test (pull_request) Successful in 29s
ci / bench (pull_request) Successful in 5s
ci / bench (push) Successful in 13s
ci / qemu-tools (push) Successful in 1m56s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / patches-apply (pull_request) Successful in 1m5s
ci / kernel-symbols (push) Successful in 4m0s
ci / quality (pull_request) Successful in 1m51s
ci / test (push) Successful in 15s
ci / mcdc (push) Successful in 30s
ci / prune-artifacts (push) Skipped
ci / mcdc (pull_request) Successful in 30s
ci / qemu-tools (pull_request) Successful in 1m18s
ci / badges (pull_request) Skipped
ci / quality (push) Successful in 2m5s
ci / badges (push) Skipped
ci / kernel-symbols (pull_request) Successful in 5m14s
flowc compiles a flow's `override` action to `override TOPIC DOC|null`, and a test-flavor warden-ui answers the override verb on test/req/ui, but the rig driver had no such verb and the control bridge only reached the UI's old FIFO, so a flow using it failed with an unknown command (flare-edge #2054). qmp.py `override` sends the request through the control bridge: the args JSON in `@hookdoc` / `@hookdoc+` pieces of 2000 bytes (the ctl port is a cooked tty that cuts a line at 4095 bytes; a document may be 16 KiB), then `@hook override`. The bridge runs the payload's wthctl as bus user testhook and answers its reply. ok:true passes, ok:false fails with the hook's err, and a request that never reached the hook (no client, no bus, no reply, a reply that is not a hook envelope) is fatal. The rig bus writes a testhook credential. Only plain words reach the client. ctl-bridge-test.sh covers the pieces, single use of the args, the word filter, ok:false, no reply and no client, now also under busybox sh in CI; test_qmp_drive.py covers the verb's ok, fail and fatal rows. Refs flare-edge #2054. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
eeb779b41b |
Merge pull request 'qemu: start the device bus when the payload carries a broker' (#28) from rb/lf-rig-bus into rebuild
ci / mcdc (push) Successful in 31s
ci / prune-artifacts (push) Skipped
ci / patches-apply (push) Successful in 52s
ci / quality (push) Successful in 31s
ci / test (push) Successful in 24s
ci / bench (push) Successful in 14s
ci / badges (push) Skipped
ci / qemu-tools (push) Successful in 2m8s
ci / kernel-build (push) Skipped
ci / kernel-symbols (push) Successful in 6m0s
|
||
|
|
5494b87dc3 |
qemu: start the device bus when the payload carries a broker
ci / test (push) Successful in 28s
ci / prune-artifacts (push) Skipped
ci / patches-apply (push) Successful in 1m2s
ci / mcdc (push) Successful in 29s
ci / bench (push) Successful in 12s
ci / mcdc (pull_request) Successful in 11s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / kernel-build (push) Skipped
ci / quality (push) Successful in 27s
ci / badges (push) Skipped
ci / qemu-tools (pull_request) Successful in 1m9s
ci / patches-apply (pull_request) Successful in 57s
ci / test (pull_request) Successful in 26s
ci / bench (pull_request) Successful in 16s
ci / quality (pull_request) Successful in 1m29s
ci / kernel-symbols (pull_request) Successful in 6m50s
ci / qemu-tools (push) Successful in 2m15s
ci / kernel-symbols (push) Successful in 4m42s
ci / badges (pull_request) Skipped
A panel runs one mosquitto on /run/warden/bus/bus.sock (flare-edge S10bus) and every daemon and the UI talk over it; the rig had no broker, so the Rust warden-modbus and the UI's bus client could not run there (flare-edge #1754, the #1050 QEMU half). Stage-2 init now starts the broker before the payload daemons when the payload carries a static mosquitto, with the panel's paths: the socket under sock/ with the bus.sock link, and a fresh 0400 credential file per bus user under cred/. The rig broker takes any user and loads no plugin (the rig is a test instrument; a static broker loads none). A payload without a broker boots as before. qemu/tests/init-rig-bus-test.sh covers no broker, a listening broker (layout, modes, config), a broker that exits or never listens, bad user names and the init order, under sh and busybox sh; with WARDEN_TEST_MOSQUITTO_DIR a real mosquitto carries a message between two users logged in by credential file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
13cd0c63be |
Merge pull request 'qemu: name the cause when warden-ui stops answering a flow' (#26) from rb/ln-stall-diag into rebuild
ci / test (push) Successful in 17s
ci / bench (push) Successful in 16s
ci / kernel-build (push) Skipped
ci / patches-apply (push) Successful in 1m0s
ci / mcdc (push) Successful in 35s
ci / quality (push) Successful in 2m33s
ci / badges (push) Skipped
ci / prune-artifacts (push) Skipped
ci / qemu-tools (push) Successful in 2m16s
ci / kernel-symbols (push) Successful in 2m42s
|
||
|
|
d279bc4c9f |
Merge pull request 'qemu, build: bound the busybox and kernel fetches' (#27) from rb/lc2-fix-1588 into rebuild
ci / test (push) Successful in 28s
ci / mcdc (push) Successful in 39s
ci / kernel-build (push) Skipped
ci / bench (push) Successful in 19s
ci / qemu-tools (push) Successful in 2m54s
ci / patches-apply (push) Successful in 56s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 8m3s
ci / prune-artifacts (push) Skipped
ci / quality (push) Successful in 1m56s
|
||
|
|
44b96074ed |
qemu, build: bound the busybox and kernel fetches
ci / kernel-symbols (push) Successful in 7m23s
ci / bench (pull_request) Successful in 31s
ci / mcdc (pull_request) Successful in 38s
ci / patches-apply (pull_request) Successful in 59s
ci / kernel-symbols (pull_request) Successful in 5m20s
ci / bench (push) Successful in 34s
ci / patches-apply (push) Successful in 1m6s
ci / qemu-tools (push) Successful in 2m37s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / qemu-tools (pull_request) Successful in 2m46s
ci / test (push) Successful in 40s
ci / mcdc (push) Successful in 33s
ci / test (pull_request) Successful in 43s
ci / quality (push) Successful in 1m56s
ci / badges (push) Skipped
ci / quality (pull_request) Successful in 1m27s
ci / badges (pull_request) Skipped
qemu_get_busybox and fetch-kernel-tarball.sh ran curl with no connect timeout, stall limit or total cap. A server that answered and then went silent held the flare-edge QEMU UI gate build job until its 30 minute timeout, with no retry (flare-edge #1588, run 7391 job 63953). - qemu/lib.sh: each attempt gives up below 1 KiB/s for 20 s, or after 60 s in all; curl retries once, the 3-attempt loop stays. Limits are overridable through BB_FETCH_* for the tests. - build/fetch-kernel-tarball.sh: 20 s connect timeout, abort below 10 KiB/s for 30 s, 600 s cap. The download lands in a temp file and is renamed on success, so a failed fetch no longer leaves a partial tarball that the next run takes as present and rejects on its sha256. - Tests: busybox-fetch.sh serves a stalling local HTTP endpoint to the real curl (hung for the full 60 s guard before, fails in about 9 s after); new tests/fetch-kernel-tarball suite (bounded argv, no partial file, refetch after a failure, reuse of a matching tarball; 6 of 9 checks red before). Both wired into CI and shellcheck. Refs blueflare/flare-edge#1588 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
b7be6f7fbe |
qemu: name the cause when warden-ui stops answering a flow
ci / patches-apply (pull_request) Successful in 52s
ci / mcdc (push) Successful in 32s
ci / test (push) Successful in 24s
ci / kernel-build (pull_request) Skipped
ci / bench (push) Successful in 14s
ci / qemu-tools (push) Successful in 2m29s
ci / prune-artifacts (push) Skipped
ci / test (pull_request) Successful in 24s
ci / quality (push) Successful in 1m52s
ci / mcdc (pull_request) Successful in 31s
ci / bench (pull_request) Successful in 18s
ci / kernel-build (push) Skipped
ci / patches-apply (push) Successful in 52s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 5m55s
ci / qemu-tools (pull_request) Successful in 2m6s
ci / prune-artifacts (pull_request) Skipped
ci / quality (pull_request) Successful in 1m38s
ci / badges (pull_request) Skipped
ci / kernel-symbols (pull_request) Successful in 6m17s
flare-edge #1528: on the lenovo QEMU runner warden-ui stopped answering for 30 to 60 s at a time (bridge no-reply, presses not consumed) and then recovered. Re-run jobs lose their failed-flow artifacts, so nothing showed whether the host starved the VM, the guest CPU was saturated, the guest waited on I/O, or warden-ui was blocked in an idle guest. qmp.py drive() now probes the first three such failures of a run: over 2 s it samples host load and PSI, the VM's vCPU thread CPU (query-cpus-fast thread-id), the guest /proc/stat and every guest process's stat line, and appends one line to the step's detail (verdict, numbers, top guest processes, processes in D state). The detail reaches the job log, so the answer survives a re-run. The control bridge answers the new `@procs` command itself, so the probe works while the UI is stuck. Tests: test_qmp_drive.py StallProbe (parsers, verdicts, CPU deltas, the vCPU thread sampler, a bounded probe on no-reply steps and none on a plain mismatch); ctl-bridge-test.sh checks `@procs` with no UI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
7d18896a0d |
Merge pull request 'qemu: control bridge waits out a slow UI and never hands on a late reply' (#25) from rb/ln-ctl-bridge into rebuild
ci / test (push) Successful in 45s
ci / mcdc (push) Successful in 32s
ci / bench (push) Successful in 18s
ci / qemu-tools (push) Successful in 2m6s
ci / patches-apply (push) Successful in 1m5s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / quality (push) Successful in 1m47s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 11m1s
|
||
|
|
b94fd156b4 |
qemu: control bridge waits out a slow UI and never hands on a late reply
ci / test (push) Successful in 2m34s
ci / mcdc (push) Successful in 48s
ci / bench (push) Successful in 25s
ci / qemu-tools (push) Successful in 4m5s
ci / patches-apply (push) Successful in 2m26s
ci / quality (push) Successful in 1m36s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / kernel-symbols (push) Successful in 7m19s
ci / badges (push) Skipped
ci / mcdc (pull_request) Successful in 56s
ci / bench (pull_request) Successful in 17s
ci / test (pull_request) Successful in 2m29s
ci / patches-apply (pull_request) Successful in 1m25s
ci / qemu-tools (pull_request) Successful in 4m54s
ci / quality (pull_request) Successful in 2m16s
ci / badges (pull_request) Skipped
ci / kernel-symbols (pull_request) Successful in 5m57s
The bridge waited 5 s for warden-ui's reply. On the lenovo QEMU host a page build outran it: the bridge answered an empty reply, and the UI's late reply then landed after the next command's remove and was read as that command's answer (flare-edge#1448: "page is ''", a nav answered with the previous hit). The loop moves to warden_ctl_bridge in etc/warden-lib.sh so a host test reaches it. The wait is 30 s (WARDEN_CTL_WAIT_S); a timeout answers "bridge: no reply from warden-ui ...", which qmp.py raises as a rig fault, and the next command first drains the late reply. Replies slower than 5 s are logged on the console with their time. qmp.py's control socket timeout is 90 s so it outlasts the bridge's wait. Tests: qemu/tests/ctl-bridge-test.sh (new, in CI), test_qmp_drive.py. Refs flare-edge#1448 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
f435a7d665 |
Merge pull request 'qemu: power-signal test waits for the trap install (rebuild)' (#23) from rb/lf-fix-sdk22 into rebuild
ci / test (push) Successful in 9s
ci / mcdc (push) Successful in 15s
ci / qemu-tools (push) Successful in 52s
ci / patches-apply (push) Successful in 22s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / quality (push) Successful in 30s
ci / badges (push) Skipped
ci / bench (push) Successful in 9s
ci / kernel-symbols (push) Successful in 2m33s
|
||
|
|
be4ad86230 |
qemu: power-signal test waits for the trap install (#22)
ci / mcdc (pull_request) Successful in 16s
ci / test (push) Successful in 10s
ci / mcdc (push) Successful in 17s
ci / bench (push) Successful in 5s
ci / qemu-tools (push) Successful in 50s
ci / patches-apply (push) Successful in 24s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / kernel-symbols (push) Successful in 2m40s
ci / test (pull_request) Successful in 9s
ci / quality (push) Successful in 34s
ci / badges (push) Skipped
ci / bench (pull_request) Successful in 7s
ci / qemu-tools (pull_request) Successful in 54s
ci / prune-artifacts (pull_request) Skipped
ci / patches-apply (pull_request) Successful in 27s
ci / kernel-symbols (pull_request) Successful in 2m30s
ci / kernel-build (pull_request) Skipped
ci / quality (pull_request) Successful in 44s
ci / badges (pull_request) Skipped
init-power-signals-test.sh slept a fixed 0.5 s before sending each signal. On a loaded runner the shell had not installed its traps yet, so SIGTERM took its default action and the case failed with nothing written. Each case now polls /proc/<pid>/status until SigCgt has the signal's bit (10 s hang backstop, WARDEN_TEST_TRAP_WAIT_S), and fails clearly if the handler never appears. Regression: a case whose handler install is held back 1.5 s (fails on the old fixed sleep), plus a check that the wait gives up on a shell without a handler. Fixes #22 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
aadf0e7f07 |
Merge pull request 'qemu: input consumption wait is a hang backstop (flare-edge#1138)' (#20) from rb/lf-fix-1138 into rebuild
ci / test (push) Successful in 12s
ci / bench (push) Successful in 8s
ci / patches-apply (push) Successful in 24s
ci / mcdc (push) Successful in 20s
ci / qemu-tools (push) Successful in 1m12s
ci / quality (push) Successful in 31s
ci / kernel-symbols (push) Successful in 2m15s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / badges (push) Skipped
|
||
|
|
6f931bf3ad |
qemu: input consumption wait is a hang backstop (flare-edge#1138)
ci / bench (push) Successful in 8s
ci / qemu-tools (push) Successful in 57s
ci / patches-apply (push) Successful in 23s
ci / test (push) Successful in 12s
ci / mcdc (push) Successful in 21s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / quality (push) Successful in 55s
ci / kernel-symbols (push) Successful in 2m45s
ci / kernel-symbols (pull_request) Successful in 2m17s
ci / badges (push) Skipped
ci / qemu-tools (pull_request) Successful in 55s
ci / patches-apply (pull_request) Successful in 24s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / quality (pull_request) Successful in 28s
ci / badges (pull_request) Skipped
ci / test (pull_request) Successful in 11s
ci / bench (pull_request) Successful in 6s
ci / mcdc (pull_request) Successful in 13s
The runner waited 2 s for the guest to count an injected press or release. On a loaded runner the release that opens the drawer took longer, so navigation/drawer-drag-release-policy failed both attempts although the UI handled the swipe. The wait is now a 20 s hang backstop; a wait over 2 s still passes and puts "slow guest: input consumed after N s" in the step's detail. Regression: test_swipe_release_counted_late_on_a_loaded_guest_passes (release counted 2.5 s after the drag; fails with the 2 s bound), plus a prompt-release case and a never-counted case bounded by the backstop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KerYPVh72hhNgKi3wS5ijG |
||
|
|
5507842878 |
Merge pull request 'Single M0 kernel batch with CONFIG_SUSPEND off' (#17) from rb/w04-kernel-options into rebuild
ci / kernel-symbols (push) Successful in 1m40s
ci / patches-apply (push) Successful in 15s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / quality (push) Successful in 25s
ci / badges (push) Skipped
ci / test (push) Successful in 8s
ci / mcdc (push) Successful in 13s
ci / bench (push) Successful in 5s
ci / qemu-tools (push) Successful in 46s
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkkrebuild-m0-20261010 |
||
|
|
35dc64714e |
kernel: probe V3 passed, the hardware RNG symbols are required
ci / qemu-tools (pull_request) Successful in 50s
ci / patches-apply (pull_request) Successful in 26s
ci / mcdc (push) Successful in 18s
ci / patches-apply (push) Successful in 24s
ci / test (push) Successful in 11s
ci / bench (push) Successful in 8s
ci / qemu-tools (push) Successful in 50s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / kernel-symbols (push) Successful in 2m21s
ci / test (pull_request) Successful in 12s
ci / quality (push) Successful in 33s
ci / badges (push) Skipped
ci / mcdc (pull_request) Successful in 17s
ci / bench (pull_request) Successful in 7s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
ci / quality (pull_request) Successful in 34s
ci / badges (pull_request) Skipped
ci / kernel-symbols (pull_request) Successful in 2m20s
Probe V3 (d09 T14, AT-M0-33) on the bench panel with the batch kernel: /dev/hwrng from the rockchip-rng driver, a 2.6 MB read in 2.4 s (1058 KiB/s) without blocking, and 1 FIPS 140-2 failure in 1000 blocks (limit 3). CONFIG_HW_RANDOM and CONFIG_HW_RANDOM_ROCKCHIP move from probe-symbols.txt to required-symbols.txt; the probe list is now empty, which build-kernel.sh accepts (it skips an empty probe list; the required list may never be empty). The config does not change: the defconfig already built both in, and the digest stays ec276f77. Regression tests (run-required-symbols-tests.sh): both symbols asserted and built in, a config without either is refused by name, the probe list may be empty. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkk |
||
|
|
cf72a6dcbc |
kernel: make KCONFIG_SHA256 independent of the host python (bfe-core1106-sdk#19)
DRM_MSM_VALIDATE_XML depended on `$(PYTHON3) -c "import lxml"`, so the expanded .config gained a line on hosts where python3 could import lxml and the whole-file digest differed (the flashed image ec276f77 against e8e9ef1c from a config-only run on the same tree). Drop the unused Qualcomm symbol with a one-block Kconfig patch; the digest is now ec276f77 everywhere and equals the flashed one. Regression test: tests/required-symbols/run-config-determinism-tests.sh runs the config-only expansion with a python3 whose import lxml works and one where it fails and requires the same digest; it is proven red on a copy of the tree without the patch. The kernel-symbols CI job runs it. Fixes #19. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkk |
||
|
|
0589829619 |
qemu init: read the command line without for-in-cat (blueflare/bfe-core1106-sdk#18)
ci / test (push) Canceled after 0s
ci / mcdc (push) Canceled after 0s
ci / bench (push) Canceled after 0s
ci / bench (pull_request) Canceled after 0s
ci / qemu-tools (pull_request) Canceled after 0s
ci / quality (push) Canceled after 0s
ci / kernel-symbols (pull_request) Canceled after 0s
ci / badges (push) Canceled after 0s
ci / prune-artifacts (pull_request) Canceled after 0s
ci / badges (pull_request) Canceled after 0s
ci / qemu-tools (push) Canceled after 0s
ci / kernel-symbols (push) Canceled after 0s
ci / test (pull_request) Canceled after 0s
ci / patches-apply (push) Canceled after 0s
ci / mcdc (pull_request) Canceled after 0s
ci / prune-artifacts (push) Canceled after 0s
ci / kernel-build (push) Canceled after 0s
ci / patches-apply (pull_request) Canceled after 0s
ci / kernel-build (pull_request) Canceled after 0s
ci / quality (pull_request) Canceled after 0s
shellcheck 0.9 in the qemu-tools CI job reports SC2013 for `for w in $(cat /proc/cmdline)` and exits non-zero, which kept CI red on the M0 kernel branch since the warden.run entry was added. Read /proc/cmdline into a variable and loop over its words. Regression test: tests/qemu-init/run-init-shellcheck-tests.sh (run by the qemu-tools job) shellchecks the rootfs scripts and proves the old form red on a doctored copy. Fixes #18. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkk |
||
|
|
8615f7c13a |
kernel: turn CONFIG_SUSPEND off (rebuild M0)
ci / test (pull_request) Canceled after 0s
ci / prune-artifacts (push) Canceled after 0s
ci / bench (pull_request) Canceled after 0s
ci / kernel-build (push) Canceled after 0s
ci / qemu-tools (pull_request) Canceled after 0s
ci / quality (push) Canceled after 0s
ci / badges (push) Canceled after 0s
ci / quality (pull_request) Canceled after 0s
ci / test (push) Canceled after 0s
ci / bench (push) Canceled after 0s
ci / qemu-tools (push) Canceled after 0s
ci / kernel-symbols (push) Canceled after 0s
ci / patches-apply (push) Canceled after 0s
ci / mcdc (pull_request) Canceled after 0s
ci / kernel-symbols (pull_request) Canceled after 0s
ci / patches-apply (pull_request) Canceled after 0s
ci / prune-artifacts (pull_request) Canceled after 0s
ci / kernel-build (pull_request) Canceled after 0s
ci / badges (pull_request) Canceled after 0s
ci / mcdc (push) Canceled after 0s
The panel is wall powered and never sleeps the SoC. SUSPEND defaults to y, so the defconfig carries an explicit unset, and required-symbols.txt asserts SUSPEND and PM_SLEEP unset against the final .config. Kconfig then drops PM_SLEEP, PM_SLEEP_SMP, SUSPEND_FREEZER, FREEZER, PM_GENERIC_DOMAINS_SLEEP, FW_CACHE and VT_CONSOLE_SLEEP; as PM_SLEEP_SMP was the only thing selecting HOTPLUG_CPU on this one-core SoC, HOTPLUG_CPU, KEXEC and CRASH_DUMP go with it. PM, PM_CLK and runtime PM stay. Regression test: tests/required-symbols asserts both lines, refuses a config that turns either back on, and fails when the defconfig loses the explicit unset (proven red). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkk |
||
|
|
469f31c278 |
buildroot: nftables cgroupv2 patch reads the handle with the raw syscall (uClibc has no wrapper)
ci / test (push) Successful in 19s
ci / mcdc (push) Successful in 18s
ci / bench (push) Successful in 5s
ci / qemu-tools (push) Failing after 13s
ci / kernel-symbols (push) Successful in 1m24s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / badges (push) Skipped
ci / patches-apply (push) Successful in 17s
ci / quality (push) Successful in 1m2s
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkk |
||
|
|
aa6956f595 |
buildroot: patch nftables so socket cgroupv2 matches on 32-bit kernels
ci / test (push) Canceled after 0s
ci / mcdc (push) Canceled after 0s
ci / bench (push) Canceled after 0s
ci / qemu-tools (push) Canceled after 0s
ci / kernel-symbols (push) Canceled after 0s
ci / patches-apply (push) Canceled after 0s
ci / prune-artifacts (push) Canceled after 0s
ci / kernel-build (push) Canceled after 0s
ci / quality (push) Canceled after 0s
ci / badges (push) Canceled after 0s
nftables 1.1.0 builds the id of "socket cgroupv2 level N <path>" from st_ino, which is the 64-bit kernfs id only on 64-bit kernels. On armv7 the id is (generation << 32) | ino and st_ino carries the low half, so the rule loaded and never matched: byte metering per service counted nothing (found by the M0 counting test in QEMU on the 6.18.46 kernel). The patch takes the id from the directory's file handle, in both the parse and the listing path. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkk |
||
|
|
445b2082f5 |
qemu: check the kernel contract at boot and run a staged script (warden.run)
ci / test (push) Canceled after 0s
ci / mcdc (push) Canceled after 0s
ci / bench (push) Canceled after 0s
ci / qemu-tools (push) Canceled after 0s
ci / kernel-symbols (push) Canceled after 0s
ci / patches-apply (push) Canceled after 0s
ci / prune-artifacts (push) Canceled after 0s
ci / kernel-build (push) Canceled after 0s
ci / quality (push) Canceled after 0s
ci / badges (push) Canceled after 0s
init verifies build/required-symbols.txt against the guest's /proc/config.gz, the cgroup v2 controllers and PSI and prints markers; boot-smoke.sh fails when a marker is missing. mkinitramfs.sh stages the list and merges EXTRA_DIR; run.sh --append passes warden.run=<path>, which init runs before powering off (used by the flare-edge M0 limit tests). README notes the symbol lists. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkk |
||
|
|
0360b8dc46 |
kernel: single M0 batch (cgroups, namespaces, PSI, raw table, nftables) with a symbol list and clock keep-alive
ci / test (push) Successful in 18s
ci / mcdc (push) Successful in 19s
ci / bench (push) Successful in 9s
ci / qemu-tools (push) Successful in 53s
ci / prune-artifacts (push) Skipped
ci / quality (push) Successful in 46s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 1m25s
ci / patches-apply (push) Successful in 21s
ci / kernel-build (push) Skipped
One kernel flash for everything later work needs (rebuild M0, d09 M0-2): - warden_defconfig: cgroup v2 controllers (MEMCG, CGROUP_PIDS, CGROUP_SCHED, FAIR_GROUP_SCHED, CFS_BANDWIDTH), the byte-metering match symbols (XT_MATCH_CGROUP, XT_CONNMARK, XT_MARK, IP6_NF_MANGLE), IKCONFIG and IKCONFIG_PROC, XT_MATCH_OWNER, the raw tables and the CT target (the NOTRACK for flare-edge#537), NAMESPACES with its five sub-options (USER_NS stays closed at boot by a sysctl), PSI, and the nftables set (NF_TABLES, ip and ip6 families, NFT_CT, NFT_MASQ, NFT_NAT, NFT_LIMIT, NFT_SOCKET, NFT_REJECT). TIME_NS and RT_GROUP_SCHED are explicitly unset. HW_RANDOM_ROCKCHIP is built in as a probe for the hardware RNG. - build/required-symbols.txt and probe-symbols.txt are the source of record; build-kernel.sh asserts both against the final .config instead of a hand-written list (olddefconfig drops an unknown or unsatisfied symbol without a word). - WARDEN_CONFIG_ONLY=1 stops after that assertion (a seconds-long CI gate) and, like a full build, writes the final .config and its sha256 (CONFIG_OUT), the digest firmware images record as KCONFIG_SHA256. - clk_core_mcu_rtc gets CLK_IGNORE_UNUSED like clk_core_mcu, in the patch and in the enablement source it documents, so 6.18 keeps the HPMCU mtime clock up. - CI: a kernel-symbols job expands the real configuration and asserts the lists on every push; offline tests prove the assertion fires for every failure shape. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkk |
||
|
|
d22c900fb6 |
Merge pull request 'kernel: build in IPv6 netfilter (flare-edge#533)' (#15) from fix-533-ipv6-netfilter into flare-edge-next
ci / test (push) Successful in 13s
ci / mcdc (push) Successful in 13s
ci / bench (push) Successful in 5s
ci / patches-apply (push) Successful in 15s
ci / quality (push) Successful in 27s
ci / badges (push) Skipped
ci / qemu-tools (push) Successful in 44s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
|
||
|
|
b7125fc4a7 |
kernel: correct IPv6 netfilter defconfig comment (flare-edge#533)
ci / badges (push) Skipped
ci / mcdc (push) Successful in 13s
ci / test (push) Successful in 15s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / quality (push) Successful in 29s
ci / bench (push) Successful in 5s
ci / qemu-tools (push) Successful in 44s
ci / patches-apply (push) Successful in 16s
ci / quality (pull_request) Successful in 27s
ci / badges (pull_request) Skipped
ci / test (pull_request) Successful in 14s
ci / bench (pull_request) Successful in 6s
ci / mcdc (pull_request) Successful in 12s
ci / patches-apply (pull_request) Successful in 14s
ci / qemu-tools (pull_request) Successful in 43s
ci / prune-artifacts (pull_request) Skipped
ci / kernel-build (pull_request) Skipped
The icmp6 match is part of the ip6_tables core (IP6_NF_IPTABLES), not xt_tcpudp. Comment only; the symbol set is unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkk |
||
|
|
35f3ca10eb |
kernel: build in IPv6 netfilter (flare-edge#533)
The panel kernel had no ip6tables filter table, so the IPv4 default-drop firewall never applied to IPv6 and dropbear and telnetd were reachable over ::. Enable the ip6tables core (legacy flavour, matching the userland), the filter table, and IPv6 defrag for conntrack, all built in because the panel has no /lib/modules: CONFIG_NF_DEFRAG_IPV6=y CONFIG_IP6_NF_IPTABLES=y CONFIG_IP6_NF_IPTABLES_LEGACY=y CONFIG_IP6_NF_FILTER=y No new match symbols: icmp6 lives in xt_tcpudp, and state, limit and conntrack are family-agnostic and already enabled. build-kernel.sh now asserts these four are =y in the final .config, because olddefconfig drops an unmet-dependency line silently and the loss would only show as an unfiltered IPv6 stack in the field. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxh2piVufTWbzKTmUafTkk |