Share the TDD test knob helper and quiet the stratum profile in parity tests
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 54/100
Research direction
Start with tests/test_recursive_model_parity.c and tests/test_tdd_partition_metadata.c, then inspect tests/test_mat_cache_lifetime.c for the right-filter signature coverage. Factor the duplicated environment save, set, restore, and Windows shims into one shared test helper that clears the listed worker-width knobs. Done when both tests build under MSVC, the parity test log is under 5 KB, and the guard comment accurately describes its coverage.
Written by the indexing model from the issue text.
Description
Summary
Test hygiene items left after #2127 (PR #2237).
- Shared knob helper.
tests/test_recursive_model_parity.candtests/test_tdd_partition_metadata.ceach save, set and restore TDD environment knobs and carry their own_WIN32setenv/unsetenvshim. Factor this into one test helper header. The helper should also clear the knobs that silently change worker width, so that a developer's environment cannot turn a positive control red or make a parity check vacuous:WIRELOG_TDD_MAX_ACTIVE_WORKERS;WIRELOG_TDD_GLOBAL_READ_MAX_ACTIVE_WORKERS;WIRELOG_TDD_REPLICATE_W1.
- Log noise. Both tests set
WIRELOG_TDD_STRATUM_PROFILE=1to read the selected strategy. In the parity test that prints about 45 KB into the test log per run. Read the strategy through an API or a test hook instead, or capture and drop the profile output. - Right-filter guard wording.
test_right_filter_guardintests/test_recursive_model_parity.cpasses with or without the #2127 cache-key fix: a right-filtered input has its own relation identity, or bypasses the cache. The right-filter part of the join signature is checked only bytests/test_mat_cache_lifetime.c. Reword the comment so it does not read as end-to-end coverage of that part of the signature.
Acceptance
- Both tests use the shared helper and build under MSVC.
- The parity test log is under 5 KB.
- Dominant language
- C
- Stars
- 18
- Forks
- 2
- Avg merge
- 8h 15m
- Merged PRs (30d)
- 216
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 semantic-reasoning/wirelog
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
semantic-reasoning/wirelog#2229 ·
Maintainers usually reply within 1 day
-
Doc: insert executor and incremental consolidation leave sorted runs, not globally sorted headsOpen
Difficulty 1/5 Under an hour Newbie friendliness 83/100
semantic-reasoning/wirelog#2133 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
semantic-reasoning/wirelog#2042 ·
Maintainers usually reply within 1 day
-
p2-medium
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
semantic-reasoning/wirelog#1914 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
semantic-reasoning/wirelog#2243 ·
Maintainers usually reply within 1 day
All issues in semantic-reasoning/wirelog
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zephyrproject-rtos/zephyr#123423 ·
Maintainers usually reply within 2 days
-
dspromote: /etc/exports uses -alldirs on non-mount-point directories, so mountd exports nothingOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
nextbsd/nextbsd-userland#434 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
[YSQL] Local-node initdb reads postgres.bki, but YB clusters bootstrap only from yb_postgres.bkiOpenarea/ysql kind/enhancement priority/low status/awaiting-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yugabyte/yugabyte-db#35763 ·
Maintainers usually reply within 1 day
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days