You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These lanes do not run on pull requests, so a failure here is
invisible until someone reads run history. Several of them are the
only witness for a numbered claim in specs/adrs/001-microvm-security-posture.md
— while a lane is red, that claim has no live evidence behind it.
These lanes do not run on pull requests, so a failure here is
invisible until someone reads run history. Several of them are the
only witness for a numbered claim in specs/adrs/001-microvm-security-posture.md
— while a lane is red, that claim has no live evidence behind it.
These lanes do not run on pull requests, so a failure here is
invisible until someone reads run history. Several of them are the
only witness for a numbered claim in specs/adrs/001-microvm-security-posture.md
— while a lane is red, that claim has no live evidence behind it.
These lanes do not run on pull requests, so a failure here is
invisible until someone reads run history. Several of them are the
only witness for a numbered claim in specs/adrs/001-microvm-security-posture.md
— while a lane is red, that claim has no live evidence behind it.
Burn-down triage (2026-11-13): latest failure (run 43344965233 on 849382a) is FileNotFoundError: .../archive/bundles/<sha>.mvmpkg from the application-inspection fixture — an expected bundle artifact is missing from the assembled archive, not a signing failure. Not caused by 849382a (overclaim lint skip-list only). The open composition-staging PRs (#5284, #5323, #5326) are the likely interaction surface; leaving this to that lane rather than burning a parallel investigation. Will re-check after those land.
These lanes do not run on pull requests, so a failure here is
invisible until someone reads run history. Several of them are the
only witness for a numbered claim in specs/adrs/001-microvm-security-posture.md
— while a lane is red, that claim has no live evidence behind it.
Last red scheduled run: 43367427050 (0af3031) — application-inspection-fixture emitted the bundle as a single application.mvmpkg blob and the smoke died with FileNotFoundError: .../archive/bundles/<sha>.mvmpkg.
Newest scheduled run 43558107797 (50b1a23, 2026-11-14T04:44Z): success — the same "Full pack signing round-trip test" step passes and now emits the assembled fixture.json/manifest.json/manifest.sigstore.json/bundle-author.pub set. Latest push run 43486823182 also green.
Not closed by a manual dispatch: both newest scheduled and newest push runs are green.
Activity
github-actions commentedon Nov 12, 2026
The
Pack signing smokeworkflow (schedule) failed on3010cfdb19c6577a74b7c29aad575d4e777f364f.Run: https://github.com/tinylabscom/mvm/actions/runs/43156722052
Failing or unfinished jobs:
These lanes do not run on pull requests, so a failure here is
invisible until someone reads run history. Several of them are the
only witness for a numbered claim in
specs/adrs/001-microvm-security-posture.md— while a lane is red, that claim has no live evidence behind it.
github-actions commentedon Nov 12, 2026
The
Pack signing smokeworkflow (push) failed ondd1809d049bedf4c3509f58f1f779264ec68abab.Run: https://github.com/tinylabscom/mvm/actions/runs/43267400162
Failing or unfinished jobs:
These lanes do not run on pull requests, so a failure here is
invisible until someone reads run history. Several of them are the
only witness for a numbered claim in
specs/adrs/001-microvm-security-posture.md— while a lane is red, that claim has no live evidence behind it.
github-actions commentedon Nov 13, 2026
The
Pack signing smokeworkflow (push) failed on849382ad417a28f3d68b051411b5ae3bab591b13.Run: https://github.com/tinylabscom/mvm/actions/runs/43344965233
Failing or unfinished jobs:
These lanes do not run on pull requests, so a failure here is
invisible until someone reads run history. Several of them are the
only witness for a numbered claim in
specs/adrs/001-microvm-security-posture.md— while a lane is red, that claim has no live evidence behind it.
auser commentedon Nov 13, 2026
Burn-down triage (2026-11-13): latest failure (run 43344965233 on 849382a) is
FileNotFoundError: .../archive/bundles/<sha>.mvmpkgfrom the application-inspection fixture — an expected bundle artifact is missing from the assembled archive, not a signing failure. Not caused by 849382a (overclaim lint skip-list only). The open composition-staging PRs (#5284, #5323, #5326) are the likely interaction surface; leaving this to that lane rather than burning a parallel investigation. Will re-check after those land.github-actions commentedon Nov 13, 2026
The
Pack signing smokeworkflow (schedule) failed on0af3031c04bda34a7c7a0ac7b18d190f61618047.Run: https://github.com/tinylabscom/mvm/actions/runs/43367427050
Failing or unfinished jobs:
These lanes do not run on pull requests, so a failure here is
invisible until someone reads run history. Several of them are the
only witness for a numbered claim in
specs/adrs/001-microvm-security-posture.md— while a lane is red, that claim has no live evidence behind it.
github-actions commentedon Nov 13, 2026
Pack signing smoke run 43486823182 on
ffd90f895d7080629eceb16095d1ca81c0a49b95is green again. Close this issue with a pull request.github-actions commentedon Nov 14, 2026
Pack signing smoke run 43558107797 on
50b1a239b75855150fa7fc2fd185b202c733ccddis green again. Close this issue with a pull request.auser commentedon Nov 14, 2026
Lane green on the newest scheduled run. Evidence:
application-inspection-fixtureemitted the bundle as a singleapplication.mvmpkgblob and the smoke died withFileNotFoundError: .../archive/bundles/<sha>.mvmpkg.fixture.json/manifest.json/manifest.sigstore.json/bundle-author.pubset. Latest push run 43486823182 also green.Not closed by a manual dispatch: both newest scheduled and newest push runs are green.