On 07/28/10 12:00 PM, koffie wrote:
Hej David,
If you think that RAM exaustion is going to cause problems, why don't
you also add the recording of the memory useage in the doctesting (I
wouldn't now how to exactly do this but I guess you could use the
output of command line utilities such as top, vmstat/vm_stat or free).
If this would make the output of "sage -t" to long for the average
user/debugger you could always make a verbose and/or memory option to
the doctesting which could be used by running "sage -tv" or "sage -tm"
or or something alike.
I hope you find these ideas usefull.
Kind Rigards,
Maarten Derickx
I believe any number of problems on the system could cause build or doctests
failures. I think it would just be easier to record the time. There is a plan to
create a script which would aid debugging by collecting system information
http://trac.sagemath.org/sage_trac/ticket/8048
but I would not suggest printing that out each time there's a doctest failure.
I had a build fail on t2.math. When I look in the system logs I see
Jul 25 16:11:07 t2 tmpfs: [ID 518458 kern.warning] WARNING: /tmp: File system
full, swap space limit exceeded
Jul 25 16:11:07 t2 last message repeated 25 times
Had that been a doctest failure, it would have been useful to know the time of
the failure. If it was around 16:11:07 on 25th July, I would have suspected that
as a problem.
Getting the date is probably trivial and can be put on one line. Getting
information about all possible problems on all platforms would be a lot more
difficult. It''s not only RAM. For examples I see NFS related errors
Jul 26 19:41:59 t2 nfs: [ID 220977 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS op OP_CLOSE got error 4 causing recovery action
NR_LOST_STATE_RQST.
Jul 26 19:41:59 t2 nfs: [ID 814820 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]Lost OP_CLOSE request for fs /home, file
./mpatel/.sage/temp/t2/20720/qsieve_0/tmp2.1117.21848
Had mpatel's build failed there, we could have suspected that as a problem.
There are lots of people working on improving the doctest framework. If there
was a consensus to record the date/time of any failures, I would suggest adding
it, but so far nobody has really felt it is worthwhile other than me!
I would suggest having something like:
sage -t -long devel/sage/sage/geometry/cone.py
**********************************************************************
File
"/rootpool2/local/kirkby/sage-4.5.2.alpha0-9343/devel/sage-main/sage/geometry/cone.py",
line 559:
sage: c = Cone([(1,0), (0,1)])
Expected:
4372618627376133801
Got nothing
**********************************************************************
1 items had failures:
1 of 3 in __main__.example_7
***Test Failed*** 1 failures.
For whitespace errors, see the file
/rootpool2/local/kirkby/.sage//tmp/.doctest_cone.py
[66.6 s at Wed Jul 28 07:38:15 EDT 2010]
I also think it would be useful to add the hostname and operating system
somewhere in the log file use for testing, though that only needs doing once,
not on every line.
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
