Re: [sage-release] Re: Sage 8.5.beta5 released

2018-12-20 Thread Sébastien Labbé


On Wednesday, November 28, 2018 at 9:49:53 AM UTC+1, François Bissey wrote:
>
> That’s interesting. I thought the failures in sage/databases/sql_db.py in 
> sage-on-gentoo 
> were due to the use of a newer version of sqlite. But if you see it too 
> that must be something 
> more subtle. 
>
>
I just created
https://trac.sagemath.org/ticket/26920 
for the issue with sql_db.py since it is still a problem with 8.5.rc0.

-- 
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, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 8.5.beta5 released

2018-11-28 Thread François Bissey
This is definitely it. It introduced the doctests in question. I guess
I should have provided that extra info.


> On 28/11/2018, at 22:11, fchapot...@gmail.com wrote:
> 
> Could be caused by https://trac.sagemath.org/ticket/26702
> 
> Le mercredi 28 novembre 2018 09:49:53 UTC+1, François Bissey a écrit :
> That’s interesting. I thought the failures in sage/databases/sql_db.py in 
> sage-on-gentoo 
> were due to the use of a newer version of sqlite. But if you see it too that 
> must be something 
> more subtle. 
> 
> François 
> 
> > On 28/11/2018, at 21:46, Sébastien Labbé  wrote: 
> > 
> > On Ubuntu 16.04, the command 
> > 
> > sage -t --all --optional=sage,optional,external 
> > 
> > tests the following optional and external doctests: 
> > 
> > Using 
> > --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage
> >  
> > External software detected for doctesting: 
> > ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc 
> > 
> > 
> > and gives All tests passed except the following ones: 
> > 
> > -- 
> > sage -t --long src/sage/databases/findstat.py  # 5 doctests failed 
> > sage -t --long src/sage/symbolic/integration/integral.py  # 1 doctest 
> > failed 
> > sage -t --long src/sage/combinat/tutorial.py  # 1 doctest failed 
> > sage -t --long src/sage/symbolic/integration/external.py  # 3 doctests 
> > failed 
> > sage -t --long src/sage/combinat/designs/ext_rep.py  # 1 doctest failed 
> > sage -t --long src/sage/repl/load.py  # 1 doctest failed 
> > sage -t --long src/sage/misc/persist.pyx  # 2 doctests failed 
> > sage -t --long src/sage/databases/sql_db.py  # 2 doctests failed 
> > -- 
> > 
> > 
> > Follow up at https://trac.sagemath.org/ticket/25536. New failures are 
> > copied below. 
> > 
> > 
> > 
> > sage -t --long src/sage/combinat/tutorial.py 
> > ** 
> > File "src/sage/combinat/tutorial.py", line 224, in sage.combinat.tutorial 
> > Failed example: 
> > oeis([1,1,2,5,14])# optional -- internet 
> > Expected: 
> > 0: A000108: Catalan numbers: C(n) = binomial(2n,n)/(n+1) = 
> > (2n)!/(n!(n+1)!). Also called Segner numbers. 
> > 1: A120588: G.f. satisfies: 3*A(x) = 2 + x + A(x)^2, with a(0) = 1. 
> > 2: ... 
> > Got: 
> > 0: A000108: Catalan numbers: C(n) = binomial(2n,n)/(n+1) = 
> > (2n)!/(n!(n+1)!). Also called Segner numbers. 
> > 1: A124302: Number of set partitions with at most 3 blocks; number of 
> > Dyck paths of height at most 4; dimension of space of symmetric polynomials 
> > in 3 noncommuting variables. 
> > 2: A120588: G.f. satisfies: 3*A(x) = 2 + x + A(x)^2, with a(0) = 1. 
> > ** 
> > 1 item had failures: 
> >1 of 249 in sage.combinat.tutorial 
> > 5 tests for not implemented functionality not run 
> > 6 not tested tests not run 
> > 0 tests not run because we ran out of time 
> > [248 tests, 1 failure, 24.70 s] 
> > 
> > 
> > sage -t --long src/sage/databases/sql_db.py 
> > ** 
> > File "src/sage/databases/sql_db.py", line 956, in 
> > sage.databases.sql_db.SQLDatabase.__init__ 
> > Failed example: 
> > D.show('simon') 
> > Expected: 
> > graph6   vertices edges 
> >  
> > ?00 
> > @10 
> > A?   20 
> > A_   21 
> > B?   30 
> > BG   31 
> > BW   32 
> > Bw   33 
> > C?   40 
> > C@   41 
> > CB   42 
> > CF   43 
> > CJ   43 
> > CK   42 
> > CL   43 
> > CN   44 
> > C]   44 
> > C^   45 
> > C~   46 
> > Got: 
> > graph6   vertices edges   
> >  
> > ?00   
> > @10   
> > A?   

