Ready for review.
On Wednesday, 9 November 2022 at 11:36:51 UTC+1 axio...@yahoo.de wrote:
> The findstat errors are now tracked in
> https://trac.sagemath.org/ticket/34734
>
> On Tuesday, 8 November 2022 at 16:25:58 UTC+1 axio...@yahoo.de wrote:
>
>> The findstat errors very likely occur because
The findstat errors are now tracked in
https://trac.sagemath.org/ticket/34734
On Tuesday, 8 November 2022 at 16:25:58 UTC+1 axio...@yahoo.de wrote:
> The findstat errors very likely occur because findstat switched to python3
> last weekend. Some of these might be upstream errors, many thanks f
The findstat errors very likely occur because findstat switched to python3
last weekend. Some of these might be upstream errors, many thanks for the
report!
Are you going to open a ticket, or should I do it?
Martin
On Monday, 7 November 2022 at 13:52:05 UTC+1 Sébastien Labbé wrote:
> On Ubun
On Ubuntu 18.04, with few optional/external packages, here is what I get:
Running with SAGE_LOCAL='/home/slabbe/GitBox/sage/local' and
SAGE_VENV='/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.10.8'
Using --optional=build,debian,external,glucose,pip,sage,sage_spkg
Features to be detecte
On Debian testing running on core i7 + 16 GB RAM, avter installing the
msolve package (which trigerred the reinstallation of some packages, among
them pari and giac), upgrading 9.8.beta2 to 9.8.beta3 and running ptestlong
gives three failures` :
---
Thanks for the new release.
On Ubuntu 20.04 running on Xeon E5-2623 + 16 GB RAM:
- incremental build (-j16) from 9.8.beta2, with system python (3.8.10): OK
- make ptestlong --> "All tests passed!"
Eric.
--
You received this message because you are subscribed to the Google Groups
"sage-releas
