-
-
Notifications
You must be signed in to change notification settings - Fork 514
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
sage --fixdoctests --update-known-test-failures
; silence modularized distributions in CI
#36264
sage --fixdoctests --update-known-test-failures
; silence modularized distributions in CI
#36264
Conversation
d603403
to
834ad0a
Compare
[testenv:sagepython-sagewheels] | ||
basepython = {env:SAGE_VENV}/bin/python | ||
package_env = .pkg-sagepython | ||
|
||
[testenv:sagepython-norequirements] | ||
basepython = {env:SAGE_VENV}/bin/python3 | ||
package_env = .pkg-sagepython | ||
|
||
|
||
[testenv:sagepython-sagewheels-nopypi-norequirements] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
single empty line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This break is intended - this sets apart the default environment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK.
[testenv:sagepython-sagewheels] | ||
basepython = {env:SAGE_VENV}/bin/python | ||
package_env = .pkg-sagepython | ||
|
||
[testenv:sagepython-norequirements] | ||
basepython = {env:SAGE_VENV}/bin/python3 | ||
package_env = .pkg-sagepython | ||
|
||
|
||
[testenv:sagepython-sagewheels-nopypi-norequirements] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two lines, intended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this separates the default environment from the others above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK.
}, | ||
"sage.repl.attach": { | ||
"ntests": 128 | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No "failed: false"?
Or "success: true"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the timings2.json files created by the doctester don't have these.
# Build dependencies according to requirements.txt (all versions fixed). | ||
# Use ONLY the wheels built and stored by the Sage distribution (no PyPI): | ||
# | ||
# ./sage -sh -c '(cd pkgs/sagemath-standard && tox -v -v -v -e sagepython-sagewheels-nopypi)' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No sagepython-sagewheels-nopypi
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the envlist
only lists the default environments, i.e., those that will be tested if one uses tox
without the -e
switch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK. Thanks.
# ./sage -sh -c '(cd pkgs/sagemath-standard && tox -v -v -v -e sagepython-sagewheels-nopypi)' | ||
# | ||
sagepython-sagewheels-nopypi, | ||
# |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#
# SUPPORTED ENVIRONMENTS:
#
No?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've changed the format from "SUPPORTED" / "OTHER SUPPORTED" to (unmarked) default / "OTHER SUPPORTED"
I got
Is it really running "sage -t -p "? |
|
From
I don't understand the output. It seems not running anything. |
"--fixed-point" sounds good by itself. But since it follows "--fixdoctests", it makes me stop and think. An alternative is "--stabilize". Just a suggestion. |
Is this normal? I ran this after |
There is an error |
From
why does this run?
It seems that this runs if |
Thanks, fixed in 93f6a05 |
Thanks, done in e380f9a |
It gives an error now after a61cdbf |
The |
This must have been an old |
Before it tests the given files, it uses this command to see if the |
I also considered |
Then how about not logging the line "Running ... ./src/sage/version.py", but instead logging the result of the check? That log looks internal. |
The I tested again after This
works though. So the problem is with |
Ah, yes. The doctester is provided by sagemath-repl, which depends on sagemath-objects. Because of this, sagemath-objects is not tested using the doctester. (Also, the |
I suspected that sort of things. Then how about detecting such a situation, and warn the user of |
…with 0 tests, no errors
…n-test-failures.json
… simplify spkg-install
…ut only run tests if SAGE_CHECK
…tion all (for 10.2.beta2)
…ithout distributions
7e85c27
to
23e9923
Compare
Documentation preview for this PR (built with commit 23e9923; changes) is ready! 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Thank you! |
The distributions
sagemath-repl
andsagemath-categories
run parts of the testsuite in a virtual environment created bytox
when SAGE_CHECK=yes. This also runs as part of the Build & Test CI.Here we make several improvements:
--baseline-stats-path={toxinidir}/known-test-failures.json
known-test-failures.json
, are encounteredTo help maintain the
known-test-failures.json
, we also add new features to the commandsage --fixdoctests
.sage --fixdoctests --update-known-test-failures
reads the stats files generated by the doctester in the virtual environments and writes updatedknown-test-failures.json
files to the source treentests
- number of doctests of a module that were runsage --fixdoctests
also receives new switches--distribution all
,--fixed-point
,--verbose
,--no-diff
and some other improvements.📝 Checklist
⌛ Dependencies
pyproject.toml
files #36263 (merged here)sage -t
: Distinguish .pxd from .pyx in doctest basenames #36238 (merged here)