Opened 22 months ago

Last modified 6 months ago

#28037 new enhancement

Document how to fix or disable failing CI

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-doc, tor-ci, postfreeze-ok, teor-unreached-2019-03-08, doc, 041-deferred-20190719
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We want our CI to always be passing.

Sometimes, we can fix the bug quickly, or revert the commit.
But if the CI environment is broken, we need to disable the failing test cases until the bug is fixed.

In doc/HACKING, document how to disable failing CI jobs.
In the Travis and Appveyor configs, summarise or give an example of how to disable a failing CI config.

Child Tickets

Change History (8)

comment:1 Changed 21 months ago by nickm

Milestone: Tor: 0.3.6.x-finalTor: 0.4.0.x-final

Tor 0.3.6.x has been renamed to 0.4.0.x.

comment:2 Changed 19 months ago by nickm

Keywords: postfreeze-ok added

Mark some tickets as postfreeze-ok, to indicate that I think they are okay to accept in 0.4.0 post-freeze. Does not indicate that they are all necessary to do postfreeze.

comment:3 Changed 17 months ago by teor

Keywords: teor-unreached-2019-03-08 added
Owner: teor deleted

I'd like to do these tickets, but not in the next few months.

comment:4 Changed 15 months ago by nickm

Keywords: 041-should added
Milestone: Tor: 0.4.0.x-finalTor: 0.4.1.x-final

comment:5 Changed 15 months ago by nickm

Keywords: doc added

Mark a few documentation tickets as "doc"

comment:6 Changed 13 months ago by nickm

Keywords: 041-deferred-20190719 added; 041-should removed

Add 041-deferred-20190719 tag to 041-should tickets I am deferring today.

comment:7 Changed 13 months ago by nickm

Milestone: Tor: 0.4.1.x-finalTor: unspecified

comment:8 Changed 6 months ago by teor

Status: assignednew

Change tickets that are assigned to nobody to "new".

Note: See TracTickets for help on using tickets.