Show which test failed and in which configuration

Open
#96 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
ci-cd, tooling

Research direction

Start by locating rla's existing job-failure reporting and its Travis/Azure Pipelines log handling. Trace how logs from the "run the build" CI step are processed, then define done as showing the failed test and configuration when available while preserving useful output when that information cannot be found.

Written by the indexing model from the issue text.

Description

Right now, rla only shows which job failed. It would be nice to also show which test failed and on which configuration.

Note that sometimes this information is not available (eg because the job failed outside of the "run the build" CI step). So this should be a best effort implementation.

Original infra survey comment:

When CI fails, it's often not easy to figure out which exact test suite failed in which configuration (in particular, on which target!), and how to reproduce the failure locally. (I guess that's more of a t-bootstrap than t-infra thing?)

Dominant language
Rust
Stars
52
Forks
27
No merged PRs in 30d

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.

More from rust-lang/rust-log-analyzer

All issues in rust-lang/rust-log-analyzer

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.