Dr. David Kirkby wrote:
> I've just tried the patch at
> 
> http://sagetrac.org/sage_trac/ticket/6788
> 
> It does not appear to have solved my problem, but it highlights one that 
> has bugged me for some time - one where running doctests can bring the 
> machine to an almost standstill.

I did not get much response (well none actually) about this issue. But I 
went out today and run the doctests. They finished, with failures (see 
the end), but more to the point, look at the state of the machine.

   PID USERNAME  SIZE   RSS STATE  PRI NICE      TIME  CPU PROCESS/NLWP
  27695 drkirkby   30M   19M run     23    0   1:06:38 5.0% maxima/1
   2662 drkirkby   30M   13M run     33    0   2:38:10 5.0% maxima/1
  27740 drkirkby   30M   23M run     33    0   0:36:50 4.8% maxima/1
  23278 drkirkby  341M  262M sleep   49    0   0:09:11 3.5% 
thunderbird-bin/8
    692 drkirkby  249M  105M run     59    0   4:09:46 3.3% Xsun/1
      1 root     2896K 1048K sleep   59    0   1:22:54 2.3% init/1
    906 drkirkby  103M   38M sleep   59    0   0:14:17 1.6% metacity/1
  10854 drkirkby  242M  175M sleep   59    0   1:07:33 1.5% firefox-bin/9
    962 drkirkby  134M   94M sleep   59    0   0:43:24 1.2% gnome-terminal/2
   6912 drkirkby  152M   50M sleep   49    0   0:31:12 0.5% python/1
  29808 drkirkby  172M  101M sleep   49    0   0:10:21 0.5% python/1
  12516 drkirkby  152M   65M sleep   49    0   0:16:28 0.5% python/1
    925 drkirkby  101M   35M run     49    0   0:04:21 0.4% wnck-applet/1
    912 drkirkby   82M   37M sleep   59    0   0:00:37 0.3% nautilus/5
  23632 drkirkby 4712K 1728K sleep   49    0   0:08:27 0.2% prstat/1
  10807 drkirkby   20M   13M sleep   49    0   0:30:51 0.2% sunpcbinary/3
   9116 drkirkby 3440K 2544K sleep   52    0   0:00:00 0.2% bash/1
   9810 drkirkby 3832K 3088K cpu1    52    0   0:00:00 0.1% prstat/1
    970 drkirkby  232M   68M run     49    0   0:11:09 0.1% java/18
  29302 drkirkby  214M  126M sleep   49    0   0:01:22 0.1% acroread/1
    903 drkirkby   12M 1168K sleep   59    0   0:01:07 0.1% gnome-smproxy/1
Total: 150 processes, 358 lwps, load averages: 8.70, 8.70, 8.79


There's 3 maxima processes still running, when there should be non. For 
some reason they are not using a high percentage of CPU time, but the 
load average is very high. I've had this before, and will have to find 
out what it was (it would not surprise me if it Sage related, as the 
machine was fine when I went out earlier). But now you can see, there 
are maxima processes running. Tests are failing, but not killing the 
processes.


Here are the failures. I had increased the timeout to 1800 second (half 
an hour) just in case any that were timing out were doing so as my 
machine is not sufficiently fast.

sage -t  "devel/sage/sage/modules/vector_integer_sparse_h.pxi"
          [2.9 s]

----------------------------------------------------------------------
The following tests failed:


         sage -t  "devel/sage/sage/server/simple/twist.py"
         sage -t  "devel/sage/sage/rings/tests.py"
         sage -t  "devel/sage/sage/graphs/graph.py"
         sage -t  "devel/sage/sage/graphs/graph_database.py"
         sage -t  "devel/sage/sage/graphs/graph_list.py"
         sage -t  "devel/sage/sage/databases/database.py"
         sage -t  "devel/sage/sage/symbolic/assumptions.py"
         sage -t  "devel/sage/sage/misc/randstate.pyx"
         sage -t  "devel/sage/sage/misc/getusage.py"
         sage -t  "devel/sage/sage/misc/latex.py"
         sage -t 
"devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py"
         sage -t  "devel/sage/sage/libs/pari/gen.pyx"
         sage -t  "devel/sage/sage/interfaces/maxima.py"
         sage -t  "devel/sage/sage/interfaces/rubik.py"
         sage -t  "devel/sage/sage/interfaces/sage0.py"
         sage -t  "devel/sage/sage/interfaces/tests.py"
         sage -t  "devel/sage/sage/interfaces/expect.py"
         sage -t  "devel/sage/sage/interfaces/psage.py"
         sage -t  "devel/sage/sage/geometry/lattice_polytope.py"
         sage -t  "devel/sage/sage/gsl/integration.pyx"
         sage -t  "devel/sage/sage/gsl/interpolation.pyx"
Total time for all tests: 90229.7 seconds
However, an ERROR occurred in the Distributed Sage unit tests.
Please see /export/home/drkirkby/.sage//tmp/test.log for the complete 
log from this test.

Does anyone have any idea why the maxima processes are not being killed? 
It's difficult to doctest Sage if doing so causes such a huge load, due 
to processes not being killed.

Dave



--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to