Log analysis message can be significantly delayed and show up after the next bors run is already going

Open
#79 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
ci-cd

Research direction

Start by comparing the linked issue comments on pull request 118454 and tracing how the log-analysis message is associated with a bors run. Done means analysis messages refer to the correct failed run and are not delayed until after a subsequent bors run has started.

Written by the indexing model from the issue text.

Description

This message refers not to the bors run that started in the message just before, it refers to the run that failed here. That means the message was 30min delayed, and also the fact that there already was a new bors run means it was very confusing to still yet a log analysis message from the previous run.

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.