#18172: Random failure in singular leakcheck
--------------------------------------+------------------------
Reporter: vbraun | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.6
Component: packages: standard | Resolution:
Keywords: random_fail | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
--------------------------------------+------------------------
Comment (by nbruin):
This ticket triggered for me a problem with git and finding history: I
tried to find which ticket introduced the test in singular.polynomial, so
I looked with `git blame`. That found some relevant commits, but none of
them explicitly referred to a trac ticket and were otherwise terse,
descriptive commit messages.
By googling for one of the commit messages I quickly arrived at the trac
ticket which had a lot more history of the problem than the commits, but
I'm not sure we want to rely on external tools to document our history.
Am I missing some trick that reliably leads to the trac ticket from a git
commit? It is still often the case that trac ticket discussions contain a
lot of detail (sometimes even relevant) that the commit messages don't
(and probably shouldn't). I think it would be nice if we continue/resume
providing links from git commits to trac tickets.
--
Ticket URL: <http://trac.sagemath.org/ticket/18172#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
