Use mozconfig of the failed task
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Start by tracing the failed-task handling and the existing mozconfig selection logic. Use the proposed mozconfig_for_task entry point and inspect the task payload's env fields, including MOZCONFIG, MOZHARNESS_CONFIG, and EXTRA_MOZHARNESS_CONFIG. Done means the failed task's mozconfig is selected consistently.
Written by the indexing model from the issue text.
Description
We should use the mozconfig of the task that fails. @padenot suggested this as an example:
async def mozconfig_for_task(task_id, source_repo):
task = await fetch_json(
f"[https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/{task_id}](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/%7Btask_id%7D)"
)
env = task["payload"].get("env", {})
extra = json.loads(env.get("EXTRA_MOZHARNESS_CONFIG", "{}"))
if env.get("MOZCONFIG"):
return source_repo / env["MOZCONFIG"]
configs = load_mozharness_configs(
env["MOZHARNESS_CONFIG"],
env.get("MOZHARNESS_CONFIG_PATHS", ""),
source_repo,
)
config = merge_configs(configs)
config.update(extra)
if "src_mozconfig" in config:
return source_repo / config["src_mozconfig"]
return (
source_repo
/ config["app_name"]
/ "config"
/ "mozconfigs"
/ config["mozconfig_platform"]
/ config["mozconfig
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 68
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mozilla/bugbug
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
good-first-bug hackbot
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·