Hi

On 27 September 2012 02:17, Dr. David Kirkby <david.kir...@onetel.net>wrote:

> On 26/09/2012 06:34, Jan Groenewald wrote:
>
>> Hi
>>
>> I saw all these errors compiling sage 5.3 from source with make testlong
>> (even more with make testalllong, though they seemed to expect magma to be
>> installed).
>>
>> model name    : Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz
>> http://users.aims.ac.za/~jan/**sage-5.3-ubuntu12.04.1-amd64-**
>> testlong.log.xz<http://users.aims.ac.za/~jan/sage-5.3-ubuntu12.04.1-amd64-testlong.log.xz>
>>
>> ------------------------------**------------------------------**
>> ----------
>> The following tests failed:
>>
>>
>>          sage -t  --long -force_lib
>> "devel/sage/doc/de/tutorial/**tour_advanced.rst"
>>
>
> <snip>
>
>
>  Total time for all tests: 10482.9 seconds
>>
>
> That is a lot of failures, but are any of them due to timeout? Over 10000
> seconds for the tests is a long time, so perhaps some are timing out. There
> is an environment variable that can control that - something like
> SAGE_TIMEOUT_LONG, but check the docs.
>

These tests kept failing. It is a make testalllong which led to many
failures includign many regarding magma, which is not installed.
Then I did make testlong which completed the build, and sag starts, but
with the errors above from testlong.log. The tests continue to fail, not
timeout.

Rebuilding from scratch worked perfectly with make testlong, with no errors.

I was just trying to find out what all the 'optional' versus 'all' versus
'long' options are in the Makefile,
as there seemed to be an excess of aliases in there.

Maybe someone can explain?

Regards,
Jan


-- 
  .~.
  /V\     Jan Groenewald
 /( )\    www.aims.ac.za
 ^^-^^

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.


Reply via email to