hathach 8a42508300 Key HIL report dir by run id so re-runs and other PRs cannot clobber it ...

A re-run attempt merged into an empty base: another PR's HIL job ran
between attempt 1 and the retry and rewrote the shared hil_report.json,
so the run-stamp guard (correctly) refused the foreign base but the
full-fleet results were lost - the retry report contained only the
re-run cells.

Give each (run id, job) its own report dir instead:
- attempts of the same run share a dir, so the retry always finds its
  own sidecar and .failed spec intact
- interleaved runs of other PRs/jobs write elsewhere and cannot clobber
- the run-stamp mechanism (.failed.run file) becomes redundant and is
  removed
- stale per-run dirs are pruned after 2 weeks

2026-07-17 15:39:10 +07:00

..

actions

Update several actions to latest version

2026-03-18 00:31:01 +07:00

ISSUE_TEMPLATE

correct flash/ram for v307 and v305

2025-07-28 11:43:20 +07:00

workflows

Key HIL report dir by run id so re-runs and other PRs cannot clobber it

2026-07-17 15:39:10 +07:00

FUNDING.yml

Set GitHub Sponsors username in FUNDING.yml

2026-05-25 12:59:30 +07:00

labeler.yml

ci(labeler): auto-apply Port labels from changed driver files (#3673)

2026-06-04 15:18:40 +07:00

membrowse_pr_message.j2

set new membrowse comment github workflow with comment message

2026-03-10 07:10:53 +00:00