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

2020-08-20 Thread Steven Trogdon 
I've seen the following failures when doctesting Sage-on-Gentoo but I'm now 
seeing them when doctesting vanilla Sage:

sage -t --long --warn-long 165.2 --random-seed=0 src/sage/rings/integer.pyx
**
File "src/sage/rings/integer.pyx", line 3100, in 
sage.rings.integer.Integer.divisors
Failed example:
for i in range(20):  # long time
try:
alarm(RDF.random_element(1e-3, 0.5))
_ = n.divisors()
cancel_alarm()  # we never get here
except AlarmInterrupt:
pass
Exception raised:
Traceback (most recent call last):
  File 
"/local/sage-git/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 715, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/local/sage-git/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 1139, in compile_and_execute
exec(compiled, globs)
  File "", line 4, in 

_ = n.divisors()
  File "sage/rings/integer.pyx", line 3170, in 
sage.rings.integer.Integer.divisors 
(build/cythonized/sage/rings/integer.c:20840)
ptr = check_allocarray(divisor_count, 3 * 
sizeof(unsigned long))
  File "memory.pxd", line 87, in cysignals.memory.check_allocarray 
(build/cythonized/sage/rings/integer.c:47465)
MemoryError: failed to allocate 33554432 * 24 bytes
**
File "src/sage/rings/integer.pyx", line 3912, in 
sage.rings.integer.Integer.?
Failed example:
n.factor(proof=True)
Exception raised:
Traceback (most recent call last):
  File 
"/local/sage-git/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 715, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/local/sage-git/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 1139, in compile_and_execute
exec(compiled, globs)
  File "", line 1, in 
n.factor(proof=True)
  File "sage/rings/integer.pyx", line 3994, in 
sage.rings.integer.Integer.factor 
(build/cythonized/sage/rings/integer.c:25893)
F = factor_using_pari(n, int_=int_, debug_level=verbose, 
proof=proof)
  File "sage/rings/factorint.pyx", line 345, in 
sage.rings.factorint.factor_using_pari 
(build/cythonized/sage/rings/factorint.c:6481)
p, e = n.__pari__().factor(proof=proof)
  File "cypari2/gen.pyx", line 4311, in cypari2.gen.Gen.factor
cysignals.signals.AlarmInterrupt
**

and

sage -t --long --warn-long 165.2 --random-seed=0 src/sage/doctest/test.py
**
File "src/sage/doctest/test.py", line 521, in sage.doctest.test
Failed example:
if system() == "Linux":
P = subprocess.Popen(["sage", "-t", "--warn-long", "0", 
"--random-seed=0", "--memlimit=2000", "memlimit.rst"], 
stdout=subprocess.PIPE, **kwds)
out, err = P.communicate()
ok = ("MemoryError: failed to allocate" in bytes_to_str(out))
Expected nothing
Got:
Process DocTestWorker-1:
Traceback (most recent call last):
  File 
"/local/sage-git/sage/local/lib/python3.7/multiprocessing/process.py", line 
297, in _bootstrap
self.run()
  File 
"/local/sage-git/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 2185, in run
task(self.options, self.outtmpfile, msgpipe, self.result_queue)
  File 
"/local/sage-git/sage/local/lib/python3.7/site-packages/sage/doctest/forker.py",
 
line 2535, in __call__
result_queue.put(result, False)
  File 
"/local/sage-git/sage/local/lib/python3.7/multiprocessing/queues.py", line 
87, in put
self._start_thread()
  File 
"/local/sage-git/sage/local/lib/python3.7/multiprocessing/queues.py", line 
170, in _start_thread
self._thread.start()
  File "/local/sage-git/sage/local/lib/python3.7/threading.py", line 
847, in start
_start_new_thread(self._bootstrap, ())
RuntimeError: can't start new thread


On Tuesday, August 18, 2020 at 5:01:42 PM UTC-6, Volker Braun wrote:
>
> 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 
>
>
> 548666e9f2 (tag: 9.2.beta9, trac/develop) Updated SageMath version to 
> 9.2.beta9
> 842a6866f1 Trac #29974: Make combinat doctests ready for random seeds
> 1de1d457b4 Trac #29971: Make categories doctests ready for random seeds
> 6864757e11 Trac #29968: Make algebras doctests ready for random seeds
> b526019731 Trac #29963: Make geometry doctests ready for random seeds
> 719f9af12c Trac #29509: rational_points fails for some hyperelliptic curves
> 4d5ab773b5 Trac #29257: use solve_left for division operation of matrices
> e18e84219d Trac #30365: Disable LTO in matplotl

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

2020-08-20 Thread Dima Pasechnik 


On Wednesday, August 19, 2020 at 3:04:18 PM UTC+1 erik@gmail.com wrote:

