#10098: Flaky doctest in sage/interfaces/expect.py
-----------------------+----------------------------------------------------
Reporter: mpatel | Owner: mvngu
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.6
Component: doctest | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by drkirkby):
I think this shows the value of a suggestion I've made before on other
ticket(s).
If we knew the exact date/time of the tests (pass or fail), we could look
at the logs on the machine and see if there was a problem. Problems with
NFS are often logged - I've seen them logged on t2.math, when William had
disabled the ZIL. We can even tie them up with user name - here's a few
errors logged for both Simon and John.
{{{
Sep 12 09:05:40 t2 nfs: [ID 814820 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]Lost OP_CLOSE request for fs /home, file
./palmieri/.sage-t2/temp/t2/23760/qsieve_0/lprels.1005.23843 (rn
ode_pt: 0x30009d028d8), dir <null string> (0x0) for server disk
Sep 12 09:05:40 t2 nfs: [ID 581112 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS Starting recovery for mount /home (mi 0x60040c42000
mi_recovflags [0x40]) on server disk, rnode_pt1 .
/palmieri/.sage-t2/temp/t2/23760/qsieve_0/lprels.1005.23843
(0x30009d028d8), rnode_pt2 <null string> (0x0)
Sep 12 09:05:40 t2 nfs: [ID 273629 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS Recovery done for mount /home (mi 0x60040c42000) on
server disk, rnode_pt1 ./palmieri/.sage-t2/temp/t
2/23760/qsieve_0/lprels.1005.23843 (0x30009d028d8), rnode_pt2 <null
string> (0x0)
Sep 12 09:05:40 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.
Sep 12 09:05:40 t2 nfs: [ID 814820 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]Lost OP_CLOSE request for fs /home, file
./palmieri/.sage-t2/ipython/history-sage (rnode_pt: 0x300375c68f
0), dir <null string> (0x0) for server disk
Sep 12 09:05:40 t2 nfs: [ID 581112 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS Starting recovery for mount /home (mi 0x60040c42000
mi_recovflags [0x40]) on server disk, rnode_pt1 .
/palmieri/.sage-t2/ipython/history-sage (0x300375c68f0), rnode_pt2 <null
string> (0x0)
Sep 12 09:05:40 t2 nfs: [ID 273629 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS Recovery done for mount /home (mi 0x60040c42000) on
server disk, rnode_pt1 ./palmieri/.sage-t2/ipytho
n/history-sage (0x300375c68f0), rnode_pt2 <null string> (0x0)
Sep 12 09:05:40 t2 nfs: [ID 236337 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS op OP_CLOSE got error NFS4ERR_STALE causing
recovery action NR_STALE.
Sep 12 09:05:40 t2 nfs: [ID 286389 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]File ./SimonKing/.sage/temp/t2/13276/dir_2/.nfsD44308
(rnode_pt: 3000da37bd8) was closed due to NFS recov
ery error on server disk(failed to recover from NFS4ERR_STALE
NFS4ERR_STALE)
}}}
If the doc tests had the exact times, it would go some way to helping
determine if the system detected a problem.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10098#comment:8>
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.
