Re: [sage-release] Sage 9.2.beta9 released

2020-08-19 Thread Maxime Bombar
Hi,

On a fresh install from sources on Debian Sid build and documentation
are ok, but tests sometimes fail :

make: *** [Makefile:190: ptestlong] Error 17

-- 
MB.



-- 
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/10a9e3e4-0c5f-6740-a891-3461994dd956%40inria.fr.


signature.asc
Description: OpenPGP digital signature


Re: [sage-release] Sage 9.2.beta9 released

2020-08-20 Thread Maxime Bombar
On 8/20/20 11:58 AM, Dima Pasechnik wrote:
> On Wed, Aug 19, 2020 at 2:57 PM Maxime Bombar  wrote:
>> Hi,
>>
>> On a fresh install from sources on Debian Sid build and documentation
>> are ok, but tests sometimes fail :
>>
>> make: *** [Makefile:190: ptestlong] Error 17
> More details please - which tests have  failed?
> (normally there should be a summary report at the end of testing session)
>
> Thanks
> Dima
>> --
>> MB.
>>
>>
>>
>> --
>> 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/10a9e3e4-0c5f-6740-a891-3461994dd956%40inria.fr.

Oh yes sure, sorry I didn't see it. It that the following ?

 sage -t --long --random-seed=0
src/doc/en/constructions/algebraic_geometry.rst  # 1 doctest failed
 sage -t --long --random-seed=0 src/doc/en/reference/sat/index.rst  #
Killed due to segmentation fault
 sage -t --long --random-seed=0 src/sage/crypto/mq/sr.py  # Killed due
to abort
 sage -t --long --random-seed=0 src/sage/modules/fg_pid/fgp_module.py  #
3 doctests failed
 sage -t --long --random-seed=0
src/sage/modules/free_module_morphism.py  # 3 doctests failed
 sage -t --long --random-seed=0 src/sage/rings/complex_arb.pyx  # 6
doctests failed
 sage -t --long --random-seed=0 src/sage/rings/polynomial/pbori.pyx  #
Killed due to abort
 sage -t --long --random-seed=0
src/sage/rings/polynomial/multi_polynomial_sequence.py  # Killed due to
abort
 sage -t --long --random-seed=0 src/sage/rings/real_arb.pyx  # 2
doctests failed
 sage -t --long --random-seed=0
src/sage/rings/polynomial/polynomial_ring_constructor.py  # Killed due
to abort
 sage -t --long --random-seed=0 src/sage/sat/boolean_polynomials.py  #
Killed due to abort
 sage -t --long --random-seed=0 src/sage/sat/solvers/dimacs.py  # Killed
due to abort
 sage -t --long --random-seed=0
src/sage/schemes/hyperelliptic_curves/monsky_washnitzer.py  # Killed due
to abort

I can be more specific by digging into the log file, for instance :

File "src/doc/en/constructions/algebraic_geometry.rst", line 145, in
doc.en.constructions.algebraic_geometry
Failed example:
    print(L)
Expected:
    [1]:
   _[1]=y   
   _[2]=x   
    ...
Got:
    [1]:
   _[1]=y^2+y+1
   _[2]=x+1
    [2]:
   _[1]=y^2+y+1
   _[2]=x+y+1
    [3]:
   _[1]=y^2+y+1
   _[2]=x+y
    [4]:
   _[1]=y^2+y+1
   _[2]=x
    [5]:
   _[1]=y+1
   _[2]=x^2+x+1
    [6]:
   _[1]=y+1
   _[2]=x+1
    [7]:
   _[1]=y+1
   _[2]=x
    [8]:
   _[1]=y
   _[2]=x^2+x+1
    [9]:
   _[1]=y
   _[2]=x+1
    [10]:
   _[1]=y
   _[2]=x


Best,

-- 
MB.


-- 
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/4884af9a-7f02-a9a7-534a-338ecfe76700%40inria.fr.


Re: [sage-release] Sage 9.2.beta9 released

2020-08-20 Thread Maxime Bombar
On 8/20/20 4:24 PM, Dima Pasechnik wrote:
> It would be good to know which of these still fail if you run them
> separately.

I have exactly the same result by running them separately.

I tried running those tests with sage9.1, and both
`src/sage/rings/real_arb.pyx` and `src/sage/rings/complex_arb.pyx`
failed with the same error as 9.2.beta9 but the other tests passed.

How can I be more helpful ?

Best,

-- 
Maxime Bombar

-- 
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/a03d7375-1e2b-6ed9-681d-eae0fb4dfba8%40inria.fr.


Re: [sage-release] Sage 9.2.beta9 released

2020-08-24 Thread Maxime Bombar
On 8/20/20 5:05 PM, Dima Pasechnik wrote:
> segfaults and aborts you get from tests are kind of worrying. Could it
> be that you have "rogue" libraries in /usr/local, which get picked up
> instead of system ones?
>
> Perhaps, post the main config.log
>
Hi,

I upgraded to beta10, and every segfault is now gone. I bet it was an
edge case of forbidding a recent version of some compiler like gcc.
There is only one abortion left
(src/sage/schemes/hyperelliptic_curves/monsky_washnitzer.py
), but it seems to be documented here
https://trac.sagemath.org/ticket/29719#comment:17, because on debian
unstable libflint-dev depends on libflint-2.6.3, and libflint-dev was
recommended in the installation guide for later version than debian buster.

It could be a good idea to ensure flint version to be less than 2.6.3,
as it was done for gcc and gfortran before beta10. How do you think ?
Should I open a ticket ?

I uninstalled this lib from my system, and the test now passes.

I will continue to look at the other failures.

Best,

-- 
MB.


-- 
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/8d47374c-967d-b16e-c203-4e8213c6e3d6%40inria.fr.


Re: [sage-release] Final 9.6 upgrade is catastrophic on Debian testing

2022-05-17 Thread Maxime Bombar

On 5/16/22 23:56, Emmanuel Charpentier wrote:


After perusing the failures log and some wild guesses, problem worked 
around by |./configure --with-system-python=no|.


Does this problem deserve reporting to Debian (/i. e./ filing a ticket 
against Debian|python3| package) ?


I just tried on Debian unstable, with the same Python version as in 
Debian testing, and I didn't get any error at all (all tests passed) 
either with Sage's own Python (3.10.3), or with Debian' s version (3.10.4).


Maybe it is something fixed between testing and unstable, or there is 
another issue, but in any case I don't think this problem deserves 
reporting to Debian.


--
Maxime

--
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/5cfc8a87-ce7f-2db6-d5ba-973b227ad86e%40inria.fr.


OpenPGP_signature
Description: OpenPGP digital signature