> On Friday, August 14, 2020 at 1:44:38 PM UTC+2 david@gmail.com wrote:
>
>> Same here on a fresh clone with macOS 10.15.16
>>
>>
>> [dochtml] Building en/constructions.
>> [dochtml] 
>> [dochtml] [construct] building [html]: targets for 16 source files that 
>> are out of date
>> [dochtml] [construct] updating environment: [new config] 16 added, 0 
>> changed, 0 removed
>> ^C[dochtml] Error building the documentation.
>> [dochtml] Traceback (most recent call last):
>> [dochtml]   File 
>> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py",
>>  
>> line 193, in _run_module_as_main
>> [dochtml] "__main__", mod_spec)
>> [dochtml]   File 
>> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py",
>>  
>> line 85, in _run_code
>> [dochtml] exec(code, run_globals)
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__main__.py",
>>  
>> line 2, in 
>> [dochtml] main()
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>>  
>> line 1721, in main
>> [dochtml] builder()
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>>  
>> line 337, in _wrapper
>> [dochtml] build_many(build_other_doc, L)
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>>  
>> line 281, in build_many
>> [dochtml] _build_many(target, args, processes=NUM_THREADS)
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/utils.py",
>>  
>> line 263, in build_many
>> [dochtml] waited_pid, waited_exitcode = wait_for_one()
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/utils.py",
>>  
>> line 179, in wait_for_one
>> [dochtml] pid, sts = os.wait()
>> [dochtml]   File "src/cysignals/signals.pyx", line 320, in 
>> cysignals.signals.python_check_interrupt
>> [dochtml] KeyboardInterrupt
>> [dochtml] 
>> [dochtml] Note: incremental documentation builds sometimes cause 
>> spurious
>> [dochtml] error messages. To be certain that these are real errors, 
>> run
>> [dochtml] "make doc-clean" first and try again.
>> make[3]: *** [doc-html] Error 1
>> make[2]: *** [all-start] Interrupt: 2
>> make[1]: *** [all-start] Interrupt: 2
>> make: *** [all] Interrupt: 2
>>
>>
>>
> As I noted at [1], this implies that one or more of the docbuilds are 
> running some code that hangs forever, so it would help narrow it down by 
> finding out what code it's running to cause a hang.  Normally in docbuilds 
> the most likely code to run will be some plotting code, so you can try to 
> take the plot code present in the relevant documentation pages, run it, and 
> see if it hangs.  Chances are if you run it in a single process it might 
> *not* hang--frequently this happens only in a forked subprocess.  So you 
> can try something like:
>
> from multiprocessing import Process
> p = Process(target=)
> p.start()
>
> and see if it hangs. I've often found this to be the case with calls to 
> np.dot(), which matpotlib uses sometimes to perform various 
> transformations, and which in turn often results in a call to a 
> multi-threaded OpenBLAS function which are sometimes buggy.
>
> As an aside, I would like to make the parallel doc build code more robust 
> to this kind of hang, but it's hard to say exactly what the right solution 
> is (I know more or less what the technical solution is, but I mean more the 
> UX solution).  Because as far as the docbuild code is concerned, it doesn't 
> know that the process is "hung".  It's just taking however long it needs to 
> take, and the code will wait for it to finish.  Perhaps we could implement 
> some kind of timeout to kill docbuild processes that are taking too long 
> (but what should the timeout be)? Or report back to the user exactly which 
> docbuilds are still running (like, a log message at some interval) so that 
> the user can decide whether or not to take action.
>

