-
-
Notifications
You must be signed in to change notification settings - Fork 488
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 doctest option to hide features #34185
Comments
Branch: u/soehms/hide_features_34185 |
Author: Sebastian Oehms |
Commit: |
New commits:
|
comment:3
I think instead of reading from SAGE_PKGS directly, it would be better to refactor |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:5
Replying to @mkoeppe:
Actually, I didn't do that well. Many thanks for looking at the ticket! |
comment:6
A |
comment:7
Replying to @mkoeppe:
Will be in the next commit. I'm wondering what's wrong with the patchbots? For example:
All tests failing on the patchbots succeed in the Gitpod environment. But here there is a failing test, as well, but obviously unrelated to the branch. It is caused by:
This happens since |
comment:10
The recent commit takes care of joined features. In addition (in order to allow more interesting doctest examples) I make |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
Replying to @soehms:
See #34282 for a suggestion to have this fixed. Furthermore, when testing on a system with meataxe you may randomly run into a circular import issue in |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:14
The previous commit should fix the only failure that happened on the previous patchbot run. This is the following long test: Doctesting 1 file using 4 threads.
sage -t --long --random-seed=32647687899858611983071143867735298580 src/sage/doctest/sources.py
**********************************************************************
File "src/sage/doctest/sources.py", line 781, in sage.doctest.sources.FileDocTestSource._test_enough_doctests
Failed example:
for path, dirs, files in itertools.chain(os.walk('sage'), os.walk('doc')): # long time
path = os.path.relpath(path)
dirs.sort(); files.sort()
for F in files:
_, ext = os.path.splitext(F)
if ext in ('.py', '.pyx', '.pxd', '.pxi', '.sage', '.spyx', '.rst'):
filename = os.path.join(path, F)
FDS = FileDocTestSource(filename, DocTestDefaults(long=True, optional=True, force_lib=True))
FDS._test_enough_doctests(verbose=False)
Expected:
There are 3 unexpected tests being run in sage/doctest/parsing.py
There are 1 unexpected tests being run in sage/doctest/reporting.py
Got:
There are 7 tests in sage/doctest/control.py that are not being run
There are 3 unexpected tests being run in sage/doctest/parsing.py
There are 1 unexpected tests being run in sage/doctest/reporting.py
**********************************************************************
1 item had failures:
1 of 9 in sage.doctest.sources.FileDocTestSource._test_enough_doctests
[371 tests, 1 failure, 105.47 s]
----------------------------------------------------------------------
sage -t --long --random-seed=32647687899858611983071143867735298580 src/sage/doctest/sources.py # 1 doctest failed |
comment:15
I saw one typo when looking at the diff:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:17
Replying to Sébastien Labbé:
Done! In Addition I rebased over 9.7.rc0 and the current changes in #34282. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:20
Just rebasing to 9.8.beta1. |
This former Trac ticket will be continued in PR #35668. |
As suggested in #33823 (see comment 25) I make a first attempt for such an option here. The purpose of the option is to find test which need to be marked as
optional
but aren't right now.For example see the test of the following file which contains two tests involving the optional package
database_knotinfo
. Note that on the system where I produced the output below this feature is available.The first test is missing the
optional
tag. Thus, this would fail on a system without that feature. But, runningsage -t
without the new option does not show the problem:Using the new option this will be the case:
Depends on #34282
Depends on #34283
CC: @seblabbe
Component: doctest framework
Author: Sebastian Oehms
Branch/Commit: u/soehms/hide_features_34185 @
2a582f4
Issue created by migration from https://trac.sagemath.org/ticket/34185
The text was updated successfully, but these errors were encountered: