New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New make targets "sagelib-tox-...", "sage_docbuild-tox-...", ... #31535
Comments
Author: Matthias Koeppe |
New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:11
Moving this ticket to 9.4, as it seems unlikely that it will be merged in 9.3, which is in the release candidate stage |
comment:12
Setting a new milestone for this ticket based on a cursory review. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:17
Reduced the scope of the ticket |
This comment has been minimized.
This comment has been minimized.
comment:18
I've tried to test these locally but I always get some complaint about
This proceeded to build everything inside of
Is that expected (did I construct my example wrong?) |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
comment:21
Should be better with this branch |
comment:22
(needs |
comment:23
I just noticed these as well, probably from an empty
|
comment:24
Yes, this is #30876 |
Reviewer: Michael Orlitzky |
comment:25
Looking better now; regardless, the |
comment:26
Thanks! |
For all script packages
SPKG
that have an embedded source tree -- currentlysagelib
,sage_docbuild
,sage_sws2rst
-- we add a new target:SPKG-tox-%
(which callstox -e %
in the package's source tree)These targets are particularly useful for invoking them within the portability tests of the top-level
tox
:$ TARGETS_PRE=config.status tox -e docker-ubuntu-focal-standard -- sage_docbuild-tox
invokes the tox testing of thesage_docbuild
distribution$ EXTRA_CONFIGURE_ARGS="--disable-notebook" tox -e docker-ubuntu-focal-standard -- build sagelib-tox-python-sagewheels-nopypi
builds (in a Docker container) the Sage distribution (without Jupyter notebook) and then invokes the tox testing of sagelib (added in sagelib: Generate pyproject.toml and setup.cfg [install_requires], requirements.txt, Pipfile, and src/Pipfile #30913) in a venv populated using the wheels$ tox -e local-homebrew-macos-maximal -- build-local cysignals networkx sagelib-tox-python-sagewheels-sitepackages-norequirements-nopypi
(added in sagelib: Generate pyproject.toml and setup.cfg [install_requires], requirements.txt, Pipfile, and src/Pipfile #30913) builds the non-Python parts of the Sage distribution on top of Homebrew, using a virtual environment that uses homebrew's Python packages$ tox -e local-conda-forge-macos-src-environment -- sage_conf sagelib-tox-python-sagewheels-sitepackages-norequirements-nobuildisolation-nopypi
(needs sagelib: Generate pyproject.toml and setup.cfg [install_requires], requirements.txt, Pipfile, and src/Pipfile #30913, cython_aliases: Do not fail if one of the listed libraries is not known to pkgconfig #31384) uses thesrc/environment.yml
file to set up a complete environment from conda and then tests sagelib in a venv using toxDepends on #32899
CC: @jhpalmieri @dimpase @kliem @orlitzky @tobiasdiez
Component: porting
Author: Matthias Koeppe
Branch/Commit:
ad12d25
Reviewer: Michael Orlitzky
Issue created by migration from https://trac.sagemath.org/ticket/31535
The text was updated successfully, but these errors were encountered: