#12486: Add patchbot to Sage itself.
----------------------------------------------+-----------------------------
Reporter: robertwb | Owner: mvngu
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.1
Component: doctest | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Robert Bradshaw, Dan Drake | Merged in:
Dependencies: | Stopgaps:
----------------------------------------------+-----------------------------
Comment (by jdemeyer):
Is there a way how "state" could be preserved across patchbot runs? Could
it happen that the patchbot tests ticket X and somehow ticket X has a bug
causing failures in ''following'' tickets the patchbot tests? Because it
looks like this is happening here.
I did 600 test runs of `maxima_abstract.py` on vanilla sage-5.1.beta2 and
found no error. Nobody has reported this bug on the mailing list and I
haven't seen it on the buildbot with sage-5.1.beta2 or earlier. So I
conclude that the bug is introduced by a not-yet-merged ticket.
Since it is extremely unlikely that all the tickets in kini's list above
cause the same bug, the most logical explanation is that somehow one
ticket corrupted further patchbot runs.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12486#comment:19>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
