release-stable run 319: metadata failed #145

Closed
opened 2026-07-29 03:05:46 +00:00 by forgejo-actions · 1 comment
(no lane.log captured)
``` (no lane.log captured) ```
Contributor

Not a defect. Run 319 was dispatched ten seconds after run 318 finalized v0.15.0, so metadata refused a version that was already published — the lane law working as written ("refuse a rerun of a version already published unless the lane is explicitly repairing it").

Worth noting what this issue does illustrate: its body is only (no lane.log captured), which is another specimen for #136 — the failing step contributed nothing to the outward evidence, so the report says a job failed without saying why. The reason had to be reconstructed from run timing and the published metadata.

Not a defect. Run 319 was dispatched ten seconds after run 318 finalized v0.15.0, so `metadata` refused a version that was already published — the lane law working as written ("refuse a rerun of a version already published unless the lane is explicitly repairing it"). Worth noting what this issue does illustrate: its body is only `(no lane.log captured)`, which is another specimen for #136 — the failing step contributed nothing to the outward evidence, so the report says a job failed without saying why. The reason had to be reconstructed from run timing and the published metadata.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishLab/plumb#145
No description provided.