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

2018-10-03 Thread tscrim
On Wednesday, October 3, 2018 at 7:35:08 PM UTC+10, Kwankyu Lee wrote: > > > > On Wednesday, October 3, 2018 at 3:14:32 PM UTC+9, tsc...@ucdavis.edu > wrote: >> >> I believe there is a Heisenbug in src/sage/rings/function_field/ideal.py. >> Here is a specific test that can sometimes fail: >>

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

2018-10-03 Thread tscrim
I believe there is a Heisenbug in src/sage/rings/function_field/ideal.py. Here is a specific test that can sometimes fail: sage: K. = FunctionField(GF(3^2)); R. = K[] sage: F. = K.extension(t^3 + t^2 - x^4) sage: Oinf = F.maximal_order_infinite() sage: I = Oinf.ideal(1/y) sage: I.factor() #

Re: [sage-release] Re: Sage 8.4.beta3 released

2018-09-06 Thread tscrim
I also sampled a few of the other mirrors and got the same resulting md5sum and checksum, which is different from the one in build/pkgs/configure/checksums.ini. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe

Re: [sage-release] Re: Sage 8.4.beta3 released

2018-09-06 Thread tscrim
I got a report of someone getting an invalid checksum using the configure-280.tar.gz on one of the mirrors (using a fresh git clone): Fastest mirror: http://www.mirrorservice.org/sites/www.sagemath.org/ http:

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

2018-03-10 Thread tscrim
> Built without any problem. However, I am no longer able to run doctests on > my system (Ubuntu 17.04) with 8.2.beta8: > > Actually, this seems to be an issue with system as I get a similar error with an older version of Sage. I will instead most the post to sage-devel. Sorry for the noise

[sage-release] Re: Sage 8.1.rc4 released

2017-12-02 Thread tscrim
What about https://trac.sagemath.org/ticket/24297? I don't know if this problem materializes on other platforms, but I know Erik will be happy with all tests passing on Cygwin. ;) Best, Travis PS - I saw that https://trac.sagemath.org/ticket/24085 was not closed. On Saturday, December 2,

[sage-release] Re: Sage 8.1.beta2 released

2017-08-21 Thread tscrim
Hey Simon, Sorry for my delay, I was on a transpacific flight and recovering from that. > > On 2017-08-17, tsc...@ucdavis.edu > wrote: > >> What kind of polynomials is involved in that test? libsingular? > > > > I believe they are the generic polynomials: > > > >

[sage-release] Re: Sage 8.1.beta2 released

2017-08-17 Thread tscrim
Addendum: _.__mro__ (, , , , , , , ... -- 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+unsubscr...@googlegroups.com. To post to this group,

[sage-release] Re: Sage 8.1.beta2 released

2017-08-17 Thread tscrim
Hey Simon, > > On 2017-08-17, tsc...@ucdavis.edu > wrote: > > about half of the time is in > > > > {method 'map_coefficients' of > > 'sage.rings.polynomial.polynomial_element.Polynomial' objects} > > > > and subfunction calls. I would say a better solution would

[sage-release] Re: Sage 8.1.beta2 released

2017-08-16 Thread tscrim
> > > Indeed. > > sage -t --long --warn-long 75.4 src/sage/rings/function_field/ > function_field.py > ** > File "src/sage/rings/function_field/function_field.py", line 69, in sage. > rings.function_field.function_field >

Re: [sage-release] Re: Sage 8.0.beta10 released

2017-06-11 Thread tscrim
> Given what I see, you only get this when you set SAGE_TUNE_GF2X=full. > Unsetting SAGE_TUNE_GF2X (which is the default) or putting it to no > will work. At least it looks to me like SAGE_TUNE_GF2X is set to full > from the log, let me know if this assumption is wrong. > > I didn't set

Re: [sage-release] Re: Sage 8.0.beta10 released

2017-06-11 Thread tscrim
> > t seems that this happens on several machines: > > > > Error installing package gf2x-1.1.p2 > > > > See for example > > > > > https://patchbot.sagemath.org/log/0/LinuxMint/18.1/x86_64/4.4.0-59-generic/rk02-math/2017-06-11%2018:40:38?short > >

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

2017-05-22 Thread tscrim
I was able to build on Cygwin64 with the blockers (and the ECM fix). However, sirocco (libsirocco-2.0.tar.gz) could not be found on the mirrors. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and

[sage-release] Re: Sage 8.0.beta6 released

2017-05-13 Thread tscrim
I was not able to download the tarbal for normaliz from the mirrors (https://trac.sagemath.org/ticket/22684). Best, Travis -- 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

Re: [sage-release] Sage 8.0.beta3 released

2017-04-26 Thread tscrim
I've been in the process of getting beta3 to build on Cygwin using --with-blas=atlas and Cygwin's GCC 6.3. Here is what I needed to do: - Python3 was not building due to a 3.4.5-struct.patch in #22666. Erik sent me an revised patch for this. - Pynac was not building, so I "reverted" 22764 by

Re: [sage-release] Sage 7.4.rc0 released

2016-10-08 Thread tscrim
I think we should fix %attach before the next stable release, and I would also like %lprun fixed too. Best, Travis -- 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