Thanks for the release.
On Ubuntu 14.04 I get LOTS of test timeouts that I didn't get
previously. It's possible though that the system is just uder heavy
load, but even re-running the tests with --failed keeps giving me
timeouts for some modules. So I'm concerned about a real performance
regression somewhere. I'm running ./sage -t -a --failed yet again,
but from my last run I got:
sage -t src/sage/libs/gap/all_documented_functions.py # Timed out
sage -t src/sage/libs/gap/assigned_names.py # Timed out
sage -t src/sage/manifolds/differentiable/affine_connection.py # Timed out
sage -t src/sage/manifolds/differentiable/euclidean.py # Timed out
sage -t src/sage/manifolds/differentiable/metric.py # Timed out
sage -t src/sage/manifolds/differentiable/multivectorfield.py # Timed out
sage -t src/sage/manifolds/differentiable/tensorfield.py # Timed out
sage -t src/sage/plot/plot.py # Timed out
sage -t src/sage/rings/padics/padic_base_leaves.py # Timed out
sage -t src/sage/rings/padics/padic_lattice_element.py # Timed out
(and interrupt failed)
Will try 16.04 (the current base for my Docker images) and 18.04 next.
> email to sage-release+unsubscribe@googlegroups.com.
> To post to this group, send email to sage-r...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscribe@googlegroups.com.
Bionic 18.04 AMD x8 64 bits, compile perfect. I started from
fresh git sage because upgrading from 8.2 failed. It couldn't find
many libs. By the way I found my crash problem while compiling : I
had to config the bios allowing warmer processing.
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscribe@googlegroups.com.
To post to this group, send email to sage-r...@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscribe@googlegroups.com.
Yes I did! I had installed some stuff needed for LMFDB using sage -i pip instal ... and it told me my pip was not the most recent and should be upgraded, so I did.
On 2018-05-16 17:26, Erik Bray wrote:
I'm not sure, but I think this might be pip-related. I think Jeroen
mentioned something about this to me a couple weeks ago. Is it
possible you upgraded the pip in your Sage install?
Indeed, I guess you are using pip 10 by accident.
It might be a good idea to upgrade the pip in Sage and fix this issue.
On Ubuntu 16.04, the command `./sage -t -p --all --long --optional=sage,optional,external` finishes with:
----------------------------------------------------------------------
sage -t --long src/sage/coding/code_constructions.py # 1 doctest failed
----------------------------------------------------------------------
Total time for all tests: 1821.3 seconds
cpu time: 11639.5 seconds
cumulative wall time: 14059.4 seconds
External software detected for doctesting: gurobi,latex
Traceback (most recent call last):
File "/home/slabbe/GitBox/sage/src/bin/sage-runtests", line 127, in <module>
err = DC.run()
File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 1176, in run
+ ','.join(available_software.seen()))
File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 583, in log
self.logger.write(s + end)
File "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 250, in write
f.write(x)
ValueError: I/O operation on closed file
--