R19 raised two things about this comment. One resolved itself — it used to explain why the matrix had no API 37 row at all, and #56 added the gating row.
The other survived. The comment read:
api-level must be "37.0". A bare 37 is not an SDK package and fails during setup
The second sentence is true and was measured — it cost a run to find. The first overstates it. What must be true is that the api-level is a point release; 37.0 is one of several.
The repo already knew this, in two other places
api37-debug.yml's own input descriptions:
API level, as the SDK spells it. 37.0, 37.1, 37.2-beta3, 36 …
System image target. android-37.1 and 37.2-beta* ship ONLY as google_apis_ps16k
And docs/api-37-emulator-crash.md measures android-37.0 rev 6 and android-37.1 rev 8 side by side, both aborting. So the repo knows 37.1 exists and behaves the same; only this comment implied otherwise.
Why it's worth the words
Someone debugging this row and wondering whether a newer image helps reads "must be 37.0" as a constraint and stops. The measured answer is that it doesn't help — a better thing to learn than a rule that isn't one. And the ps16k-only wrinkle above 37.0 is the detail that would actually bite them.
Comment only. No job, matrix, filter or gating behaviour changes. actionlint clean at the pinned digest.
Closes #28 (R19).
R19 raised two things about this comment. **One resolved itself** — it used to explain why the matrix had no API 37 row at all, and #56 added the gating row.
**The other survived.** The comment read:
> `api-level` must be `"37.0"`. A bare 37 is not an SDK package and fails during setup
The second sentence is true and was measured — it cost a run to find. **The first overstates it.** What must be true is that the api-level is a *point release*; `37.0` is one of several.
## The repo already knew this, in two other places
`api37-debug.yml`'s own input descriptions:
> API level, as the SDK spells it. **37.0, 37.1, 37.2-beta3**, 36 …
> System image target. android-37.1 and 37.2-beta* ship **ONLY** as `google_apis_ps16k`
And `docs/api-37-emulator-crash.md` measures `android-37.0` rev 6 and `android-37.1` rev 8 **side by side**, both aborting. So the repo knows 37.1 exists and behaves the same; only this comment implied otherwise.
## Why it's worth the words
Someone debugging this row and wondering whether a newer image helps reads *"must be 37.0"* as a constraint and stops. The measured answer is that it **doesn't** help — a better thing to learn than a rule that isn't one. And the `ps16k`-only wrinkle above 37.0 is the detail that would actually bite them.
Comment only. No job, matrix, filter or gating behaviour changes. actionlint clean at the pinned digest.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #28 (R19).
R19 raised two things about this comment. One resolved itself — it used to explain why the matrix had no API 37 row at all, and #56 added the gating row.
The other survived. The comment read:
The second sentence is true and was measured — it cost a run to find. The first overstates it. What must be true is that the api-level is a point release;
37.0is one of several.The repo already knew this, in two other places
api37-debug.yml's own input descriptions:And
docs/api-37-emulator-crash.mdmeasuresandroid-37.0rev 6 andandroid-37.1rev 8 side by side, both aborting. So the repo knows 37.1 exists and behaves the same; only this comment implied otherwise.Why it's worth the words
Someone debugging this row and wondering whether a newer image helps reads "must be 37.0" as a constraint and stops. The measured answer is that it doesn't help — a better thing to learn than a rule that isn't one. And the
ps16k-only wrinkle above 37.0 is the detail that would actually bite them.Comment only. No job, matrix, filter or gating behaviour changes. actionlint clean at the pinned digest.