check-skill-pages: show fixture build errors when a build fails

Open Beginner friendly
  • Is something wrong?
#439 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@ShahadatTest is already working on this.

Since Nov 1, 2026.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bash, python, shell
Domain
build-system, testing-qa

Research direction

Start in tests/check-skill-pages.sh, where the four fixture builds of scripts/build-skill-pages.py redirect stderr to a temp file under set -e. Copy the rc=0 / || rc=$? / cat "$err" pattern from the main build at the top of the script into a small helper and use it for $fake, $desc and $real. Done when a deliberately failing fixture build prints its stderr and the script exits non-zero with a message.

Written by the indexing model from the issue text.

Description

good first issue P2

tests/check-skill-pages.sh runs four extra builds of scripts/build-skill-pages.py against fixture eval dirs ($fake, $desc, $real and, once #433 merges, $c4). Each one sends stderr to a temp file. Under set -e, a build that crashes ends the script before that file is shown, so CI fails with no error message.

The main build at the top of the script already handles this:

rc=0
python3 scripts/build-skill-pages.py --out "$out" 2>"$err" || rc=$?
cat "$err" >&2
[ "$rc" -eq 0 ] || { echo "build-skill-pages.py exited $rc" >&2; exit "$rc"; }

Fix: give the fixture builds the same pattern (one small helper is enough), then check by making one fixture build fail on purpose and confirming its stderr appears in the output.

Dominant language
HTML
Stars
347
Forks
12
Avg merge
1d 23m
Merged PRs (30d)
118

Getting set up

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 coco-research/coco

All issues in coco-research/coco

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.