irisandClaude Opus 5
4641b9ec9b
The two-APK case had no fixture: it was verified against a scratch project that was not kept, so the shape three recent bugs came out of was covered only by a tempfile unit test. test-projects/two-clients is two Apk components in one checkout, each with its own cwd and its own package -- what tdep-survey looks like, and what service-and-app cannot stand in for, since only one of its two components produces an APK. tablet is slow on purpose (six seconds of pretending to cross-compile, reporting its own progress) beside a phone that builds in two, because that is what makes ?component= visible rather than merely asserted: building one finishes while the other has not started. Verified live against a throwaway server rather than reasoned about. build?component=phone ran phone alone; afterwards phone reported built and tablet did not, which is the sibling-masking bug -- under the root-anchored "never built at all" check the tablet would have read as current and been refused its own first build. prepare?component=tablet then ran tablet alone and it did build. Each component resolved its own APK under its own directory, with its own size and mtime, so nothing reports the first match for both. Also corrects a sentence in that README that went stale when discovery moved per-component: find_apks is anchored at project.join(cwd), not at the project path. The conclusion it supports is unchanged -- every other fixture declares no cwd, so the anchor is still the project root for them, and building into app/ is still what keeps a stub APK from being offered as a build of Dev Updater itself. Re-ran the check command in that section: only the updater's own APK is reachable from the repository root. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
12 lines
536 B
Bash
Executable File
12 lines
536 B
Bash
Executable File
#!/bin/sh
|
|
# Builds this project's phone client -- the fast half of the pair, so that
|
|
# the two components finishing at visibly different times is the fixture's
|
|
# own evidence that only one of them ran.
|
|
#
|
|
# Run from `two-clients/phone`, which is this component's `cwd`, so the
|
|
# shared builder writes into `phone/app/build/outputs/apk/` and the APK is
|
|
# reachable from this component's directory but not from the project root's
|
|
# two-level patterns.
|
|
set -eu
|
|
../../lib/build-apk.sh --package com.example.dutest.phone --label "Test Phone"
|