Re: [sage-support] sagemathlib only building single-threaded

2023-02-12 Thread John H Palmieri
I have been setting MAKE and MAKEFLAGS for a long time, and I have not seen 
any difference in the behavior of "make build". If I unset MAKE and 
MAKEFLAGS, then it takes longer to build sagelib, as it should.

On Saturday, February 11, 2023 at 11:44:43 AM UTC-8 Nils Bruin wrote:

> On Saturday, 11 February 2023 at 01:51:47 UTC-8 Dima Pasechnik wrote:
> >
> >make -j8 normaliz pynormaliz
> >
> > "sage -i"  is obsolete - at least in my mind :-)
> OK -- thanks! so what used to be "spkg"s are now makefile targets. That 
> reduces the possibility of having "third party" spkgs -- I guess that means 
> they should be packaged as "pip" packages instead.
>
> Also for this, sage itself actually instructed me to install it with `sage 
> -i`, so if "make" is now preferred, we should change docs on that. I think 
> it even suggested something like "!sage -i normaliz" which is difficult to 
> find a make analogue of.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/ae28def1-4eb6-4c44-b2a2-8ab0fdee9863n%40googlegroups.com.


Re: [sage-support] Re: Sage 9.8.rc1 builds, but reports an empty list of packages failed.

2023-02-12 Thread Dr. David Kirkby
On Sat, 11 Feb 2023 at 22:11, Dima Pasechnik  wrote:

>
>
> I'm just running
>>
>> make -j ptestlong
>>
>
> yes. Although -j without a parameter is a bit risky...
>

Point taken Dima about using -j without a parameter. That could have been
tricky if doctesting had used thousands of threads.😂😂

TLDR: I have sage  9.8 built and passed all tests with the latest R. The
rpy in Sage is compatible with the latest R, and does not need updating
just to work with the current version of R

There are a couple of things bugging me.

* Sage is only doctesting with 8 threads.
* A message "pytest is not installed in the venv, skip checking tests that
rely on it" This is despite I have pytest - admittedly an old version.
* A weird failure of 'make' when pytest was not installed.

*This is what I did. *

1) Deleted anything and everything related to Conda. The fact it had
changed my prompt to have "(base)" in it, and the prompt seemed to take a
long time to appear when a terminal was opened, was not giving me a good
feeling. I felt the system was in charge of me, rather than the other way
around. 😂😂

2) Deleting *everything* Conda related meant deleting the recent R. The R I
had was from the Ubuntu repository, which is R version 3.6.3 (2020-02-29) -
i.e. almost 3 years old.

3) Built Sage with the old R 3.6.3

$ ./configure
$ make -j 50 ptestlong

sage built okay, using the old R.

When running the doctests I saw this message

*"Doctesting 4451 files using 8 threads"*

Why does Sage not use 50 threads when running the tests, but only 8? I'd
told make to use 50.

The following was the result of the doctesting. The build failed.

sage -t --long --warn-long 41.7
--random-seed=247878169657737533415589408317275108273
src/sage/tests/cmdline.py
[217 tests, 47.85 s]
--
sage -t --long --warn-long 41.7
--random-seed=247878169657737533415589408317275108273
src/sage/rings/polynomial/polynomial_quotient_ring_element.py * # 6
doctests failed*
--
Total time for all tests: 1898.7 seconds
cpu time: 12100.3 seconds
cumulative wall time: 13160.6 seconds
Features detected for doctesting:
4ti2,cvxopt,dvipng,gfan,graphviz,imagemagick,lrslib,nauty,palp,pandoc,pdf2svg,pdftocairo,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sagemath_doc_html,sphinx
*pytest is not installed in the venv*, skip checking tests that rely on it
make[2]: *** [Makefile:273: test] Error 1
make[2]: Leaving directory '/home/drkirkby/sage-9.8'
make[1]: *** [Makefile:288: ptest] Error 2
make[1]: Leaving directory '/home/drkirkby/sage-9.8'
make: *** [Makefile:294: ptestlong] Error 2
drkirkby@canary:~/sage-9.8$

I expected to see a list of the tests that failed, but I didn't see any
list, despite polynomial_quotient_ring_element.py indicated 6 failures.

Next I decided to

1) Build the latest R from source, as I did not want a 3-year old version.
That needed quite a bit of work to get all the dependencies R wanted for an
optimal configuration. I'm not surprised that maintaining the R package was
difficult.

2) Install pytest as there was an error message about it not being
installed in the venv, whatever the venv is. (Typo for environment?) That
gave me pytest version 4.6.9. I see the latest is 7.x, so I assume 4.6.9 is
pretty old

3) Rebuild Sage.

$ ./configure
$ make -j 50 ptestlong.

This time, with pytest present, there's an error message it is not, but the
build does not fail. All tests pass. So the rpy in Sage is compatible with
the latest R, and does not need updating just to work with the current
version of R.


sage -t --long --warn-long 61.6
--random-seed=244047359021345785605807767847544173245
src/sage/libs/flint/fmpz_poly_mat.pxd
[0 tests, 0.00 s]
sage -t --long --warn-long 61.6
--random-seed=244047359021345785605807767847544173245
src/sage/schemes/toric/sheaf/__init__.py
[0 tests, 0.00 s]
--
*All tests passed!*
--
Total time for all tests: 1873.0 seconds
cpu time: 12087.9 seconds
cumulative wall time: 13194.0 seconds
Features detected for doctesting:
4ti2,cvxopt,dvipng,gfan,graphviz,imagemagick,lrslib,nauty,palp,pandoc,pdf2svg,pdftocairo,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sagemath_doc_html,sphinx
pytest is not installed in the venv, skip checking tests that rely on it
make[2]: Leaving directory '/home/drkirkby/sage-9.8

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsu