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

[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 
> 10.1.beta7 and ruunning ptestlong gives one new permanent failure :
> -- 
> sage -t --long --warn-long 212.6 
> --random-seed=194612805071128352802316091612762641901 
> src/sage/groups/perm_gps/partn_ref/data_structures.pyx # 1 doctest failed 
> -- 
>
> Running this test standalone gives :
> charpent@zen-book-flip:/usr/local/sage-10$ sage -t --long --warn-long 
> 212.6 --random-seed=194612805071128352802316091612762641901 
> src/sage/groups/perm_gps/partn_ref/data_structures.pyx # 1 doctest failed 
> Running doctests with ID 2023-07-22-11-38-11-b06fd130. Git branch: develop 
> Git ref: 10.1.beta0-1229-g543f8d62b0 Running with 
> SAGE_LOCAL='/usr/local/sage-10/local' and 
> SAGE_VENV='/usr/local/sage-10/local/var/lib/sage/venv-python3.11' Using 
> --optional=debian,dot2tex,fricas,gap_jupyter,gap_packages,libsemigroups,msolve,pip,pysingular,saclib,sage,sage_spkg,singular_jupyter
>  
> Features to be detected: 
> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,cvxopt,cvxopt,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,fpylll,gfan,graphviz,imagemagick,ipython,jupymake,kenzo,latte_int,lrcalc_python,lrslib,mcqd,meataxe,mpmath,msolve,nauty,networkx,numpy,palp,pandoc,pdf2svg,pdftocairo,pexpect,phitigra,pillow,plantri,polytopes_db,polytopes_db_4d,pplpy,primecountpy,ptyprocess,pynormaliz,pyparsing,python_igraph,requests,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.libs.flint,sage.libs.gap,sage.libs.ntl,sage.libs.pari,sage.libs.singular,sage.misc.cython,sage.modular,sage.modules,sage.plot,sage.rings.finite_rings,sage.rings.function_field,sage.rings.number_field,sage.rings.padics,sage.rings.polynomial.pbori,sage.rings.real_double,sage.rings.real_mpfr,sage.schemes,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,scipy,singular,sphinx,sympy,tdlib
>  
> Doctesting 1 file. sage -t --long --warn-long 212.6 
> --random-seed=194612805071128352802316091612762641901 
> src/sage/groups/perm_gps/partn_ref/data_structures.pyx 
> ** File 
> "src/sage/groups/perm_gps/partn_ref/data_structures.pyx", line 1294, in 
> sage.groups.perm_gps.partn_ref.data_structures.SC_test_list_perms Failed 
> example: for n in range(4,8): # long time test_stab_chain_fns_4(n, 1, 1, 1) 
> test_stab_chain_fns_4(n, 2, 1, 1) test_stab_chain_fns_4(n, 2, 1, 1) 
> test_stab_chain_fns_4(n, 3, 1, 1) Exception raised: Traceback (most recent 
> call last): File "/usr/local/sage-10/src/sage/doctest/forker.py", line 696, 
> in _run self.compile_and_execute(example, compiler, test.globs) File 
> "/usr/local/sage-10/src/sage/doctest/forker.py", line 1106, in 
> compile_and_execute exec(compiled, globs) File " sage.groups.perm_gps.partn_ref.data_structures.SC_test_list_perms[24]>", 
> line 5, in  test_stab_chain_fns_4(n, Integer(3), Integer(1), 
> Integer(1)) File " sage.groups.perm_gps.partn_ref.data_structures.SC_test_list_perms[22]>", 
> line 7, in test_stab_chain_fns_4 SC_test_list_perms(perms, n, limit, gap, 
> Integer(0), contains) File 
> "sage/groups/perm_gps/partn_ref/data_structures.pyx", line 1612, in 
> sage.groups.perm_gps.partn_ref.data_structures.SC_test_list_perms raise 
> File "sage/groups/perm_gps/partn_ref/data_structures.pyx", line 1470, in 
> sage.groups.perm_gps.partn_ref.data_structures.SC_test_list_perms raise 
> AssertionError AssertionError 
> ** 1 
> item had failures: 1 of 46 in 
> sage.groups.perm_gps.partn_ref.data_structures.SC_test_list_perms [49 
> tests, 1 failure, 5.00 s] 
> -- sage 
> -t --long --warn-long 212.6 
> --random-seed=194612805071128352802316091612762641901 
> src/sage/groups/perm_gps/partn_ref/data_structures.pyx # 1 doctest failed 
> -- 
> Total time for all tests: 10.1 seconds cpu time: 4.3 seconds cumulative 
> wall time: 5.0 seconds Features detected for doctesting: 
> charpent@zen-book-flip:/usr/local/sage-10$ 
>
> HTH, 
> ​
> Le vendredi 21 juillet 2023 à 21:16:55 UTC+2, Volker Braun a écrit :
>
>> As always, you can get the latest beta version from the "develop" git 
>> branch. Alternatively, the self-contained source tarball is at 
>> http://www.sagemath.org/download-latest.html
>>
>>
>> 543f8d62b08 (tag: 10.1.beta7, github/develop) Updated SageMath version to 
>> 10.1.beta7
>> 98520945e06 

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

[Dave Morris]

Maybe I'm being stupid, but I don't think the given list of generators is 
complete. The inverse of a generator is also a generator, so aren't there 8 
generators, not 4?  (Sorry I couldn't find the PR, to put this comment 
there.)

On Friday, June 16, 2023 at 2:57:38 AM UTC-6 John Cremona wrote:

> I'll review the new PR, though I probably should have seen this problem 
> arising with the original one. 
>
> John
>
> On Fri, 16 Jun 2023 at 09:30, Dima Pasechnik  wrote:
>
>> You can't reopen PRs, I think, you can certainly reopen issues.
>>
>> No need to fill in the longish PR boilerplate, just remove it and write  
>> what it does, mentioning #35626
>>
>>
>>
>> On Fri, 16 Jun 2023, 09:08 chris wuthrich,  
>> wrote:
>>
>>> I replaced old tests with "random" by new ones with "random" (and forgot 
>>> these two). Some other tests do check consistency. 
>>>
>>> All that the function really does is converting a pari output back into 
>>> a point on the elliptic curve. Therefore the test checks if pari runs 
>>> without error and if the returned is a point on the curve. Checking if it 
>>> is a generator modulo torsion would be checking if pari gets this right. Is 
>>> that what we should do?
>>>
>>> But this discussing should happen on a pull request. I repeat my 
>>> question: Do I open a new one or is the faulty initial one reopened? (Trac 
>>> tickets used to be reopened, that is why I ask).
>>>
>>> Chris
>>>
>>> On Friday, 16 June 2023 at 01:39:46 UTC+1 tsc...@ucdavis.edu wrote:
>>>
 I don't think it should be random; that has the chance of hiding actual 
 bugs. I think we should check that it belongs to a particular set 
 (specifically, the one from John's comment).

 Best,
 Travis


 On Thursday, June 15, 2023 at 5:15:52 AM UTC+9 chris wuthrich wrote:

> I agree with John. Lines 2380 and 2388 need a "random output" for that 
> reason, like the other calls of that function have already.
> Is this a new pull request or is the old #35626 
> https://github.com/sagemath/sage/pull/35626 opened again for 
> corrections?
>
> Chris
>
> On Wednesday, 14 June 2023 at 17:49:21 UTC+1 John Cremona wrote:
>
>> On Tue, 13 Jun 2023 at 17:06, John Cremona  
>> wrote:
>>
>>> The elliptic curve failure might be a consequence of the recently 
>>> merged PR #35626 about using libpari to compute ranks and generators.
>>>
>>> I'll take a look to at least see if the output you get is 
>>> mathematically correct -- generators are not unique.
>>>
>>
>> I was right. This curve has rank 1 and torsion (Z/2Z)^2 so if P is 
>> one generator (of infinte order) then there are 3 other, P+T for T a 
>> point 
>> of order 2.  The one your are getting is one of these.
>>
>> So we conclude that we cannot reply on pari always returning the same 
>> generator despite random seeds etc being fixed in doctests.  I don't 
>> know 
>> why that is, but if it is the case then this (and other similar) 
>> doctests 
>> will have to be written accordingly.
>>  
>>
>>>
>>> John
>>>
>>>
>>> On Tue, 13 Jun 2023, 17:00 Emmanuel Charpentier, <
>>> emanuel.c...@gmail.com> wrote:
>>>
 On Debian testing running on core i7 + 16 GB RAM, upgrading 
 10.1.beta2 to 10.1.beta3 and rinning ptestlong gives 3 permanent 
 failures :
 -- 
 sage -t --long --warn-long 207.1 
 --random-seed=291812591553963182024849035945523427319 
 src/sage/schemes/elliptic_curves/ell_rational_field.py # 1 doctest 
 failed 
 sage -t --long --warn-long 207.1 
 --random-seed=291812591553963182024849035945523427319 
 src/sage/coding/linear_code.py # 2 doctests failed sage -t --long 
 --warn-long 207.1 
 --random-seed=291812591553963182024849035945523427319 
 src/sage/coding/code_constructions.py # 1 doctest failed 
 -- 

 The last two have been already reported a few times, and seem 
 cosmetic. The first one is new and seemingly *not* cosmetic :
 charpent@zen-book-flip:/usr/local/sage-10$ sage -t --long 
 --warn-long 207.1 
 --random-seed=291812591553963182024849035945523427319 
 src/sage/schemes/elliptic_curves/ell_rational_field.py # 1 doctest 
 failed 
 Running doctests with ID 2023-06-13-17-49-08-8dac2a23. Git branch: 
 develop 
 Git ref: 10.1.beta0-453-g443b7549ad Running with 
 SAGE_LOCAL='/usr/local/sage-10/local' and 
 SAGE_VENV='/usr/local/sage-10/local/var/lib/sage/venv-python3.11' 
 Using 
 --optional=debian,dot2tex,fricas,gap_jupyter,gap_packages,libsemigroups,msolve,pip,pysingular,sage,sage_spkg,singular_jupyter

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

[Dave Morris]

Using "make -j8 build" instead of "make build" seems to have solved the 
problem for me.  (I have 8 cores.)  I was able to build, and "make 
ptestlong" says "All tests passed!".

Thanks for your suggestions and your patience!  

Fyi, I updated the command line tools to 13.2, but that didn't solve the 
problem on its own (although it may have contributed to the solution).  
Answering the other questions, I don't seem to have 
MACOSX_DEPLOYMENT_TARGET or any other similar environment variables set, 
and "xcrun --show-sdk-version" says 11.3, both before and after the 
update.  "pkgutil --pkg-info=com.apple.pkg.CLTools_Executables" used to say 
12.5, but now says 13.2.  (My next step was going to be replacing python, 
as suggested, but I didn't need to so that.)

On Wednesday, January 12, 2022 at 4:23:58 AM UTC-7 Kwankyu Lee wrote:

> On Wednesday, January 12, 2022 at 11:56:52 AM UTC+9 
> dmo...@deductivepress.ca wrote:
>
>> I installed this version of python yesterday, by downloading a MacOS 
>> installer from https://www.python.org/downloads/macos/.  I did this 
>> because my first failed attempt to build 9.5.rc0 was with Python 3.7, and I 
>> thought that having an old python version might be the problem (and I 
>> understand that Python 3.10 is not yet fully supported).  I got the same 
>> error message with the old install of python as with this new one.
>>
>  
> In my case, it helped to remove the python from www.python.org, and only 
> have python 3.9 installed by homebrew. 
>  
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/d8d94b70-1cce-44ed-b88f-3ad8981b5bccn%40googlegroups.com.

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

[Dave Morris]

Thanks for your reply.  The message when I start python says:
Python 3.9.9 (v3.9.9:ccb0e6a345, Nov 15 2021, 13:29:20)
[Clang 6.0 (clang-600.0.57)] on darwin

I installed this version of python yesterday, by downloading a MacOS 
installer from https://www.python.org/downloads/macos/.  I did this because 
my first failed attempt to build 9.5.rc0 was with Python 3.7, and I thought 
that having an old python version might be the problem (and I understand 
that Python 3.10 is not yet fully supported).  I got the same error message 
with the old install of python as with this new one.
On Tuesday, January 11, 2022 at 6:32:20 PM UTC-7 matthia...@gmail.com wrote:

> The python3 used in this build is 
> /Library/Frameworks/Python.framework/Versions/3.9/bin/python3 
> -- could you check which version this is and do you recall how you 
> installed it?
>
>
> On Tuesday, January 11, 2022 at 4:19:41 PM UTC-8 dmo...@deductivepress.ca 
> wrote:
>
>> I failed to build 9.5rc0 on MacOS 11.5.2 after "make distclean", because 
>> I got "ERROR: pplpy-0.8.6-cp39-cp39-macosx_11_0_x86_64.whl is not a 
>> supported wheel on this platform."  I know nothing about build systems, so 
>> I wouldn't be surprised if I'm doing something stupid, but I did know to do 
>> "source .homebrew-build-env" and ".bootstrap" before "./configure" and 
>> "make build", and I was able to build 9.5b9 again after this failure, so it 
>> seems to me that some commit is causing a problem for me.   I posted 
>> config.log  and 
>> pplpy-0.8.6.log 
>>  on the 
>> internet.
>>
>> Suggestions or a diagnosis are welcome.  (Perhaps I should learn how to 
>> use conda?)
>>
>> Best,
>> Dave
>>
>> On Tuesday, January 11, 2022 at 1:08:35 PM UTC-7 Sébastien Labbé wrote:
>>
>>> Dear Volker,
>>>
>>> I would also like to ask whether it is possible to include
>>> https://trac.sagemath.org/ticket/20343
>>> in the next rc? It got a positive review last Thursday. It adds a new 
>>> module sage/plot/tikzpicture.py to deal with tikzpicture, show them 
>>> automatically in a Jupyter cell and export them to various format (pdf, 
>>> png, svg), etc. The module was in preparation in my personnal package since 
>>> 6 years. It is now mature enough to go into Sage. I know few people who 
>>> install my package only for that module. I think it will be a nice new 
>>> feature for 9.5.
>>>
>>> Note: it can go with or without the dependency 
>>> https://trac.sagemath.org/ticket/33005
>>>
>>> Sincerely,
>>>
>>> Sébastien
>>>
>>>
>>>
>>>
>>> On Monday, January 10, 2022 at 5:27:11 PM UTC+1 egourg...@gmail.com 
>>> wrote:
>>>
 Hi Volker,

 Thank you for this release. 
 Would it be possible to include 
 https://trac.sagemath.org/ticket/30362 
 in the next rc if any? This ticket has been in positive review state 
 for 17 days; it introduces symplectic structures on manifolds and it would 
 be nice if Sage 9.5 is shipped with them. Thank you. 

 Eric.



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/948a5e06-c2aa-41f8-b533-755a82bc0e41n%40googlegroups.com.

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

[Dave Morris]

I failed to build 9.5rc0 on MacOS 11.5.2 after "make distclean", because I 
got "ERROR: pplpy-0.8.6-cp39-cp39-macosx_11_0_x86_64.whl is not a supported 
wheel on this platform."  I know nothing about build systems, so I wouldn't 
be surprised if I'm doing something stupid, but I did know to do "source 
.homebrew-build-env" and ".bootstrap" before "./configure" and "make 
build", and I was able to build 9.5b9 again after this failure, so it seems 
to me that some commit is causing a problem for me.   I posted config.log 
 and pplpy-0.8.6.log 
 on the internet.

Suggestions or a diagnosis are welcome.  (Perhaps I should learn how to use 
conda?)

Best,
Dave

On Tuesday, January 11, 2022 at 1:08:35 PM UTC-7 Sébastien Labbé wrote:

> Dear Volker,
>
> I would also like to ask whether it is possible to include
> https://trac.sagemath.org/ticket/20343
> in the next rc? It got a positive review last Thursday. It adds a new 
> module sage/plot/tikzpicture.py to deal with tikzpicture, show them 
> automatically in a Jupyter cell and export them to various format (pdf, 
> png, svg), etc. The module was in preparation in my personnal package since 
> 6 years. It is now mature enough to go into Sage. I know few people who 
> install my package only for that module. I think it will be a nice new 
> feature for 9.5.
>
> Note: it can go with or without the dependency 
> https://trac.sagemath.org/ticket/33005
>
> Sincerely,
>
> Sébastien
>
>
>
>
> On Monday, January 10, 2022 at 5:27:11 PM UTC+1 egourg...@gmail.com wrote:
>
>> Hi Volker,
>>
>> Thank you for this release. 
>> Would it be possible to include 
>> https://trac.sagemath.org/ticket/30362 
>> in the next rc if any? This ticket has been in positive review state for 
>> 17 days; it introduces symplectic structures on manifolds and it would be 
>> nice if Sage 9.5 is shipped with them. Thank you. 
>>
>> Eric.
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/cef6a584-f501-4684-839c-57d6690929e0n%40googlegroups.com.