I found out that the problem is due to OpenMP, see 
https://trac.sagemath.org/ticket/30351#comment: 
50
The workaround (or perhaps the only way to proceed, I don't know) is to set 
env.var. OMP_NUM_THREADS=1

 

>
> [1] https://trac.sagemath.org/ticket/30351#comment:40 
>

-- 
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/017886ad-d707-45d1-ba42-d97422909385n%40googlegroups.com.

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

2020-08-20 Thread 'Justin C. Walker' via sage-release 



> On Aug 18, 2020, at 16:01, Volker Braun  wrote:
> 
> 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 

Built from fresh clones of the 9.2.b8 branch, on two macOS systems: 10.13.6 
(2019 iMac Pro, 18-core Xeon W); and 10.15.6 (2019 MBP, 8-core Core i9).

No problems with either of the builds, and testing (‘ptestlong’) on each 
completed with no failures.

Justin

-- 
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/3BA8C899-4FA8-4E06-9278-5F42BB0AFBA0%40mac.com.

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

2020-08-20 Thread Dima Pasechnik 
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


On Thu, 20 Aug 2020, 16:01 Maxime Bombar,  wrote:

> 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
> .
>

-- 
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/CAAWYfq0PBsUjQxSvOJ4kZBKXS7Y%2BXgsD8o5%3D-42k-1U-QGuY-w%40mail.gmail.com.

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-20 Thread Dima Pasechnik 
It would be good to know which of these still fail if you run them
separately.


On Thu, 20 Aug 2020, 15:19 Maxime Bombar,  wrote:

> 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
> .
>

-- 
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/CAAWYfq3qVtqrpZT7pXaLxrye5ykRrhsgh7ZFBZTjtK5w0muGQg%40mail.gmail.com.

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 Dima Pasechnik 
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.

-- 
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/CAAWYfq0gQVBsbP8JCTYvU_9rcCTAb8kpK7XeW6FH_s8eU_6Qug%40mail.gmail.com.

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

2020-08-20 Thread Kenji Iohara 
It is a fresh build.

> 2020/08/20 9:33、David Coudert のメール:
> 
> was it incremental build (and from which beta) or fresh build ?
> 
> 
>> Le 20 août 2020 à 02:55, Kenji Iohara > > a écrit :
>> 
>> I have Mac OS X.15.6.   I could compile it with no problem, 
>> but I had some errors running ptestlong 
>> 
>> -- 
>> 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/592E1BCB-055D-4F13-9CD9-D86F6B27BCE9%40gmail.com
>>  
>> .
>> 
>> 
>> 
>>> 2020/08/19 18:17、Steven Trogdon >> >のメール:
>>> 
>>> Actually I have system m4ri-20200125 and not 20200115 installed. For me the 
>>> info in config.log was somewhat misleading. I have been using the sage 
>>> provided brial, so after rebuilding brial the html docs successfully built 
>>> and sage starts.
>>> 
>>> On Tuesday, August 18, 2020 at 11:07:05 PM UTC-6, Steven Trogdon wrote:
>>> This beta fails on Gentoo, apparently when building the html-docs, as and 
>>> upgrade from beta7 which built successfully.
>>> 
>>> [dochtml]   File "sage/rings/polynomial/polynomial_element.pyx", line 7893, 
>>> in sage.rings.polynomial.polynomial_element.Polynomial.roots 
>>> (build/cythonized/sage/rings/polynomial/polynomial_element.c:64031)
>>> [dochtml]   File 
>>> "/local/sage-git/sage/local/lib/python3.7/site-packages/sage/rings/polynomial/complex_roots.py",
>>>  line 246, in complex_roots
>>> [dochtml] factors = p.squarefree_decomposition()
>>> [dochtml]   File "sage/rings/polynomial/polynomial_element.pyx", line 1815, 
>>> in 
>>> sage.rings.polynomial.polynomial_element.Polynomial.squarefree_decomposition
>>>  (build/cythonized/sage/rings/polynomial/polynomial_element.c:18350)
>>> [dochtml]   File 
>>> "/local/sage-git/sage/local/lib/python3.7/site-packages/sage/categories/fields.py",
>>>  line 501, in _squarefree_decomposition_univariate_polynomial
>>> [dochtml] return Factorization(factors, unit=unit, sort=False)
>>> [dochtml]   File 
>>> "/local/sage-git/sage/local/lib/python3.7/site-packages/sage/structure/factorization.py",
>>>  line 299, in __init__
>>> [dochtml] self.__universe = Sequence(t[0] for t in x).universe()
>>> [dochtml]   File 
>>> "/local/sage-git/sage/local/lib/python3.7/site-packages/sage/structure/sequence.py",
>>>  line 255, in Sequence
>>> [dochtml] from sage.rings.polynomial.pbori import BooleanMonomialMonoid
>>> [dochtml] ImportError: libm4ri-0.0.20200115.so 
>>> : cannot open shared object file: No such 
>>> file or directory
>>> make[3]: *** [Makefile:1864: doc-html] Error 1
>>> make[2]: *** [Makefile:1754: all-start] Error 2
>>> 
>>> I have system m4ri-2010115 and m4ri3-20200115 installed. From config.log
>>> 
>>> configure:36038: result: m4ri-20200115:   using 
>>> system package; SPKG will not be installed
>>> configure:36038: result: m4rie-20200115:  using 
>>> system package; SPKG will not be installed
>>> 
>>> and
>>> 
>>> configure:24084: will use system package and not install SPKG lrcalc
>>> ## -- ##
>>> ## Checking whether SageMath should install SPKG m4rie... ##
>>> ## -- ##
>>> configure:24184: checking whether any of m4ri is installed as or will be 
>>> installed as SPKG
>>> configure:24193: result: no
>>> configure:24196: checking m4rie/m4rie.h usability
>>> configure:24196: g++ -std=gnu++11 -c -g -O2   conftest.cpp >&5
>>> configure:24196: $? = 0
>>> configure:24196: result: yes
>>> configure:24196: checking m4rie/m4rie.h presence
>>> configure:24196: g++ -E -std=gnu++11   conftest.cpp
>>> configure:24196: $? = 0
>>> configure:24196: result: yes
>>> configure:24196: checking for m4rie/m4rie.h
>>> configure:24196: result: yes
>>> 
>>> So my system m4ri is not found even though installed.
>>> 
>>> -- 
>>> 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/1a0cd293-12bf-4c04-a6d7-e12774362819o%40googlegroups.com
>>>  
>>> .
>> 
>> 
>> -- 
>> You re

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

2020-08-20 Thread David Coudert 
was it incremental build (and from which beta) or fresh build ?


> Le 20 août 2020 à 02:55, Kenji Iohara  a écrit :
> 
> I have Mac OS X.15.6.   I could compile it with no problem, 
> but I had some errors running ptestlong 
> 
> -- 
> 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/592E1BCB-055D-4F13-9CD9-D86F6B27BCE9%40gmail.com
>  
> .
> 
> 
> 
>> 2020/08/19 18:17、Steven Trogdon > >のメール:
>> 
>> Actually I have system m4ri-20200125 and not 20200115 installed. For me the 
>> info in config.log was somewhat misleading. I have been using the sage 
>> provided brial, so after rebuilding brial the html docs successfully built 
>> and sage starts.
>> 
>> On Tuesday, August 18, 2020 at 11:07:05 PM UTC-6, Steven Trogdon wrote:
>> This beta fails on Gentoo, apparently when building the html-docs, as and 
>> upgrade from beta7 which built successfully.
>> 
>> [dochtml]   File "sage/rings/polynomial/polynomial_element.pyx", line 7893, 
>> in sage.rings.polynomial.polynomial_element.Polynomial.roots 
>> (build/cythonized/sage/rings/polynomial/polynomial_element.c:64031)
>> [dochtml]   File 
>> "/local/sage-git/sage/local/lib/python3.7/site-packages/sage/rings/polynomial/complex_roots.py",
>>  line 246, in complex_roots
>> [dochtml] factors = p.squarefree_decomposition()
>> [dochtml]   File "sage/rings/polynomial/polynomial_element.pyx", line 1815, 
>> in 
>> sage.rings.polynomial.polynomial_element.Polynomial.squarefree_decomposition 
>> (build/cythonized/sage/rings/polynomial/polynomial_element.c:18350)
>> [dochtml]   File 
>> "/local/sage-git/sage/local/lib/python3.7/site-packages/sage/categories/fields.py",
>>  line 501, in _squarefree_decomposition_univariate_polynomial
>> [dochtml] return Factorization(factors, unit=unit, sort=False)
>> [dochtml]   File 
>> "/local/sage-git/sage/local/lib/python3.7/site-packages/sage/structure/factorization.py",
>>  line 299, in __init__
>> [dochtml] self.__universe = Sequence(t[0] for t in x).universe()
>> [dochtml]   File 
>> "/local/sage-git/sage/local/lib/python3.7/site-packages/sage/structure/sequence.py",
>>  line 255, in Sequence
>> [dochtml] from sage.rings.polynomial.pbori import BooleanMonomialMonoid
>> [dochtml] ImportError: libm4ri-0.0.20200115.so 
>> : cannot open shared object file: No such 
>> file or directory
>> make[3]: *** [Makefile:1864: doc-html] Error 1
>> make[2]: *** [Makefile:1754: all-start] Error 2
>> 
>> I have system m4ri-2010115 and m4ri3-20200115 installed. From config.log
>> 
>> configure:36038: result: m4ri-20200115:   using 
>> system package; SPKG will not be installed
>> configure:36038: result: m4rie-20200115:  using 
>> system package; SPKG will not be installed
>> 
>> and
>> 
>> configure:24084: will use system package and not install SPKG lrcalc
>> ## -- ##
>> ## Checking whether SageMath should install SPKG m4rie... ##
>> ## -- ##
>> configure:24184: checking whether any of m4ri is installed as or will be 
>> installed as SPKG
>> configure:24193: result: no
>> configure:24196: checking m4rie/m4rie.h usability
>> configure:24196: g++ -std=gnu++11 -c -g -O2   conftest.cpp >&5
>> configure:24196: $? = 0
>> configure:24196: result: yes
>> configure:24196: checking m4rie/m4rie.h presence
>> configure:24196: g++ -E -std=gnu++11   conftest.cpp
>> configure:24196: $? = 0
>> configure:24196: result: yes
>> configure:24196: checking for m4rie/m4rie.h
>> configure:24196: result: yes
>> 
>> So my system m4ri is not found even though installed.
>> 
>> -- 
>> 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/1a0cd293-12bf-4c04-a6d7-e12774362819o%40googlegroups.com
>>  
>> .
> 
> 
> -- 
> 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...@g