Well… This one didn’t go too well.
Reminder : my configuration :
charpent@zen-book-flip:/usr/local/sage-10$ ./config.status --config
--enable-dot2tex --enable-fricas --with-system-fricas=yes
--enable-gap_packages --enable-singular_jupyter --enable-msolve
--without-system-brial --disable-editable --with-system-editables=no
--disable-ccache --with-system-m4ri=no --with-system-m4rie=no
System’s fricas *IS* installed, and works :
charpent@zen-book-flip:/usr/local/sage-10$ fricas openServer result 0
FriCAS Computer Algebra System Version: FriCAS 1.3.11 built with gcl 2.6.14
Timestamp: Sun Jul 28 16:52:27 UTC 2024
-----------------------------------------------------------------------------
Issue )copyright to view copyright notices. Issue )summary for a summary of
useful system commands. Issue )quit to leave FriCAS and return to shell.
-----------------------------------------------------------------------------
(1) -> 2+2 (1) 4 Type: PositiveInteger (2) -> )quit
However, Sage doesn’t seem to be able to find the relevant files, and fails
*all* the tests involving fricas. In the following tests, *all* of the
errors are on examples involving Fricas :
---------------------------------------------------------------------- sage
-t --long --warn-long 30.0
--random-seed=258790151247230234231313284285510764479
src/sage/symbolic/expression.pyx # 2 doctests failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/symbolic/integration/integral.py # 3 doctests failed sage -t
--long --warn-long 30.0
--random-seed=258790151247230234231313284285510764479
src/sage/interfaces/fricas.py # 172 doctests failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/combinat/posets/posets.py # 1 doctest failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/calculus/calculus.py # 6 doctests failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/functions/other.py # 1 doctest failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/calculus/desolvers.py # 13 doctests failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/doctest/forker.py # 5 doctests failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/functions/orthogonal_polys.py # 6 doctests failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/rings/finite_rings/integer_mod.pyx # 2 doctests failed sage -t
--long --warn-long 30.0
--random-seed=258790151247230234231313284285510764479
src/sage/functions/jacobi.py # 4 doctests failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/matrix/matrix1.pyx # 4 doctests failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/functions/log.py # 3 doctests failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/symbolic/expression_conversions.py # 20 doctests failed sage -t
--long --warn-long 30.0
--random-seed=258790151247230234231313284285510764479
src/sage/symbolic/integration/external.py # 13 doctests failed sage -t
--long --warn-long 30.0
--random-seed=258790151247230234231313284285510764479
src/sage/functions/special.py # 10 doctests failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/rings/finite_rings/integer_mod_ring.py # 1 doctest failed sage -t
--long --warn-long 30.0
--random-seed=258790151247230234231313284285510764479
src/sage/rings/infinity.py # 2 doctests failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/functions/gamma.py # 4 doctests failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/symbolic/ring.pyx # 1 doctest failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/functions/error.py # 1 doctest failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/rings/integer_ring.pyx # 1 doctest failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/rings/rational_field.py # 1 doctest failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/rings/complex_double.pyx # 1 doctest failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/rings/real_double.pyx # 1 doctest failed sage -t --long
--warn-long 30.0 --random-seed=258790151247230234231313284285510764479
src/sage/rings/real_mpfr.pyx # 1 doctest failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/functions/generalized.py # 1 doctest failed
----------------------------------------------------------------------
A couple of other doctest fail during ptestlong but pass with no errors
when re-ran standalone :
sage -t --long --warn-long 30.0
--random-seed=258790151247230234231313284285510764479
src/sage/doctest/test.py # 23 doctests failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/tests/cmdline.py # 7 doctests failed sage -t --long --warn-long
30.0 --random-seed=258790151247230234231313284285510764479
src/sage/doctest/control.py # 7 doctests failed
In all these cases, the test.log suggests that there may be due to a
crossing of the answers between tests (one test receiving the answer
expected frim another test).
Two failures involve gap :
sage -t --long --warn-long 30.0
--random-seed=258790151247230234231313284285510764479
src/sage/coding/linear_code.py # 4 doctests failed
The common cause seems to be :
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/local/sage-10/local/lib/gap/pkg/guava//bin/wtdist'
and, indeed :
charpent@zen-book-flip:/usr/local/sage-10$ find
/usr/local/sage-10/local/lib/gap/pkg/guava/bin -name wtdist
/usr/local/sage-10/local/lib/gap/pkg/guava/bin/x86_64-pc-linux-gnu-default64-kv9/wtdist
More serious :
sage -t --long --warn-long 30.0
--random-seed=258790151247230234231313284285510764479
src/sage/libs/gap/element.pyx # Killed due to segmentation fault
This is reproducible. according to test.log, the last test to be
successfully executed is
sage: s = libgap.Sum sage: s(libgap([1,2])) 3 sage: s(libgap(1), libgap(2))
Traceback (most recent call last): ... GAPError: Error, no method found!
Error, no 1st choice method found for `SumOp' on 2 arguments sage: for i in
range(100): ....: rnd = [ randint(-10,10) for i in range(randint(0,7)) ]
....: # compute the sum in GAP ....: _ = libgap.Sum(rnd) ....: try: ....:
libgap.Sum(*rnd) ....: print('This should have triggered a ValueError')
....: print('because Sum needs a list as argument') ....: except
ValueError: ....: pass
and the crash could have been created by :
sage: libgap_exec = libgap.eval("Exec") sage: libgap_exec('echo hello from
the shell') hello from the shell
Config and logs follow by separate email (the damn Googlegroups interface
does not accept .tar.gz files
Any advice/hint welcome !
HTH,
Le vendredi 24 janvier 2025 à 19:55:26 UTC+1, Emmanuel Charpentier a écrit :
> The curious Wolfram calls reappeared at the start of make ptestlong
> (which rechecks the documentation), and hanged the whole thing. Killing
> them allowed the process to restart.
>
> ptestlong still running…
>
> Le vendredi 24 janvier 2025 à 12:50:23 UTC+1, Emmanuel Charpentier a
> écrit :
>
>> After disabling the system’s m4ri* libraries, compilation could indeed
>> proceed ;it hanged on a couple of curious Woilfram calls (yes, I use the
>> gratis-but-not-free Wolfram engine) :
>> 1713185 pts/5 Sl+ 0:00
>> /usr/local/Wolfram/WolframEngine/14.0/SystemFiles/Kernel/Binaries/Linux-x86-64/WolframKernel
>>
>> -wlbanner -rawterm 1723650 pts/8 Sl+ 0:00
>> /usr/local/Wolfram/WolframEngine/14.0/SystemFiles/Kernel/Binaries/Linux-x86-64/WolframKernel
>>
>> -wlbanner -rawterm
>>
>> Killing these processes (kill -KILL was necessary, -HUP and -TERM were
>> unsufficient) allowed the compilation to finish.
>>
>> I do not understand what these processes were trying to do. Hints ?
>>
>> Now `ptestlong running…
>>
>> Le jeudi 23 janvier 2025 à 22:14:51 UTC+1, Antonio Rojas a écrit :
>>
>>> This is a bug in m4ri 20240729. Disable system m4ri, or ask Debian to
>>> apply
>>> https://github.com/malb/m4ri/commit/3197be5f7d3c67e8f13e32516557f35cbf4ff6ce
>>>
>>> El jueves, 23 de enero de 2025 a las 18:01:14 UTC+1,
>>> [email protected] escribió:
>>>
>>> Another attempt : adding --disable-ccache to my config, reconfiguring
>>> an re-making still fails on sagelib-10.6.beta4. From
>>> logs/pkgs/sagelib-10.6.beta4.log :
>>> [spkg-install] from /usr/local/sage-10/pkgs/sagemath-standard/s
>>> age/libs/polybori/pb_wrap.h:7: [spkg-install]
>>> /usr/local/sage-10/local/include/polybori/groebner/BoundedDivisor
>>> sOf.h:43:15: warning: 'template<class _Arg, class _Result> struct
>>> std::unary_fun ction' is deprecated [-Wdeprecated-declarations]
>>> [spkg-install] 43 | public std::unary_function<Monomial, MonomialSet> {
>>> [spkg-install] | ^~~~~~~~~~~~~~ [spkg-install]
>>> /usr/include/c++/14/bits/stl_function.h:117:12: note: declared he re
>>> [spkg-install] 117 | struct unary_function [spkg-install] | ^~~~~~~~~~~~~~
>>> [spkg-install] g++: warning: @SIMD_CFLAGS@: linker input file unused
>>> because lin king not done [spkg-install] g++: error: @SIMD_CFLAGS@: linker
>>> input file not found: No such file or directory [spkg-install] g++:
>>> warning: @SIMD_CFLAGS@: linker input file unused because linking not done
>>> [spkg-install] g++: error: @SIMD_CFLAGS@: linker input file not found: No
>>> such file or directory [spkg-install] g++: warning: @SIMD_CFLAGS@: linker
>>> input file unused because linking not done [spkg-install] g++: error:
>>> @SIMD_CFLAGS@: linker input file not found: No such file or directory
>>> [spkg-install] g++: warning: @SIMD_CFLAGS@: linker input file unused
>>> because linking not done [spkg-install] g++: error: @SIMD_CFLAGS@: linker
>>> input file not found: No such file or directory [spkg-install] g++:
>>> warning: @SIMD_CFLAGS@: linker input file unused because linking not done
>>> [spkg-install] g++: error: @SIMD_CFLAGS@: linker input file not found: No
>>> such file or directory [spkg-install] g++: warning: @SIMD_CFLAGS@: linker
>>> input file unused because linking not done [spkg-install] g++: error:
>>> @SIMD_CFLAGS@: linker input file not found: No such file or directory
>>> [spkg-install] g++: warning: @SIMD_CFLAGS@: linker input file unused
>>> because linking not done [spkg-install] g++: error: @SIMD_CFLAGS@: linker
>>> input file not found: No such file or directory [spkg-install] error:
>>> command '/usr/bin/g++' failed with exit code 1 [spkg-install]
>>> [spkg-install] ERROR Backend subprocess exited when trying to invoke
>>> build_wheel [spkg-install]
>>> *****************************************************************:
>>>
>>> Any hint ?
>>>
>>> Le jeudi 23 janvier 2025 à 17:32:41 UTC+1, Emmanuel Charpentier a écrit :
>>>
>>> BTW, ccache is *not* installed systemwide. Would it help to try to
>>> install it ?
>>>
>>> Le jeudi 23 janvier 2025 à 17:27:21 UTC+1, Emmanuel Charpentier a écrit :
>>>
>>> From my config.log :
>>> configure:113368: result: ccache: optional, use "./configure
>>> --enable-ccache" to install SPKG version 4.10.2
>>>
>>> A Sage bug, if I follow you…
>>>
>>> HTH,
>>>
>>> Le jeudi 23 janvier 2025 à 17:13:02 UTC+1, Dima Pasechnik a écrit :
>>>
>>> It should not be getting installed, unless explicitly requested.
>>> (the error you see comes from ccache installation procedure
>>> In your top-level config.log, do you see something like
>>>
>>> configure:113516: result: ccache: optional, use "./configure
>>> --enable-ccache" to install SPKG version 4.10.2
>>>
>>> - if you see something different, that's probably not something on
>>> Sage side. If you see this, but still see it getting installed, it's
>>> probably a Sage bug.
>>>
>>>
>>> On Thu, Jan 23, 2025 at 9:11 AM John Cremona <[email protected]>
>>> wrote:
>>> >
>>> > For what it is worth, I tried again with a fresh git clone of
>>> > 10.6.beta4, the only commands I used were ./bootstrap; ./configure;
>>> > make and I get the same problem with ccache. Some sort of download
>>> > fails.
>>> >
>>> > Here are the logs.
>>> >
>>> > John
>>> >
>>> > On Thu, 23 Jan 2025 at 11:19, John Cremona <[email protected]>
>>> wrote:
>>> > >
>>> > > I have trouble building 10.6.beta4.
>>> > >
>>> > > I must be getting old as every time I build Sage these days, I get
>>> > > problems I have never seen before on computers which have
>>> successfully
>>> > > built Sage hundreds of times before. It just seems to get harder to
>>> > > get it right.
>>> > >
>>> > > After make distclean and ./bootstrap and ./configure and make, the
>>> > > failure is in building ccache-4.10.2. The log says that it is timing
>>> > > out while fetching
>>> > > https://github.com/Cyan4973/xxhash/archive/refs/tags/v0.8.2.tar.gz.
>>> > >
>>> > > My configure output includes this: "ccache:
>>> > > optional, use "./configure --enable-ccache" to install SPKG version
>>> > > 4.10.2"
>>> > > but I put nothing on the command line after ./configure, so I don't
>>> > > even know why it is trying to install ccache.
>>> > >
>>> > > Help!
>>> > >
>>> > > John
>>> > >
>>> > > On Sat, 18 Jan 2025 at 21:09, Volker Braun <[email protected]>
>>> 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
>>> > > >
>>> > > >
>>> > > > 5188024881d (tag: 10.6.beta4, github/develop) Updated SageMath
>>> version to 10.6.beta4
>>> > > > 5eb37241946 gh-39333: some ruff suggestions in algebras/
>>> > > > 8468f45f4a5 gh-39332: some changes about dict in combinat (ruff
>>> PLC0206)
>>> > > > d9a5d731e47 gh-39330: fix a bunch of typos and add some spaces
>>> after commas
>>> > > > f1b71f2a156 gh-39325: [DOC] Allow Sphinx PDF build to reflow long
>>> decimal expansions in code-blocks to avoid them extending beyond page
>>> limits
>>> > > > 4e66964ee2f gh-39324: less use of ParentWithGens
>>> > > > d09850e1a9b gh-39322: Implement the chi function in
>>> sage.crypto.sboxes
>>> > > > 3503f4cf7aa gh-39316: use memory allocator in
>>> `sage/combinat/designs/`
>>> > > > d37ff1aeb29 gh-39315: partial pep8 cleanup in Lie conformal
>>> algebras
>>> > > > f2bdadfef38 gh-39312: use memory allocator in
>>> `sage/coding/binary_code.pyx`
>>> > > > 66d1d42dcb6 gh-39306: simplify many range(0,n) to range(n)
>>> > > > f53ae51ad18 gh-39305: fixing some ruff PLR warnings
>>> > > > 056c849a5b6 gh-39303: let the categories handle "is_commutative"
>>> for rings
>>> > > > d2e5f02e880 gh-39302: adding the category keyword to padic rings
>>> and fields classes
>>> > > > 11312f9ad14 gh-39301: Using a new functions in libbraiding in
>>> zariski_vankampen
>>> > > > cd1dd19a97d gh-39298: small cleanup in tropical files
>>> > > > 2412b2b22d8 gh-39293: Fix segmentation fault in singular interface
>>> code
>>> > > > 80dd3a640b2 gh-39291: Workaround to allow flint to be compiled
>>> with numpy 2
>>> > > > cac2b74ce16 gh-39288: Fix the new release workflow by escaping
>>> special characters
>>> > > > 2ff22f9991b gh-39284: Remove failing modular ci tests
>>> > > > d4449201e58 gh-39282: Fix tests for Python 3.13
>>> > > > 422311a7e6b gh-39281: fix and activate the ruff check for F811
>>> > > > 880ee64f986 gh-39278: Meson: build groups even without gap
>>> > > > 5069f3f4921 gh-39277: Fix import duplication in `sage.rings.all`
>>> > > > 3756cd4a869 gh-39271: return correct error message when trying to
>>> add/delete vertex/edge from a static graph
>>> > > > ff96023665c gh-39268: Upgrade dependency requirements in
>>> accordance with Spec 0
>>> > > > dea78248d04 gh-39264: add parameter immutable to generators in
>>> `sage/graphs/digraph_generators.py` (part 1)
>>> > > > 025fc1ea848 gh-39263: Remove old deprecations in `algebras` and
>>> `categories`
>>> > > > 545f5bf7508 gh-39261: Fix tests with scipy 1.15
>>> > > > d5f99eccad4 gh-39253: some type annotations in modular folder
>>> > > > 3823c4361dc gh-39252: minor annotation details in posets to please
>>> mypy
>>> > > > 0e1a4ec0726 gh-39233: add some typing annotations to gens methods
>>> (-> tuple)
>>> > > > 9f4042a6e60 gh-39228: faster bidirectional dijkstra using pairing
>>> heap
>>> > > > 46c24c2ae14 gh-39220: some care in
>>> `src/sage/graphs/comparability.pyx`
>>> > > > 09274507705 gh-39201: Fix `spyx_tmp()` cleanup.
>>> > > > b5dbe52ca1e gh-39188: Declare Python 3.13 as supported in sagelib
>>> > > > 57fa9581511 gh-39185: Fix find_replacements with Python 3.13
>>> > > > ba0e89a5178 gh-39184: Refactor produce_latex_macro
>>> > > > c1dbfad7570 gh-39182: Define __iter__ method in iterator types
>>> > > > 07455c02b25 gh-39168: Addition of Kähler algebras as a category
>>> > > > e32f80afcb9 gh-39164: Update conda to use Python 3.12, drop 3.9
>>> and 3.10
>>> > > > c2e57524046 gh-39153: Mark several tests as random to avoid test
>>> failure
>>> > > > 2765b20e923 gh-39151: add parameter `forbidden_vertices` to some
>>> connectivity methods
>>> > > > 55137dcb6a7 gh-39147: Fix doctesting with Python 3.13
>>> > > > af9eace610d gh-39123: change ore_algebra package to latest version
>>> > > > a94a570bc29 gh-39008: Add Meson-specific settings to vscode
>>> settings
>>> > > > 8c9d4febfe8 gh-38965: adding an example of semiring
>>> > > > 15f25d90023 gh-38904: provide a class for partitions with bounded
>>> length and minimal part
>>> > > > 076e8d8b6b9 gh-38823: Graph Plotting updates
>>> > > > 1be0a589260 (tag: 10.6.beta3) Updated SageMath version to
>>> 10.6.beta3
>>> > > >
>>> > > > --
>>> > > > 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 [email protected].
>>> > > > To view this discussion visit
>>> https://groups.google.com/d/msgid/sage-release/04d57935-e97f-47c3-8d67-c070c2ec0b88n%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 [email protected].
>>> > To view this discussion visit
>>> https://groups.google.com/d/msgid/sage-release/CAD0p0K5TM5UdDcozVBGjotYJH5Fz7p_OYnb3pRM%3DWbWdtag%2BzA%40mail.gmail.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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/sage-release/7b8b6180-cf43-4188-a369-ce191019987cn%40googlegroups.com.