[sage-release] Re: Sage 10.1.beta7 released

2023-07-22 Thread Dave Morris
fwiw: Emmanuel's random seed gives me an AssertionError in beta2 and beta6, so I don't think this bug is new in beta7 (but maybe it got worse). On Saturday, July 22, 2023 at 3:44:06 AM UTC-6 Emmanuel Charpentier wrote: > On Debian testing running on core i7 + 16 GB RAM, upgrading 10.1.beta6 to

[sage-release] Re: Sage 10.1.beta7 released

2023-07-22 Thread Emmanuel Charpentier
On Debian testing running on core i7 + 16 GB RAM, upgrading 10.1.beta6 to 10.1.beta7 and ruunning ptestlong gives one new permanent failure : -- sage -t --long --warn-long 212.6

[sage-release] Re: Sage 10.1.beta7 released

2023-07-21 Thread Matthias Köppe
For the "# needs" tags (and block-scoped # optional tags) to have an effect, we need #35749, of course. But I prepared #35919 and #35951 in a way that all tests of the monolithic Sage library pass. On Friday, July 21, 2023 at 1:03:29 PM UTC-7 Kwankyu Lee wrote: > #35919 and #35951 merged here

[sage-release] Re: Sage 10.1.beta7 released

2023-07-21 Thread Kwankyu Lee
#35919 and #35951 merged here are dependent on #35749 not merged yet. #35749 is ready to be merged. It's a mistake that #35919 and #35951 did not declare #35749 as a dependency. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe