wiki:org/teams/NetworkTeam/CIFailures

CI Failures

This page lists the CI failures for the network team.

It's based on the Network Team's 0.4.0 Release Status page, and teor's user page.

CI Builders

Jenkins builds our supported branches and Debian packages for deb.torproject.org. Notifications go to #tor-bots on irc.oftc.net.

Travis and Appveyor build GitHub pull requests, personal repositories, and our supported branches. Notifications go to #tor-ci on irc.oftc.net.

Handling CI Failures

We want to log every CI failure in trac, so we can see which CI issues we need to fix first.

Supported Branches

We want CI to always pass on supported branches.

When CI fails on:

  • master, a supported maint branch, or a supported release branch, or
  • a pull request, but it's not related to the changes in the pull request.
  1. Find the failure log message, the failed branch, and the merge head (if it's a pull request).
  2. If there is an existing ticket, log that information on the existing ticket.
  3. Otherwise, log a ticket tagged "tor-ci-fail" with the information, and mark it as high priority.
  4. If the failure is on an earlier supported branch, update the version and backport tags to that branch.

Pull Requests

When CI fails on a pull request, and it was caused by the changes in the pull request, mark the ticket for that pull request as needs_revision.

CI Failure Tickets

Unassigned tickets

These open tickets are tagged ci-fail, and they don't have an owner.

TODO: who will assign them to the best person to fix the ticket?

Owner: (none) (2 matches)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#30235 Stem hangs waiting for control port data needs_information Medium Normal 2 months ago
#29437 test-stem times out intermittently assigned Medium Normal 2 months ago

Owner Action tickets

These tickets are tagged ci-fail, they have an owner, and they are in a status that needs action from the owner.

Anyone can change the assignments:

  • assign themselves one of these tickets,
  • un-assign ticket from themselves, or
  • ask someone else to take one of their tickets.

Owner: teor (1 match)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#30901 Add control port trace logging to tor needs_revision teor Medium Normal 2 days ago

Needs Review tickets

These tickets are tagged ci-fail, and they are in needs_review.

Reviewer: juga (1 match)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#30909 sbws consensus timestamp updates incorrectly use the current time needs_review teor juga Medium Normal 6 weeks ago

Merge Ready tickets

These tickets are tagged ci-fail, and they are in merge_ready.

Ticket Summary Status Owner Reviewer Priority Severity Modified
No tickets found

Last modified 5 months ago Last modified on Apr 5, 2019, 12:06:54 AM