[sage-release] Re: Sage 8.9.beta9 released

2019-09-03 Thread John H Palmieri
With a Python 3 build on OS X, I get a sporadic failure in numerical/linear_tensor_element.pyx — it fails not every time, but at least half the time. As far as I can tell, this is due to #27587 (that is, I get failures with 8.9.beta8 + that ticket, but not with 8.9.beta8), but I don't

[sage-release] Re: Sage 8.9.beta9 released

2019-09-03 Thread Emmanuel Charpentier
On another maciine (Debian testing running on core i7 + 16 GB RAM), upgrading a Python 3-based Sage 8.9.beta8 to beta9 gives me the same permanent failure of prest-python3, pl;us another (also already reported): charpent@zen-book-flip:/usr/local/sage-P3-2$ sage -t --long --warn-long 157.5

[sage-release] Re: Sage 8.9.beta9 released

2019-09-03 Thread Emmanuel Charpentier
On Debian testing running on core i5 + 8 GB RAM, upgrading a Python 3-based Sage 8.9.beta8 to beta9 gives me one permanent failure of prest-python3, already multireported: charpent@p-202-021:/usr/local/sage-python3$ sage -t --long src/sage/rings/polynomial/polynomial_rational_flint.pyx too

[sage-release] Re: Sage 8.9.beta8 released

2019-09-03 Thread Sébastien Labbé
On Sage 8.9.beta8, running optional and external tests Using --optional=awali,cbc,cryptominisat,dot2tex,e_antic,external,glucose,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage I get:

Re: [sage-release] Sage 8.9.beta9 released

2019-09-03 Thread François Bissey
https://trac.sagemath.org/ticket/28271 broke the building of the pdf doc. See https://github.com/cschwan/sage-on-gentoo/issues/549 I’ll have a follow up at some point in the next 24hours. The ticket introduced a unicode “minus” sign at