3 | | > |
4 | | > ---------------------------------------------------------------------- |
5 | | > The following tests failed: |
6 | | > |
7 | | > sage -t -long |
8 | | > "rro/sage-4.4.4.alpha1/devel/sage/sage/interfaces/maxima.py" # |
9 | | > Killed/crashed |
| 3 | $ ./sage -t devel/sage/sage/interfaces/maxima.py |
| 4 | sage -t "devel/sage/sage/interfaces/maxima.py" |
| 5 | *** *** Error: TIMED OUT! PROCESS KILLED! *** *** |
| 6 | |
| 7 | [361.3 s] |
| 8 | |
| 9 | ---------------------------------------------------------------------- |
| 10 | The following tests failed: |
| 11 | |
| 12 | |
| 13 | sage -t "devel/sage/sage/interfaces/maxima.py" # Time out |
| 14 | Total time for all tests: 361.3 seconds |
11 | | This is due to the commands in this file which create the tab completion list for use with Sage's Maxima; for some reason even when done 'by hand' they often time out, and since they happen a few different times in this file it will nearly always time out (even with huge `SAGE_TIMEOUT` set). |
| 16 | This is because on OS X 10.4, maxima takes a long time (a few seconds to a minute) to process an interrupt. Sage only waits 2 seconds for an interrupt and thinks that Maxima is stuck. It naively sends more interrupts which totally lock up Maxima. The work-around is simply to send only 1 interrupt and wait... |
| 17 | |
| 18 | With the patch: |
| 19 | {{{ |
| 20 | $ ./sage -t devel/sage/sage/interfaces/maxima.py |
| 21 | sage -t "devel/sage/sage/interfaces/maxima.py" |
| 22 | [129.5 s] |
| 23 | |
| 24 | ---------------------------------------------------------------------- |
| 25 | All tests passed! |
| 26 | Total time for all tests: 130.0 seconds |
| 27 | }}} |