-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
MAINT: backports for 1.15.1 #22296
Merged
tylerjereddy
merged 7 commits into
scipy:maintenance/1.15.x
from
tylerjereddy:treddy_1.15.1_backports
Jan 10, 2025
Merged
MAINT: backports for 1.15.1 #22296
tylerjereddy
merged 7 commits into
scipy:maintenance/1.15.x
from
tylerjereddy:treddy_1.15.1_backports
Jan 10, 2025
+35
−10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a follow-up to scipygh-21983, and fixes some more issues reported on scipygh-18909. It's possible to run into these when building with a high level of parallelism, or trying to build just a single target like `spatial/_qhull.so` with Ninja.
This test was recently introduced in scipygh-22158. It causes a crash when running the test suite with `pytest-run-parallel`, because of writing to the same tempfile from multiple threads. [skip cirrus] [skip circle]
* Update the SciPy `1.15.1` release notes after some backport activity.
The one test failure is gh-22297, let me check that real quick. |
* TST: stats.Normal: bump tolerance on test of logcdf * Update scipy/stats/tests/test_continuous.py [skip ci] Co-authored-by: Matt Haberland <mhaberla@calpoly.edu> --------- Co-authored-by: Daniel Schmitz <40656107+dschmitz89@users.noreply.github.com>
* Update the SciPy `1.15.1` release notes following additional backport activity.
Ok, Matt already solved that one, so I've backported that in now. |
Regular CI is green. The diff is pretty small and looks sensible. Let's see if I can get a release done today. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A fairly serious bug (gh-22257) was discovered and patched, warranting a prompt release of
1.15.1
.Backports included so far:
TODO:
regular CI green
wheels CI green as precaution before starting release proper (could skip maybe, backport count is small-ish)
I had a few doc build warnings locally, but we have an issue open for that and it is "ok" in the release env usually I think.
Locally,
TestCurveFit.test_curvefit_omitnan
had a small tolerance issue;test_quad_vec_pool
failed because it took too long; I'll probably ignore both if CI is happy though