Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion data/backlog.json
Original file line number Diff line number Diff line change
Expand Up @@ -173,4 +173,4 @@
{"project":"linux-phone-oco/lab-tools","id":"test-hold-parallel-flake","title":"hold::tests::the_phone_is_held_by_one_change_at_a_time fails in a parallel workspace run, passes alone","status":"open","note":"Sign (coordinator, 2026-11-18): failed once in a parallel workspace run, passes alone. Likely a shared lease file or lock path across tests; give each test its own.","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"cargo test --workspace passes 20 runs in a row with default parallelism","rank":10,"about":null}
{"project":"linux-phone-oco/lab-tools","id":"sxmo-utils-lab-apk-deliver","title":"Build, sign and publish the sxmo-utils lab apk as the sxmo-utils@lab repository","status":"open","note":"Blocked on the conveyor (linux-package-distribution-oco/conveyor, alpine.yml v1), not on lab-tools. Read 2026-11-18: it takes a declaration input and a tag, but (1) it copies only the APKBUILD into the build folder, while sxmo-utils has 7 local source files beside it (rootfs-*, *.post-install), so abuild fetch/verify fails; (2) it builds one Pages site per repository from this run's artifacts alone, so a second package in lab-tools would replace lpoco-health's repository (and the verify step reads the page for one NAME). Needs of the conveyor: copy the APKBUILD's whole folder; merge into the existing site (or one site per package), verify per package. Then lab-tools adds packaging/sxmo-utils/conveyor.toml (tag-prefix sxmo-utils-v, tag sxmo-utils-v1.18.1_p20261118) and a second packages job with declaration:. Nothing landed in lab-tools: a trigger now would clobber the live lpoco-health page.","opened":"2026-11-18","waits":"a conveyor tag (linux-package-distribution-oco/conveyor alpine.yml) that copies the APKBUILD folder whole and deploys a second package without replacing the first, with verify per package","blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"suspend-retry-backs-off","rank":4,"about":"sxmo-utils-lab-apk"}
{"project":"linux-phone-oco/lab-tools","id":"phone-pieces-drift-in-lab","title":"lpoco lab names a stale phone-side piece at every change's end, from the report it reads back","status":"open","note":"Rest of phone-pieces-drift-named: reuse lpoco_host::stale_pieces. Also from review: picking the newest report by file name assumes names sort by time (check that).","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"a test in lab-tools lpoco/tests (to write, failing first): after a change the lab output names a piece off main","rank":6,"about":"phone-pieces-drift-named"}
{"project":"linux-phone-oco/lab-tools","id":"host-plan-unreadable-not-new","title":"lpoco host plan says a root-only file it cannot read is unreadable, not new","status":"open","note":"Sign (orchestration, 2026-11-18): planning 0.15.0 named /etc/polkit-1/rules.d/50-lpoco.rules '(new)' while the directory is root-only (Permission denied), so plan cannot tell whether the author's earlier prepare already wrote it. The same limit was noted for NetworkManager keyfiles (part 6b). The author is asked for sudo on a guess.","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"a host plan test from fixtures: a declared file under a directory the lab user cannot read is planned as 'unreadable, rewritten by prepare now', never '(new)'; a readable missing file is still '(new)'","rank":7,"about":"lpoco-host-rest"}
{"project":"linux-phone-oco/lab-tools","id":"host-plan-unreadable-not-new","title":"lpoco host records each root file it installs, so plan reads an unreadable one as up to date","status":"open","note":"Coordinator, 2026-11-18: when lpoco-host installs a root file, it records the staged content's hash in user state (~/.local/state/lpoco-host, or ~/.cache/lpoco-host). Plan then treats a root file it cannot read as up to date when the staged hash matches the recorded one and its check passes (for 50-lpoco.rules: the share check), and as changed only when the staged content differs. Sign: planning 0.15.0 named /etc/polkit-1/rules.d/50-lpoco.rules '(new)' though the author's 0.14.2 prepare installed it at about 15:00 and the share check passed - the directory is root-only. The same limit applies to NetworkManager keyfiles (part 6b). Bootstrap: the lab has no record yet. Consider recording without root once a check proves the file in place (e.g. lpoco host check passing the share check writes the record for the staged hash), so no sudo is asked for an unchanged file. Then orchestration runs the 0.15.0 prepare itself, with 0 root commands.","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":"build","device":"xiaomi-surya","proof":"host plan tests from fixtures: (1) a root file under an unreadable directory, whose staged content hashes to the hash recorded at its last install, is planned up to date with 0 root commands; (2) changed staged content is planned as a root install; (3) with no record, it is named as unreadable and not known, never '(new)'; (4) prepare now records the hash after each root install it runs","rank":5,"about":"lpoco-host-rest"}
8 changes: 4 additions & 4 deletions docs/backlog.md
Original file line number Diff line number Diff line change
Expand Up @@ -4338,7 +4338,7 @@ About


<a id="host-plan-unreadable-not-new"></a>
### lpoco host plan says a root-only file it cannot read is unreadable, not new
### lpoco host records each root file it installs, so plan reads an unreadable one as up to date

Project
: linux-phone-oco/lab-tools
Expand All @@ -4347,7 +4347,7 @@ Status
: open

Note
: Sign (orchestration, 2026-11-18): planning 0.15.0 named /etc/polkit-1/rules.d/50-lpoco.rules '(new)' while the directory is root-only (Permission denied), so plan cannot tell whether the author's earlier prepare already wrote it. The same limit was noted for NetworkManager keyfiles (part 6b). The author is asked for sudo on a guess.
: Coordinator, 2026-11-18: when lpoco-host installs a root file, it records the staged content's hash in user state (~/.local/state/lpoco-host, or ~/.cache/lpoco-host). Plan then treats a root file it cannot read as up to date when the staged hash matches the recorded one and its check passes (for 50-lpoco.rules: the share check), and as changed only when the staged content differs. Sign: planning 0.15.0 named /etc/polkit-1/rules.d/50-lpoco.rules '(new)' though the author's 0.14.2 prepare installed it at about 15:00 and the share check passed - the directory is root-only. The same limit applies to NetworkManager keyfiles (part 6b). Bootstrap: the lab has no record yet. Consider recording without root once a check proves the file in place (e.g. lpoco host check passing the share check writes the record for the staged hash), so no sudo is asked for an unchanged file. Then orchestration runs the 0.15.0 prepare itself, with 0 root commands.

Opened
: 2026-11-18
Expand All @@ -4359,10 +4359,10 @@ Device
: xiaomi-surya

Proof
: a host plan test from fixtures: a declared file under a directory the lab user cannot read is planned as 'unreadable, rewritten by prepare now', never '(new)'; a readable missing file is still '(new)'
: host plan tests from fixtures: (1) a root file under an unreadable directory, whose staged content hashes to the hash recorded at its last install, is planned up to date with 0 root commands; (2) changed staged content is planned as a root install; (3) with no record, it is named as unreadable and not known, never '(new)'; (4) prepare now records the hash after each root install it runs

Rank
: 7
: 5

About
: lpoco-host-rest
Loading