#18894: Automatic build error reporting
--------------------------------+------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.8
Component: distribution | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
--------------------------------+------------------------
Comment (by jdemeyer):
There are several points here I don't agree with or don't understand:
> * Only output from '''failed''' builds (and perhaps hung processes)
should ever be dumped to the console
Why? If people type `make` and they see nothing, they will surely think
there is a problem. I think it's good that people see that stuff is
happening.
> * replace `tee` with a python script that logs without spewing forth
endless output
I guess the "spewing forth endless output" part also refers to not dumping
output to the console?
> * Logs should always only be a single build log, and never have logs
from multiple builds concatenated
We have logs for individual packages (`logs/pkgs/gap-4.8.4.log`) and one
log with everything (`logs/install.log`). Both have reasons to exist
(`install.log` can diagnose race conditions in parallel builds).
And all this is obviously too much for one ticket. For example, the part
about replacing `tee` should be a ticket by itself.
--
Ticket URL: <http://trac.sagemath.org/ticket/18894#comment:2>
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.
