test(h2h3): ASan/UBSan builds for every HTTP/2, HTTP/3 and QUIC test
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
- Domain
- build-system, testing-qa
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
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_rawtest_h3c,test_h3c_interoptest_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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 public/cursed-http
-
P1: first release
Difficulty 5/5 Over a week Newbie friendliness 15/100
public/cursed-http#61 ·
Maintainers usually reply within 1 day
-
P0: release blocker
Difficulty 4/5 3-5 days Newbie friendliness 35/100
public/cursed-http#60 ·
Maintainers usually reply within 1 day
-
documentation P0: release blocker
Difficulty 3/5 1-2 days Newbie friendliness 42/100
public/cursed-http#59 ·
Maintainers usually reply within 1 day
-
P0: release blocker
Difficulty 4/5 3-5 days Newbie friendliness 35/100
public/cursed-http#58 ·
Maintainers usually reply within 1 day
-
P0: release blocker
Difficulty 5/5 Over a week Newbie friendliness 15/100
public/cursed-http#57 ·
Maintainers usually reply within 1 day
All issues in public/cursed-http
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
xerial/sqlite-jdbc#1515 ·
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·
-
compiler-rt:asan
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
llvm/llvm-project#242921 ·
Maintainers usually reply within 1 day
-
Missing gcc __builtin_stdc_bit_width/floor/ceil signature makes intellisense wrongly report error 70Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
microsoft/vscode-cpptools#14874 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FujiNetWIFI/fujinet-firmware#2401 ·
Maintainers usually reply within 1 day