Re: [sage-release] Re: Sage 8.5.beta5 released

2018-11-28 Thread fchapoton2
Could be caused by https://trac.sagemath.org/ticket/26702

Le mercredi 28 novembre 2018 09:49:53 UTC+1, François Bissey a écrit :
>
> That’s interesting. I thought the failures in sage/databases/sql_db.py in 
> sage-on-gentoo 
> were due to the use of a newer version of sqlite. But if you see it too 
> that must be something 
> more subtle. 
>
> François 
>
> > On 28/11/2018, at 21:46, Sébastien Labbé > 
> wrote: 
> > 
> > On Ubuntu 16.04, the command 
> > 
> > sage -t --all --optional=sage,optional,external 
> > 
> > tests the following optional and external doctests: 
> > 
> > Using 
> --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage
>  
>
> > External software detected for doctesting: 
> ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc 
> > 
> > 
> > and gives All tests passed except the following ones: 
> > 
> > -- 
> > sage -t --long src/sage/databases/findstat.py  # 5 doctests failed 
> > sage -t --long src/sage/symbolic/integration/integral.py  # 1 doctest 
> failed 
> > sage -t --long src/sage/combinat/tutorial.py  # 1 doctest failed 
> > sage -t --long src/sage/symbolic/integration/external.py  # 3 doctests 
> failed 
> > sage -t --long src/sage/combinat/designs/ext_rep.py  # 1 doctest failed 
> > sage -t --long src/sage/repl/load.py  # 1 doctest failed 
> > sage -t --long src/sage/misc/persist.pyx  # 2 doctests failed 
> > sage -t --long src/sage/databases/sql_db.py  # 2 doctests failed 
> > -- 
> > 
> > 
> > Follow up at https://trac.sagemath.org/ticket/25536. New failures are 
> copied below. 
> > 
> > 
> > 
> > sage -t --long src/sage/combinat/tutorial.py 
> > ** 
> > File "src/sage/combinat/tutorial.py", line 224, in 
> sage.combinat.tutorial 
> > Failed example: 
> > oeis([1,1,2,5,14])# optional -- internet 
> > Expected: 
> > 0: A000108: Catalan numbers: C(n) = binomial(2n,n)/(n+1) = 
> (2n)!/(n!(n+1)!). Also called Segner numbers. 
> > 1: A120588: G.f. satisfies: 3*A(x) = 2 + x + A(x)^2, with a(0) = 1. 
> > 2: ... 
> > Got: 
> > 0: A000108: Catalan numbers: C(n) = binomial(2n,n)/(n+1) = 
> (2n)!/(n!(n+1)!). Also called Segner numbers. 
> > 1: A124302: Number of set partitions with at most 3 blocks; number 
> of Dyck paths of height at most 4; dimension of space of symmetric 
> polynomials in 3 noncommuting variables. 
> > 2: A120588: G.f. satisfies: 3*A(x) = 2 + x + A(x)^2, with a(0) = 1. 
> > ** 
> > 1 item had failures: 
> >1 of 249 in sage.combinat.tutorial 
> > 5 tests for not implemented functionality not run 
> > 6 not tested tests not run 
> > 0 tests not run because we ran out of time 
> > [248 tests, 1 failure, 24.70 s] 
> > 
> > 
> > sage -t --long src/sage/databases/sql_db.py 
> > ** 
> > File "src/sage/databases/sql_db.py", line 956, in 
> sage.databases.sql_db.SQLDatabase.__init__ 
> > Failed example: 
> > D.show('simon') 
> > Expected: 
> > graph6   vertices edges 
> >  
> > ?00 
> > @10 
> > A?   20 
> > A_   21 
> > B?   30 
> > BG   31 
> > BW   32 
> > Bw   33 
> > C?   40 
> > C@   41 
> > CB   42 
> > CF   43 
> > CJ   43 
> > CK   42 
> > CL   43 
> > CN   44 
> > C]   44 
> > C^   45 
> > C~   46 
> > Got: 
> > graph6   vertices edges   
> >  
> > ?00   
> > @10   
> > A?   20   
> > A_   21   
> > B?   30   
> >   

