Repository navigation
tools: move NCM transfer profile and refresh Bluejay review status - #666
Conversation
|
Thanks, Chris. This is where I wanted the SSH transfer check to live, and the tool is careful in the ways that matter: it only reads Two changes before I merge, both in
Smaller things, take them or leave them:
The 7 Pro and laptop-sleep run for the driver stays with kernel #225. |
f09b63c to
8ca0de9
Compare
|
The November 12 review requests are addressed on Policy, full This PR was closed without merging; reopening it to keep the requested tooling follow-up reviewable. Reopening triggered CI run 43449538659: Policy has passed and Tests (tests/all, every package) is running at this publication check. Hosted tests are not yet claimed green. No new code change accompanies this comment. |
|
Thank you, Chris. Both changes are in, and the rest went further than I asked. The transfers now go through One wording point in Your new line at the end of |
|
Thanks, @latentoperator. This was ready, but #676 just merged and appended to |
a4217e8 to
4d372ff
Compare
Keep the USB-interface-pinned SSH reproduction in mobile tooling as requested in linux-omarchy-mobile derekross#225. The kernel selftest remains host-only; document what the transfer profile does and does not establish. Assisted-by: LLM
Refresh the review table after the November 11 signed replacements. Distinguish source/build results from the still-unbooted runtime stack and document the focused passive package coordination and migration dependency. Assisted-by: LLM
Use phone-ssh for identity, host-key and direct-interface settings. Report the failed transfer/check and SSH diagnostics, stop the SSH process group on timeout or interruption, and reject helper control tokens as interface names. Add offline fixtures covering successful transfers, early failures, settings, argument validation, deadlines and cancellation. The attached Bluejay also passed sixteen verified transfers on its historical kernel.
The boot-update.conf ownership follow-up was not accepted on derekross#346. Keep the package passive and describe the attended migration and smoke report that still gate it. Assisted-by: OpenAI Codex
Keep this host SSH transport test beside tests/phone-ssh rather than at the append-only tail, where new upstream suites repeatedly conflict with it. Retain all upstream test entries. Assisted-by: OpenAI Codex
4d372ff to
d891c66
Compare
|
Thanks, Chris. The rebase is just what I asked for: both suites are still there, and Moving the line up next to One small thing for a later Bluejay docs change, not this one: the UPSTREAM table still lists kernel #226 as "awaiting maintainer merge", and it merged on the 13th. Merging now. |
Add the attended USB NCM transfer check moved out of linux-omarchy-mobile #225. It reads sixteen exact 2 MiB zero streams, verifies each SHA-256 under one 20-second deadline, and stops at the first failure. It writes no phone files or partitions.
Every transfer uses
tools/phone-ssh --fresh, preserving its key, host-key pin/alias and direct-interface settings.--peerand--interfaceare required; the interface must be a literal name, sooffandautocannot disable binding. Direct binding defaultsOMAMOBILE_SSH_CONFIGto/dev/null; an incompatible explicit config fails with a diagnostic. Failures identify the transfer and failed check and include SSH's stderr. Timeouts and interruption stop the SSH process group, including its proxy.Validation: policy, repository
tests/alland every package's tests pass on the rebased head. The newtests/ncm-transferfixtures cover sixteen successful streams, pinned fresh SSH settings, early SSH/size/digest failures, argument refusals, the shared deadline and cancellation. Independent review also exercised real sleeping SSH descendants under timeout, SIGINT, SIGTERM and SIGHUP. The exact tool passed all sixteen transfers over the attached Pixel 6a's USB link using its normal pinned identity/known-host settings, with no wrapper.The phone ran
7.3.0-rc6-omamobile-bluejay-input-gated0. These transfers qualify the host tool, not the revised NCM driver's aggregation-retry path; USB tracing is needed to establish that path ran. Pixel 7 Pro and laptop-sleep qualification remain with kernel #225. This PR performs no kernel installation or boot. Bluejay's documentation records the transfer command and the fixed November 11 source/build checkpoint; current revision and CI details stay in the kernel PRs.November 13–14 follow-up
The same exact tool subsequently passed sixteen 2 MiB SHA-checked reads on the revised Bluejay restricted-pool boot (
7.3.0-rc6-omamobile-bluejay-review-20261111). This adds ordinary revised-kernel transfer evidence, not proof that a full-pool aggregation retry executed. The previous-head CI run 43449538659 completed successfully.Rebased onto main on November 14, retaining both
tests/chroot-extractorsandtests/ncm-transferafter #676. The documentation also corrects the passive-package coordination status: the proposedboot-update.confownership follow-up was not taken, and #346 stays passive. Policy, the completetests/allsuite and all 32 package suites pass locally; independent review found no remaining blocker. Current-head hosted CI passed ona4217e82274ce09c5745ba043bdb85715a283092(Policy and Tests: tests/all plus every package).Second upstream rebase — November 14, 2026
Rebased again after the install-link test additions, preserving
tests/chroot-extractors,tests/rootfs-smoke-linkand every other upstream suite. The NCM suite now runs besidetests/phone-sshrather than at the append-only tail, avoiding the repeated tail conflict. The transfer tool and its fixtures are unchanged from the previously green head.Policy, the complete final
tests/allrun and all 33 package suites pass locally. Independent review found no remaining blocker. The previous-head green CI above remains historical. The first hosted run failed in unchanged upstreamtests/stage-boot-filesafter #775. Upstream #776 fixed the named-only behavior and test. This PR has now rebased onto that fixed base (259be39), with all five topic patches unchanged by range-diff. Policy, the corrected upstream stage suite and the NCM suite pass again locally. Fresh PR-event CI passed ond891c66def3858676a751c2a1d54f7d55582625aagainst the fixed base (Policy and complete Tests: tests/all plus every package). The failed old run was not reused.