Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

suite [69] test_leak_guard.sh reports SKIP 'ASan not available' on an empty SOURCES list or a failed build

Open Beginner friendly
#1,429 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
c, shell
Domain
testing-qa

Research direction

Start with tests/test_leak_guard.sh and the suite [69] path that handles the SOURCES list, the ASan availability check, and the ASan build. Plant an empty SOURCES list and a failing ASan build; done means both report named FAIL results, while SKIP occurs only after a compiler probe proves -fsanitize=address is unavailable.

Written by the indexing model from the issue text.

Description

area:gates kind:gate-defect

Found by the small-batch builder while fixing #1340. tests/test_leak_guard.sh (suite [69]) prints SKIP: AddressSanitizer not available and exits 0 in two cases where it never checked that ASan is missing:

  • when the SOURCES list comes back empty;
  • when the ASan build fails.

This is how #1340's broken print-* reader stayed hidden in [69]: the build failed, and the section reported a SKIP. This is the silent-tolerance class.

Done when

  • [69] SKIPs only when a probe proves the compiler lacks -fsanitize=address, for example compiling a one-line program with the flag.
  • An empty SOURCES list or a failed ASan build is a named FAIL.
  • Plant: an empty SOURCES list and a failing build each turn [69] red.
Dominant language
C
Stars
3
Forks
7
Avg merge
4h 1m
Merged PRs (30d)
121

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 InauguralSystems/EigenScript

All issues in InauguralSystems/EigenScript

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.