Re: [sage-release] Re: Sage 8.5.beta5 released

2018-11-28 Thread François Bissey
That’s interesting. I thought the failures in sage/databases/sql_db.py in 
sage-on-gentoo
were due to the use of a newer version of sqlite. But if you see it too that 
must be something
more subtle.

François

> On 28/11/2018, at 21:46, Sébastien Labbé  wrote:
> 
> On Ubuntu 16.04, the command 
> 
> sage -t --all --optional=sage,optional,external
> 
> tests the following optional and external doctests:
> 
> Using 
> --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage
> External software detected for doctesting: 
> ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc
> 
> 
> and gives All tests passed except the following ones:
> 
> --
> sage -t --long src/sage/databases/findstat.py  # 5 doctests failed
> sage -t --long src/sage/symbolic/integration/integral.py  # 1 doctest failed
> sage -t --long src/sage/combinat/tutorial.py  # 1 doctest failed
> sage -t --long src/sage/symbolic/integration/external.py  # 3 doctests failed
> sage -t --long src/sage/combinat/designs/ext_rep.py  # 1 doctest failed
> sage -t --long src/sage/repl/load.py  # 1 doctest failed
> sage -t --long src/sage/misc/persist.pyx  # 2 doctests failed
> sage -t --long src/sage/databases/sql_db.py  # 2 doctests failed
> --
> 
> 
> Follow up at https://trac.sagemath.org/ticket/25536. New failures are copied 
> below.
> 
> 
> 
> sage -t --long src/sage/combinat/tutorial.py
> **
> File "src/sage/combinat/tutorial.py", line 224, in sage.combinat.tutorial
> Failed example:
> oeis([1,1,2,5,14])# optional -- internet
> Expected:
> 0: A000108: Catalan numbers: C(n) = binomial(2n,n)/(n+1) = 
> (2n)!/(n!(n+1)!). Also called Segner numbers.
> 1: A120588: G.f. satisfies: 3*A(x) = 2 + x + A(x)^2, with a(0) = 1.
> 2: ...
> Got:
> 0: A000108: Catalan numbers: C(n) = binomial(2n,n)/(n+1) = 
> (2n)!/(n!(n+1)!). Also called Segner numbers.
> 1: A124302: Number of set partitions with at most 3 blocks; number of 
> Dyck paths of height at most 4; dimension of space of symmetric polynomials 
> in 3 noncommuting variables.
> 2: A120588: G.f. satisfies: 3*A(x) = 2 + x + A(x)^2, with a(0) = 1.
> **
> 1 item had failures:
>1 of 249 in sage.combinat.tutorial
> 5 tests for not implemented functionality not run
> 6 not tested tests not run
> 0 tests not run because we ran out of time
> [248 tests, 1 failure, 24.70 s]
> 
> 
> sage -t --long src/sage/databases/sql_db.py
> **
> File "src/sage/databases/sql_db.py", line 956, in 
> sage.databases.sql_db.SQLDatabase.__init__
> Failed example:
> D.show('simon')
> Expected:
> graph6   vertices edges
> 
> ?00
> @10
> A?   20
> A_   21
> B?   30
> BG   31
> BW   32
> Bw   33
> C?   40
> C@   41
> CB   42
> CF   43
> CJ   43
> CK   42
> CL   43
> CN   44
> C]   44
> C^   45
> C~   46
> Got:
> graph6   vertices edges   
> 
> ?00   
> @10   
> A?   20   
> A_   21   
> B?   30   
> BG   31   
> BW   32   
> Bw   33   
> C?   40   
> C@   41   
> CB   42   

