Opened at 2019-08-13T18:58:41Z
Closed at 2019-08-13T22:22:30Z
#3238 closed defect (fixed)
Make CI not fail because of PyPy job failures
| Reported by: | exarkun | Owned by: | GitHub <noreply@…> |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | unknown | Version: | n/a |
| Keywords: | review-needed | Cc: | |
| Launchpad Bug: |
Description
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2479 introduced PyPy? CI. It was supposed to be an "expected fail" job on CI but the logic to make it so seems to have ... failed. That's not irony. That's software.
This pollutes CI results with constantly meaningless failures. Fix it.
Change History (2)
comment:1 Changed at 2019-08-13T20:25:35Z by exarkun
- Keywords review-needed added
comment:2 Changed at 2019-08-13T22:22:30Z by GitHub <noreply@…>
- Owner set to GitHub <noreply@…>
- Resolution set to fixed
- Status changed from new to closed
In b49ac06/trunk:
Note: See
TracTickets for help on using
tickets.
https://github.com/tahoe-lafs/tahoe-lafs/pull/644