rtk pipe -f go-test drops benchmark results
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start at the rtk pipe -f go-test handler and trace how it reduces the JSON stream to test counts. Reproduce with the reported go test -json -v=false -bench . -benchtime 10x ./benchok command; done means the benchmark results, including the ns/op line, are retained rather than discarded.
Written by the indexing model from the issue text.
Description
rtk pipe -f go-test reduces a go test -json -bench stream to test counts and drops the benchmark lines.
Go 1.24.6, go test -json -v=false -bench . -benchtime 10x ./benchok (one passing test, one benchmark that calls b.Log), piped to rtk pipe -f go-test:
Go test: No tests found
The stream contains BenchmarkX-24 10 1389 ns/op in its output events. With the default chatty JSON (Go 1.27.1, same command without -v=false) the output is Go test: 1 passed in 1 packages and the ns/op line is dropped as well.
Same output on v1.0.1 and on develop 6c2313a66. #1445 fixed this for rtk go test, which no longer injects -json for -bench runs; the pipe path still goes through the test-count reducer.
- Dominant language
- Rust
- Stars
- 85k
- Forks
- 5.4k
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 59
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 rtk-ai/rtk
-
area:cli bug good first issue priority:medium
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
`rtk dotnet test` counts a project once per output line that names its `.csproj`Possibly taken @ecoyoung claimed this 1 day ago. Openarea:cli bug dotnet good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rtk-ai/rtk#4844 · 2 comments ·
Maintainers usually reply within 1 day
-
rtk git show <commit>: truncation hint points to `rtk git diff --no-compact`, which does not show the commitPossibly taken @vshalpnjabi claimed this 1 day ago. Openarea:cli bug good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
rtk-ai/rtk#4817 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Windows: .hook_warn_last mtime never advances, so the daily hook reminder prints on every commandPossibly taken @ShryukGrandhi claimed this 6 days ago. Openarea:cli bug good first issue platform:windows priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rtk-ai/rtk#4746 · 2 comments ·
Maintainers usually reply within 1 day
-
test: help_passthrough_fuzz_test opens git's HTML manual pages in the browser on WindowsPossibly taken @viniciusdsandrade claimed this 6 days ago. Openarea:testing bug good first issue platform:windows priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
Similar issues
-
ai_p2 bug comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ClickHouse/ClickHouse#128306 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area: ui enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
JavenKazebee/capture-room#166 ·
Maintainers usually reply within 1 day