| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (27)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists. You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file. WalkthroughA single test identifier was added to the Windows environment-polluting tests list in the CI workflow configuration, expanding the set of tests flagged as environment-polluting for Windows CI runs. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
Poem🚥 Pre-merge checks | ✅ 2 | ❌ 1 ❌ Failed checks (1 inconclusive)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. ❤️ ShareComment @coderabbitai help to get the list of available commands and usage tips. |
Sorry, something went wrong.
|
Double check tests in test_class.py, test_configparser.py, test_context.py, test_str.py, test_str.py, test_subprocess.py |
Sorry, something went wrong.
|
Note to self: testing if, given the new timeout, whether timeouts count as failures, or errors (expectedFailure vs skips) |
Sorry, something went wrong.
There was a problem hiding this comment.
A few extra things besides these inline comments:
Sorry, something went wrong.
| def setUp(self): | ||
| self.cx = sqlite.Connection.__new__(sqlite.Connection) | ||
|
|
||
| @unittest.skip('TODO: RUSTPYTHON') |
There was a problem hiding this comment.
Any particular reason for the skip?
Sorry, something went wrong.
There was a problem hiding this comment.
I'm not sure. For this PR, I mainly focused on downgrading/specifying the @unittest.skip's, so they were all already notated, I'm just downgrading/removing/specifying them.
This one specifically was skipping already, except the whole class was skipped, so I just moved it to the specific failing test. It didn't have a reason attached, so the moved reason also didn't.
Sorry, something went wrong.
There was a problem hiding this comment.
If an underlying reason can be given, it will certainly be helpful when someone tries to fix the problem.
Sorry, something went wrong.
There was a problem hiding this comment.
@fanninpm i understand the logic, but review is about the changes, not about the code seen
Sorry, something went wrong.
| # TODO: RUSTPYTHON; The `expectedFailure` here is from CPython, so this test actually fails. Not run on linux? | ||
| # @unittest.expectedFailure |
There was a problem hiding this comment.
@youknowone what do you want to do about this? Related: python/cpython#49572
Sorry, something went wrong.
There was a problem hiding this comment.
I found our __new__ behavior is different from Python 3.14. (not checked incompatibility of 3.13 or changed in 3.14)
Let's see that change affect this change
Sorry, something went wrong.
There was a problem hiding this comment.
Overall it looks great!
Minor nitpicks about some added code that we can delete.
TYSM!!!
Sorry, something went wrong.
|
|
||
| @os_helper.skip_unless_symlink | ||
| @unittest.skip('TODO: RUSTPYTHON; No such file or directory "..."') | ||
| @unittest.skip('TODO: RUSTPYTHON; alters the execution environment (env changed)') |
There was a problem hiding this comment.
For better tracking:
| @unittest.skip('TODO: RUSTPYTHON; alters the execution environment (env changed)') | |
| @unittest.skipIf( | |
| 'RUSTPYTHON_SKIP_ENV_POLLUTERS' in os.environ, | |
| 'TODO: RUSTPYTHON; alters the execution environment (env changed)' | |
| ) |
...and when you do this, please add test_tempfile to the ENV_POLLUTING_TESTS_COMMON list in .github/workflows/ci.yaml.
You may end up needing to do something like this:
| @unittest.skip('TODO: RUSTPYTHON; alters the execution environment (env changed)') | |
| @unittest.skipIf( | |
| sys.platform == 'linux' and 'RUSTPYTHON_SKIP_ENV_POLLUTERS' in os.environ, | |
| 'TODO: RUSTPYTHON; alters the execution environment (env changed)' | |
| ) |
...or this:
| @unittest.skip('TODO: RUSTPYTHON; alters the execution environment (env changed)') | |
| @unittest.skipIf( | |
| sys.platform in ('darwin', 'linux') and 'RUSTPYTHON_SKIP_ENV_POLLUTERS' in os.environ, | |
| 'TODO: RUSTPYTHON; alters the execution environment (env changed)' | |
| ) |
...in which case(s), please make sure test_tempfile is added to the appropriate OS-specific variable(s) in .github/workflows/ci.yaml.
Sorry, something went wrong.
There was a problem hiding this comment.
I'm still trying to nail down the test_tempfile.py error to double check, but fyi there may an issue with the ENV_POLLUTING_TESTS_COMMON list.
In the last test run, it seems that test.test_multiprocessing_forkserver.test_threads and test.test_multiprocessing_spawn.test_threads had a similar ENV CHANGED issue, despite the fact that no changes are made to the test_multiprocessing_spawn tests
Sorry, something went wrong.
There was a problem hiding this comment.
Thank you so much! You seem to find many outdated skips in our test code.
Please make sure unskipped tests are not actually flaky. Running multiple times of them will be helpful.
Sometimes they are flaky on specific platforms. I will run the entire CI multiple times once this is done.
Sorry, something went wrong.
|
@youknowone It should be ok to rereview/run the CI/CD tests. Like I said, there seem to be intermittent issues with test.test_multiprocessing_forkserver.test_threads + test.test_multiprocessing_spawn.test_threads but it seems to be unrelated. |
Sorry, something went wrong.
|
You’re right. those are making it hard to see the actual results of this test. I’ll fix that and run it again. |
Sorry, something went wrong.
|
the failure looks like unrelated ERROR: test_saturation (test.test_concurrent_futures.test_process_pool.ProcessPoolForkProcessPoolExecutorTest.test_saturation)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/Users/runner/work/RustPython/RustPython/crates/pylib/Lib/test/test_concurrent_futures/test_process_pool.py", line 114, in test_saturation
executor.submit(sem.acquire)
^^^
File "/Users/runner/work/RustPython/RustPython/crates/pylib/Lib/concurrent/futures/process.py", line 791, in submit
raise BrokenProcessPool(self._broken)
concurrent.futures.process.BrokenProcessPool: A child process terminated abruptly, the process pool is not usable anymore
2 tests failed:
test.test_concurrent_futures.test_process_pool
test.test_concurrent_futures.test_shutdown
|
Sorry, something went wrong.
There was a problem hiding this comment.
@terryluan12 Thank you so much! I wish your awesome script to be integrated to our tools soon. Unskipping tests is not a 5 seconds task, you made it in great way. Thanks!
No issue for 6 runs. It could be not lucky enough though
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.