Opened 4 years ago
Closed 16 months ago
#23832 closed task (invalid)
Optional packages and patchbots metaticket
Reported by: | mderickx | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
Component: | misc | Keywords: | |
Cc: | Merged in: | ||
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
The goal of this metaticket is to make it easy to see if there is already a ticket for failures of some patchbots (including building optional packages). If a patchbot failure is not on the list, please make ticket with blocker
priority for it, if it does not yet exist and add it here together with a list of the affected files!
8.3.beta2
- #25399 (automorphism groups)
- #25398 (plantri feature)
- #25400 (LattE feature)
8.3.beta0
8.2.beta6
#23533 cryptominisat fails to build
#24902 deformation fails to build
8.1.rc0
#22006 CBC causes doctest failures because of linking with incompatible liblapack
sage -t --long src/sage/knots/link.py # 1 doctest failed sage -t --long src/sage/game_theory/normal_form_game.py # 5 doctests failed sage -t --long src/sage/numerical/backends/coin_backend.pyx # 314 doctests failed
#23933 OpenBLAS randomly crashes / deadlocks 2 - arando
sage -t --long src/sage/matrix/matrix_integer_dense.pyx
#23391 Test timeout in FFPACK::CharPoly? (related #21579) - multscher
src/sage/graphs/matchpoly.pyx
Only occurs once in a hundred times or so, so one needs to do:
for i in `seq 0 1000` ; do sage -t --long src/sage/graphs/matchpoly.pyx ; done
At least on OpenSuSE:
Change History (48)
comment:1 Changed 4 years ago by
- Description modified (diff)
comment:2 Changed 4 years ago by
- Description modified (diff)
comment:3 Changed 4 years ago by
- Component changed from doctest framework to misc
- Description modified (diff)
- Milestone changed from sage-8.1 to sage-duplicate/invalid/wontfix
comment:4 Changed 4 years ago by
- Description modified (diff)
comment:5 Changed 4 years ago by
- Description modified (diff)
comment:6 Changed 4 years ago by
- Description modified (diff)
comment:7 Changed 4 years ago by
- Description modified (diff)
comment:8 Changed 4 years ago by
- Description modified (diff)
comment:9 Changed 4 years ago by
- Description modified (diff)
comment:10 Changed 4 years ago by
- Description modified (diff)
comment:11 Changed 4 years ago by
- Description modified (diff)
comment:12 Changed 4 years ago by
- Description modified (diff)
comment:13 Changed 4 years ago by
- Description modified (diff)
comment:14 Changed 4 years ago by
- Description modified (diff)
comment:15 Changed 4 years ago by
- Description modified (diff)
comment:16 Changed 4 years ago by
- Description modified (diff)
comment:17 Changed 4 years ago by
- Description modified (diff)
comment:18 Changed 4 years ago by
- Description modified (diff)
comment:19 Changed 4 years ago by
- Description modified (diff)
comment:20 Changed 4 years ago by
- Description modified (diff)
comment:21 Changed 4 years ago by
- Description modified (diff)
I agree, but I prefer we just remove them depending on the beta version in which things were fixed. And just keep the things from the most recent beta and the previous one here. Since that info might still be usefull.
comment:22 Changed 4 years ago by
p.s. Jeroen what do you think about the priority of reproducible but random failing doctests? Say it fails about once in x
times where x
is some number.
I have the feeling that failing (but not silently producing incorrect answers) one out of three tests should definitely still be blocker priority, and failing (but not silently) once in every 10^{6} times does not deserve to be a blocker anymore. What would be a reasonable guideline for a cutoff? Once in a hundred?
Of course creating a stopgap for something that silently produces the wrong answer deserves to be a blocker no matter how rare.
comment:23 Changed 4 years ago by
- Description modified (diff)
comment:24 Changed 4 years ago by
- Description modified (diff)
comment:25 Changed 4 years ago by
- Description modified (diff)
comment:26 Changed 4 years ago by
- Description modified (diff)
comment:27 Changed 4 years ago by
- Description modified (diff)
comment:29 Changed 4 years ago by
- Description modified (diff)
comment:30 Changed 4 years ago by
- Description modified (diff)
comment:31 Changed 4 years ago by
- Description modified (diff)
comment:32 Changed 4 years ago by
- Description modified (diff)
comment:33 Changed 4 years ago by
- Description modified (diff)
comment:34 Changed 4 years ago by
- Description modified (diff)
comment:35 Changed 4 years ago by
- Description modified (diff)
- Summary changed from Patchbot failure metaticket to Optional packages and patchbots metaticket
comment:36 Changed 4 years ago by
- Description modified (diff)
comment:37 Changed 4 years ago by
- Description modified (diff)
comment:38 Changed 4 years ago by
- Description modified (diff)
comment:39 Changed 4 years ago by
- Description modified (diff)
comment:40 Changed 4 years ago by
- Description modified (diff)
comment:41 Changed 4 years ago by
- Description modified (diff)
comment:42 Changed 3 years ago by
- Description modified (diff)
comment:44 Changed 3 years ago by
- Description modified (diff)
comment:45 Changed 3 years ago by
- Description modified (diff)
comment:46 Changed 3 years ago by
- Description modified (diff)
comment:47 Changed 18 months ago by
- Status changed from new to needs_review
outdated, should be closed
comment:48 Changed 16 months ago by
- Resolution set to invalid
- Status changed from needs_review to closed
I think we can remove the fixed issues, otherwise this will get long very fast.