rust-lang / rust-lang/rfcs

The bencher should have a tool-friendly output format

Open
#895 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

T-dev-tools
Dominant language
Markdown
Stars
6.6k
Forks
1.7k
Avg merge
16h 14m
Merged PRs (30d)
1

Description

Issue by mzabaluev
Sunday Feb 22, 2015 at 19:17 GMT

For earlier discussion, see https://github.com/rust-lang/rust/issues/22683

This issue was labelled with: in the Rust repository


The logfiles produced by bench runs have a format that is not very friendly to simple tools like join: the type of test/result and the test path do not have stable positions if the lines are broken up into space-separated fields.

It would be nice if the test driver could produce tool-friendly output where each test produces a line of regular space-separated fields with optional freeform information:

type path result freeform

Here, type can be test, bench, or ignored. path is the crate path of the test function. result is a single token depending on the type (time/iter for benchmarks, ok|failed|etc. for tests, not present for ignored tests).

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the earlier discussion in issue 22683 and inspect the test driver's existing bench-run log output. Define how test, bench, and ignored lines should follow the proposed type/path/result/freeform layout, then verify that the resulting output is consistently space-separated and tool-friendly.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
testing, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.