On Debian testing running on core i7 + 16 GB RAM, upgrading 10.2.beta1 to 10.2.beta2 and running ptestlong gives two permanent failures :
---------------------------------------------------------------------- sage -t --long --warn-long 215.1 --random-seed=113667280999692443400711992154116895484 src/sage/combinat/posets/posets.py # 1 doctest failed sage -t --long --warn-long 215.1 --random-seed=113667280999692443400711992154116895484 src/sage/functions/special.py # 2 doctests failed ----------------------------------------------------------------------both having been already reportedfor a couple betas.
HTH,
***********************************************
make[2]: Entering directory '/home/furutaka/work/sage/sage-10.2.beta2-condaSys/build/make'
make --no-print-directory /home/furutaka/mambaforge/envs/sage-build/var/lib/sage/installed/.dummy
make[3]: '/home/furutaka/mambaforge/envs/sage-build/var/lib/sage/installed/.dummy' is up to date.
make --no-print-directory /home/furutaka/mambaforge/envs/sage-build/var/lib/sage/installed/.dummy
make[3]: '/home/furutaka/mambaforge/envs/sage-build/var/lib/sage/installed/.dummy' is up to date.
make --no-print-directory /home/furutaka/mambaforge/envs/sage-build/var/lib/sage/installed/.dummy
make[3]: '/home/furutaka/mambaforge/envs/sage-build/var/lib/sage/installed/.dummy' is up to date.
make --no-print-directory /home/furutaka/mambaforge/envs/sage-build/var/lib/sage/installed/.dummy
make[3]: '/home/furutaka/mambaforge/envs/sage-build/var/lib/sage/installed/.dummy' is up to date.
make --no-print-directory all-sage-docs all-sage
/home/furutaka/mambaforge/envs/sage-build/bin/python /home/furutaka/work/sage/sage-10.2.beta2-condaSys/build/bin/sage-venv "/home/furutaka/mambaforge/envs/sage-build"
Unable to symlink '/home/furutaka/mambaforge/envs/sage-build/bin/python3.11' to '/home/furutaka/mambaforge/envs/sage-build/bin/python3.11'
Traceback (most recent call last):
File "/home/furutaka/work/sage/sage-10.2.beta2-condaSys/build/bin/sage-venv", line 54, in <module>
b.setup_python(c)
File "/home/furutaka/mambaforge/envs/sage-build/lib/python3.11/venv/__init__.py", line 292, in setup_python
copier(context.executable, path)
File "/home/furutaka/mambaforge/envs/sage-build/lib/python3.11/venv/__init__.py", line 235, in symlink_or_copy
shutil.copyfile(src, dst)
File "/home/furutaka/mambaforge/envs/sage-build/lib/python3.11/shutil.py", line 236, in copyfile
raise SameFileError("{!r} and {!r} are the same file".format(src, dst))
shutil.SameFileError: '/home/furutaka/mambaforge/envs/sage-build/bin/python3.11' and '/home/furutaka/mambaforge/envs/sage-build/bin/python3.11' are the same file
make[3]: *** [Makefile:2831: /home/furutaka/mambaforge/envs/sage-build/var/lib/sage/installed/python3_venv-3.11--home-furutaka-mambaforge-envs-sage-build-bin-python] Error 1
make[2]: *** [Makefile:2841: all-start] Error 2
make[2]: Leaving directory '/home/furutaka/work/sage/sage-10.2.beta2-condaSys/build/make'
real 0m0.183s
user 0m0.162s
sys 0m0.021s
***************************************************************
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):
It is safe to delete any log files and build directories, but they
contain information that is helpful for debugging build problems.
WARNING: If you now run 'make' again, the build directory of the
same version of the package will, by default, be deleted. Set the
environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.
make[1]: *** [Makefile:40: all-start] Error 1
make[1]: Leaving directory '/home/furutaka/work/sage/sage-10.2.beta2-condaSys'
make: *** [Makefile:13: all] Error 2
--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/7f9f6351-e406-4843-ab8c-7ecd0af61af8n%40googlegroups.com.
The build of 10.2.beta2 by following the procedure described infailed on my Fedora-38(x86_64) system as the following: