Enhance e2e tests logs in CI

Open
  • Is something wrong?
#2,857 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the e2e test CI configuration and the current retry action. Check how node logs are emitted and how retry indexes are handled in GitHub Actions. Done means the CI UI groups e2e logs by node with distinct group IDs for retries, or documents the alternative retry action if the current approach cannot support it.

Written by the indexing model from the issue text.

Description

CI/CD :factory:

Why

The logs of the e2e tests in the CI are hard to read and could be enhanced if they were grouped by node in the UI of GitHub Actions.

What

Enhance UI of e2e logs in GiHub Actions.

How

  • Finalize group logs of nodes implementation (with different group ids by retry index)
  • If it does not work, could we do that with another retry action?
Dominant language
Rust
Stars
155
Forks
52
Avg merge
2d 17h
Merged PRs (30d)
37

Getting set up

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 IntersectMBO/mithril

All issues in IntersectMBO/mithril

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.