make test fails

3 views
Skip to first unread message

Kevin Horton

unread,
May 18, 2009, 5:14:02 PM5/18/09
to spd...@googlegroups.com
SPD built on my EeePC 901. I then tried "make test", to see if that
shook out any issues. It failed immediately with:

. local/bin/sage-env && sage-starts && sage-maketest
Testing that Sage starts...
/home/user/apps/spd-3.4.2spd2/local/bin/sage-starts: line 11: sage:
command not found
Sage failed to startup.
make: *** [test] Error 1

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++

I tried bypassing the sage-starts script, but this still failed, as it
attempts to test packages that are not installed:

. local/bin/sage-env && sage-maketest
Detected SAGE64 flag
dsage-trial tmp directory doesn't exist - creating ...
This script will run the unit tests for DSage
[ERROR
]

=
=
=
=
=
=
=
========================================================================
[ERROR]: sage.dsage

Traceback (most recent call last):
File "/home/user/apps/spd-3.4.2spd2/local/lib/python2.5/site-
packages/twisted/trial/runner.py", line 623, in loadByNames
things.append(self.findByName(name))
File "/home/user/apps/spd-3.4.2spd2/local/lib/python2.5/site-
packages/twisted/trial/runner.py", line 445, in findByName
return reflect.namedAny(name)
File "/home/user/apps/spd-3.4.2spd2/local/lib/python2.5/site-
packages/twisted/python/reflect.py", line 432, in namedAny
obj = getattr(obj, n)
exceptions.AttributeError: 'module' object has no attribute 'dsage'
-------------------------------------------------------------------------------

FAILED (errors=1)
However, an ERROR occurred in the Distributed Sage unit tests.
/home/user/apps/spd-3.4.2spd2/local/bin/sage-maketest: line 26: /home/
user/apps/spd-3.4.2spd2/sage: No such file or directory
However, an ERROR occurred in the Distributed Sage unit tests.
Please see /home/user/apps/spd-3.4.2spd2/tmp/test.log for the complete
log from this test.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++

I note that the README appears to be identical to the sage README -
e.g. it tells you to start sage, rather than spd, etc.

--
Kevin Horton
Ottawa, Canada

Brian Granger

unread,
May 18, 2009, 5:33:13 PM5/18/09
to spd...@googlegroups.com
Yes, I am not surprised the test infrastructure doesn't work. We
haven't done any work on it and it probably relies on parts of Sage
that we don't include (like most of it!).

Brian

Ondrej Certik

unread,
May 18, 2009, 5:36:15 PM5/18/09
to spd...@googlegroups.com
Hi Kevin!

On Mon, May 18, 2009 at 2:14 PM, Kevin Horton <khor...@rogers.com> wrote:
>

> SPD built on my EeePC 901.  I then tried "make test", to see if that

Excellent, I am glad it built.

The tests don't work, as this relies on Sage doctests, that are mostly
in the sage.spkg, which we do not ship. Thanks for pointing this out,
I haven't thought about tests yet. The packages themselves don't have
any tests.

[...]


> I note that the README appears to be identical to the sage README -
> e.g. it tells you to start sage, rather than spd, etc.

This is a bug, and I made it:

http://code.google.com/p/spdproject/issues/detail?id=16

Thanks for reporting it.


Ondrej

Reply all
Reply to author
Forward
0 new messages