real 26m50.752s
user 18m1.080s
sys 1m14.949s
user and sys time are sightly smaller than on my machine,
but real time is much bigger. It seems that Closure Cl
must be waiting for something, maybe it access files on
NFS?
Certainly not. That's a laptop and has no access to NFS. Everything done
on the local harddisk (no SSD). If you have an idea where to monitor
what caused that long time, I'd be very grateful.
Yes, I would like to add 'make check'. However, I do not think
we should run all things in 'src/input', for example 'marcbench'
is more a benchmark than a test, and 'mapleok' and 'r21bugsbig'
are also not usual tests. Actually, people want 'make check'
to give easy to interpret result like yes/no or number of
failing tests, so I think about running just tests handled
by unit testing machinery and add some summary feature.
As you know, I've once started another test machinery.
http://groups.google.com/group/fricas-devel/browse_thread/thread/b553b809698a9bd2
I haven't looked at it for a while, but I still want autotools for all
of fricas. I know that automake doesn't help much with the lisp stuff,
but it can generate all the boilerplate for testing.
Meanwhile I'd like to setup a local environment where I take more care
on different lisps and always running the tests. I more or less want to
automate all this.
Finding the place where the aldor-interface broke was good to learn
about git bisect, but eventually, I'd like to get automatically notified
when it (or any other part of fricas) break again.
Ralf
--
You received this message because you are subscribed to the Google Groups "FriCAS -
computer algebra system" 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/fricas-devel?hl=en.
