test(h2h3): ASan/UBSan builds for every HTTP/2, HTTP/3 and QUIC test

Open Beginner friendly
#56 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
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
c, shell

Research direction

Start with mk/h2h3.mk, where the existing _asan builds for test_h2, test_h2c, test_qpack and test_h3 are defined, and copy that pattern for the missing binaries: test_quic, test_quic_interop, test_quic_raw, test_h3c, test_h3c_interop, test_hpack, test_hpack_scalar and test_h2_scalar. Then add them to the CI run and confirm they pass, including with scaled FUZZ= runs. Done means every H2TESTS binary has an _asan target that CI executes successfully.

Written by the indexing model from the issue text.

Description

P0: release blocker

test_h2, test_h2c, test_qpack and test_h3 have ASan/UBSan builds (mk/h2h3.mk). These don't:

  • test_quic, test_quic_interop, test_quic_raw
  • test_h3c, test_h3c_interop
  • test_hpack, test_hpack_scalar, test_h2_scalar

The missing ones exercise loss, reordering, Retry, 0-RTT, key updates and stream resets: the paths most likely to hide an out-of-bounds read or a use-after-free.

Done when: every H2TESTS binary has a _asan build, CI runs all of them, and they pass, including with FUZZ= scaled runs.

Dominant language
C
Stars
0
Forks
0
Avg merge
20h 4m
Merged PRs (30d)
25

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 public/cursed-http

All issues in public/cursed-http

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.