test(tools): test_invite_answer_wiring scans nothing in a checkout whose path contains tests/
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
Research direction
Start with tools/tests/test_invite_answer_wiring.py, especially the source file filtering at lines 131–136. Reproduce the failure by running the named test from a checkout path containing tests/, then apply the suggested relative path filter. Done when the test passes from that checkout and still excludes scenario/ and tests/ files.
Written by the indexing model from the issue text.
Description
Kind: bug (test). Found while running unit A2 of #2132 (#2147).
tools/tests/test_invite_answer_wiring.py::TheScenarioEndpointReadsTheAppliersRecord::test_the_endpoint_and_the_keep_switch
filters the source files it scans by substring on the file's absolute path, so a checkout whose own path contains
tests/ scans nothing and the test fails.
Evidence at 2cbe3211
tools/tests/test_invite_answer_wiring.py:131-135:for p in (ROOT / "src/runtime").rglob("*.cpp") if "scenario/" not in p.as_posix() and "tests/" not in p.as_posix();p.as_posix()is the absolute path.- In a worktree whose directory name ends in
tests(.../claude-main-2147-parallel-tool-tests/),othersis empty:
AssertionError: 0 not greater than 50at:136, serially and in parallel. The same test passes in a checkout whose path has notests/.
Not shown
- Whether other tests filter on an absolute path (
git grep -n 'as_posix()' -- tools/testslists the candidates; the others found userelative_to(...)first).
Falsifier
The test passes in a checkout under a directory named ...-tests, with the filter taken on p.relative_to(ROOT).
Work
- Test first: copy the tree under a directory named
x-testsand run the test; it fails. - Filter on
p.relative_to(ROOT / "src/runtime").as_posix()(relative path), keeping thescenario/andtests/exclusions.
- Dominant language
- C++
- Stars
- 2
- Forks
- 5
- Avg merge
- 4h 20m
- Merged PRs (30d)
- 939
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 EchoTools/nevr-runtime
-
backlog bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
EchoTools/nevr-runtime#2335 ·
Maintainers usually reply within 1 day
-
backlog bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2332 ·
Maintainers usually reply within 1 day
-
test(tools): the stage_pack description test fails when its two zips straddle a 2-second boundaryOpenbacklog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2309 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
EchoTools/nevr-runtime#2263 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
EchoTools/nevr-runtime#2260 ·
Maintainers usually reply within 1 day
All issues in EchoTools/nevr-runtime
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Niko1221/Strata#5560 · 2 comments ·
Maintainers usually reply within 4 days
-
NVIDIA windows
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
要トリアージ 辞書
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
yksr-melt/Meltype#1625 · 1 reaction ·
Maintainers usually reply within 1 day
-
kind/bug priority/medium qa_automation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37324 ·
Maintainers usually reply within 1 day