Add ASAN status.json

Open
#108 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, json
Domain
ci-cd, release

Research direction

Start by comparing multi_arch_release.yml with multi_arch_release_asan.yml, then trace how quartz_tracking_id and status.json are generated and published. Confirm the ASAN workflow supplies its build variant and produces the status-asan.json links and latest pointers shown in the proposed rockrel-status layout.

Written by the indexing model from the issue text.

Description

We need to provide ASAN status.json.

In TheRock we have 2 important metrics to determine if and which status.json we send to:

  • release_type (the channel/stream): nightly, nightly-bkc, prerelease (plus dev, dev-bkc which are known but untracked)
  • build_variant (the sanitizer/flavor): release | asan-debug | asan (and eventually host-asan, tsan, ...)

for quartz_tracking_id we currently capture: "<orchestrator github.run_id>;<release_type>". we probably want to extend it with the build_variant.

asan is not triggered from multi_arch_release.yml but from multi_arch_release_asan.yml and has no piping of quartz_tracking_id yet.

Best would be to keep the same structure we already have and add a status-asan.json
But open to discussion if something else would be better.

New layout with status-asan.json

rockrel-status/
├── nightly/
│   ├── latest.json ──────────► <date>/status.json
│   ├── latest_good.json ─────► <date>/status.json
│   ├── latest-asan.json ─────► <date>/status-asan.json           ★ new
│   ├── latest_good-asan.json ► <date>/status-asan.json           ★ new
│   └── 20260911/
│       ├── status.json                    release  (variant=release)
│       └── status-asan.json               asan     (variant=asan)  ★ new
│
├── nightly-bkc/
│   ├── latest.json ──────────► <nightly-ver>/<bkc-date>/status.json
│   ├── latest_good.json ─────► <nightly-ver>/<bkc-date>/status.json
│   ├── latest-asan.json ─────► <nightly-ver>/<bkc-date>/status-asan.json   ★ new
│   ├── latest_good-asan.json ► <nightly-ver>/<bkc-date>/status-asan.json   ★ new
│   └── 10.1.0a20260825/
│       ├── latest.json ──────────► <bkc-date>/status.json
│       ├── latest_good.json ─────► <bkc-date>/status.json
│       ├── latest-asan.json ─────► <bkc-date>/status-asan.json    ★ new
│       ├── latest_good-asan.json ► <bkc-date>/status-asan.json    ★ new
│       └── 20260831/
│           ├── status.json
│           └── status-asan.json                                   ★ new
│
└── prerelease/
    ├── latest.json ──────────► <major.minor>/<full>/status.json
    ├── latest-asan.json ─────► <major.minor>/<full>/status-asan.json       ★ new
    └── 7.14/
        ├── latest.json ──────────► <full>/status.json
        ├── latest-asan.json ─────► <full>/status-asan.json        ★ new
        └── 7.14.0rc2/
            ├── status.json
            └── status-asan.json                                   ★ new

Dominant language
Python
Stars
1
Forks
1
Avg merge
3d 11h
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ROCm/Quartz

All issues in ROCm/Quartz

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.