I see the same failures on a laptop with an M2 chip.
On Tuesday, May 16, 2023 at 12:58:56 PM UTC-7 John H Palmieri wrote:
> On an iMac Pro (some Intel chip), the first failure
> (rings/polynomial/multi_polynomial_ideal.py) is also related to giac:
>
> sage: A9=PolynomialRing(QQ,9,'x') ## line
On an iMac Pro (some Intel chip), the first failure
(rings/polynomial/multi_polynomial_ideal.py) is also related to giac:
sage: A9=PolynomialRing(QQ,9,'x') ## line 4225 ##
sage: I9=sage.rings.ideal.Katsura(A9) ## line 4226 ##
sage: print("possible output from giac", flush=True);
I also had the same failures since several versions on Mac OS 13.3.1a with
Intel Core i5 machine.
2023年5月15日(月) 23:13 John H Palmieri :
> I consistently see these failures on various OS X machines:
>
> sage -t --long --random-seed=244618093388694547212515065258622925284
>
On Tuesday, May 16, 2023 at 6:13:03 AM UTC+9 John H Palmieri wrote:
I consistently see these failures on various OS X machines:
sage -t --long --random-seed=244618093388694547212515065258622925284
src/sage/rings/polynomial/multi_polynomial_ideal.py # 1 doctest failed
sage -t --long
I consistently see these failures on various OS X machines:
sage -t --long --random-seed=244618093388694547212515065258622925284
src/sage/rings/polynomial/multi_polynomial_ideal.py # 1 doctest failed
sage -t --long --random-seed=244618093388694547212515065258622925284
Note that what's left in the 10.0 milestone is already
hand-picked. https://github.com/sagemath/sage/milestone/152
In particular, could you please merge
https://github.com/sagemath/sage/pull/35460 (the update to our developer's
guide for GitHub -- didn't you say the transition to GitHub is
On Sunday, May 14, 2023 at 11:05:19 AM UTC+2 Dima Pasechnik wrote:
i.e. PRs 35637 and 35638
OK, will do.
--
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
On Sun, 14 May 2023, 09:48 Volker Braun, wrote:
> As always, only blockers are merged in release candidates. If a normal
> ticket is not done during the normal merge window then its not going in,
> otherwise we never finish making a release.
>
Volker, can you at least merge small documentation
As always, only blockers are merged in release candidates. If a normal
ticket is not done during the normal merge window then its not going in,
otherwise we never finish making a release.
On Saturday, May 13, 2023 at 11:54:55 PM UTC+2 matthia...@gmail.com wrote:
Other relevant tickets for the
Thanks for the new rc. Tests ran
at https://github.com/sagemath/sage/actions/runs/4962805314
All "standard" configurations on the tested Linux platform look OK - except:
- ubuntu-kinetic-standard
(https://github.com/sagemath/sage/actions/runs/4962805314/jobs/8884806221):
Segmentation faults in
10 matches
Mail list logo
