make t_client smarter in case of spurious failures

Open
#1,149 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
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c, shell

Research direction

Start by locating t_client and reading how it runs tests and reports failures; the issue does not name a file or test command. Then check whether it can rerun a small set of failed tests and define how many retries and what failure threshold to use. Done means transient failures pass after a retry, while persistent failures are still reported.

Written by the indexing model from the issue text.

Description

enhancement feature

the most annoying we can see is "the network is slow and thus many buildbot-tc client runs fail with just 1 test in t_client failing".

We should fix that :-) - like "if a small number of tests fail, try re-running them, and only complain if they still fail".

This might be nasty to do in shell or not - I have not looked into coding, just writing down ideas.

Dominant language
C
Stars
14.8k
Forks
3.4k
PR merge metrics
No merged PRs in 30d

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 OpenVPN/openvpn

All issues in OpenVPN/openvpn

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.