Re: [sage-release] Re: Sage 8.5.beta5 released

2018-11-26 Thread E. Madison Bray
On Mon, Nov 26, 2018 at 5:37 AM Steven Trogdon  wrote:
>
> On my Gentoo changing the ownership was not sufficient. After changing the 
> ownership I had to
>
> git reset --hard HEAD
>
> which revealed that
>
> Updating f894105d0d..b36eca1990
> error: The following untracked working tree files would be overwritten by 
> merge:
>
> To correct this:
>
> git clean -f build/pkgs/barvinok/
> git clean -f build/pkgs/isl/
> git clean -f build/pkgs/lcalc/patches/
> git clean -f build/pkgs/polylib/
>
> and now 'git pull' is up to date. This is all very strange.

At some point you probably did *something* as root (and by "you" it
might not have even been an action you personally took, but maybe some
cron job you forgot about; who knows).  But otherwise I don't think
there's any way that would have happened.  This happens to me too
sometimes ¯\_(ツ)_/¯  Git repos don't store anything about uid/gid of
files (that would be disastrous); in fact IIRC the only information it
stores about file permissions is whether or not the executable bit
should be set.


> On Sunday, November 25, 2018 at 9:41:58 PM UTC-6, Samuel Lelievre wrote:
>>
>> > As far as I can recall 'git pull' was always done as a normal user.
>> > Note the timestamp on the folders, which predates 8.5.beta4.
>> > And this issue did not manifest itself then. But going forward,
>> > how to correct things?
>>
>> Change to your SAGE_ROOT directory and run this as a normal user
>>
>> $ sudo chown -v -R $(id -u):$(id -g) .
>>
>> to set the owner and group of SAGE_ROOT (and recursively all
>> the included files and directories) to your user and your group.
>
> --
> 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, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 8.5.beta5 released

2018-11-25 Thread Steven Trogdon
On my Gentoo changing the ownership was not sufficient. After changing the 
ownership I had to

git reset --hard HEAD

which revealed that

Updating f894105d0d..b36eca1990
error: The following untracked working tree files would be overwritten by 
merge:

To correct this:

git clean -f build/pkgs/barvinok/
git clean -f build/pkgs/isl/
git clean -f build/pkgs/lcalc/patches/
git clean -f build/pkgs/polylib/

and now 'git pull' is up to date. This is all very strange.

On Sunday, November 25, 2018 at 9:41:58 PM UTC-6, Samuel Lelievre wrote:
>
> > As far as I can recall 'git pull' was always done as a normal user. 
> > Note the timestamp on the folders, which predates 8.5.beta4. 
> > And this issue did not manifest itself then. But going forward, 
> > how to correct things? 
>
> Change to your SAGE_ROOT directory and run this as a normal user 
>
> $ sudo chown -v -R $(id -u):$(id -g) . 
>
> to set the owner and group of SAGE_ROOT (and recursively all 
> the included files and directories) to your user and your group. 
>

-- 
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, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 8.5.beta5 released

2018-11-25 Thread Samuel Lelièvre
> As far as I can recall 'git pull' was always done as a normal user.
> Note the timestamp on the folders, which predates 8.5.beta4.
> And this issue did not manifest itself then. But going forward,
> how to correct things?

Change to your SAGE_ROOT directory and run this as a normal user

$ sudo chown -v -R $(id -u):$(id -g) .

to set the owner and group of SAGE_ROOT (and recursively all
the included files and directories) to your user and your group.

-- 
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, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.