Skip to content
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.11.0rc2 #18671

Merged
merged 17 commits into from
Jun 16, 2023

Conversation

@h-vetinari
Copy link
Member

h-vetinari commented Jun 13, 2023

good to check with conda release manager @h-vetinari if there are any concerns I'm not addressing?

Would be good to have #18630. @rgommers marked it as a backport-candidate already (but also milestoned it for 1.12? 🤔 In any case, if it's not backported, I'll have to carry it on the feedstock, at least for ppc; this would also be manageable).

Otherwise there are no additional PRs that I'm aware of that we need for the conda-forge side, thanks for checking!

@rgommers
Copy link
Member

Would be good to have #18630. @rgommers marked it as a backport-candidate already (but also milestoned it for 1.12? 🤔

Agreed. Merged now, would be good to add to the backports here. That PR is going into 1.12; this backport PR pulls it into 1.11 - the milestones on the respective PRs indicate that; the issue itself is also marked for 1.11.0.

@rgommers
Copy link
Member

The pre-release job is failing with meson.build:57:2: ERROR: Problem encountered: SciPy requires Cython < 3.0. Let's remove that check again from meson.build - for details, see https://github.com/scipy/scipy/pull/18591/files#r1229148530.

@rgommers rgommers self-requested a review as a code owner June 14, 2023 07:40
@rgommers
Copy link
Member

The musllinux job is crashing due to pulling in numpy 2.0.0.dev - the --pre flag had to be added for the 1.25.0 pre-release wheel, but we shouldn't be tested 2.0 nightlies in the 1.11.x branch.

I pushed a commit that should fix both of the failing jobs.

@h-vetinari
Copy link
Member

The musllinux job is crashing due to pulling in numpy 2.0.0.dev

Speaking of numpy, does the condition numpy <1.28.0 still make sense now that the main branch targets 2.0? Doesn't have to be changed in this PR (and of course we can backport numpy 2.0 compatibility patches if we want to), but more out of curiosity.

@rgommers
Copy link
Member

Speaking of numpy, does the condition numpy <1.28.0 still make sense now that the main branch targets 2.0?

Yes it does - the N+3 condition still holds. A numpy 1.26.0 is planned; it's unlikely that there'll be any more minor releases beyond that, but you never know.

@rgommers
Copy link
Member

rgommers commented Jun 14, 2023

Hmm, musllinux got further but is still crashing in linalg/tests/test_decomp.py on TestSVD_GESDD.test_random_complex. It passes on main, with what looks like the same version of OpenBLAS (0.3.23). That seems to be related to #17630 (comment) and commit 5055c7e.

EDIT: that test has a random number seeding issue, which may explain why it behaves differently on different branches. I'll try to fix that on main first.

EDIT 2: it passed on a second run, without making a relevant change. So it's a flake or related to seeding - let's ignore it on the 1.11.x branch.

rgommers added a commit to rgommers/scipy that referenced this pull request Jun 14, 2023
These tests crash in a quite flaky way, as seen in scipygh-18671 and
previously also in scipygh-17630. So to make sure it's not due to
test ordering, avoid use of the global RandomState instance.
rgommers added a commit to rgommers/scipy that referenced this pull request Jun 14, 2023
These tests crash in a quite flaky way, as seen in scipygh-18671 and
previously also in scipygh-17630. So to make sure it's not due to
test ordering, avoid use of the global RandomState instance.
Copy link
Member

@tupui tupui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Tyler! LGTM from my perspective.

About the release notes, can we do some tweaking here? I had some talk with Matt and we might want to highlight other things in stats and in general.

@tylerjereddy
Copy link
Contributor Author

About the release notes, can we do some tweaking here? I had some talk with Matt and we might want to highlight other things in stats and in general.

Yes, please do make release notes suggestions here, or you can even open a PR against my branch or whatever suits. Apart from Matt, I think the feedback on the release notes was pretty light initially, probably the usual reason of folks being busy.

mckib2 and others added 2 commits June 14, 2023 10:27
…18630)

[skip ci]

---------

Co-authored-by: Ralf Gommers <ralf.gommers@gmail.com>
* Fixes scipy#18595

* use `git apply` to directly apply the patch from
scipygh-18595 that worked during the RC1 phase of current
release cycle; I'll skip the CI--it isn't tested there
which is why the patch is needed in the first place

[skip ci]
@tylerjereddy
Copy link
Contributor Author

  • the two additional backports have been added in, and the summary comment at the top of this PR has been updated accordingly
  • at the time of writing, the only outstanding item is making the release notes "better" + sparse relnotes updates probably

@tupui
Copy link
Member

tupui commented Jun 14, 2023

at the time of writing, the only outstanding item is making the release notes "better" + sparse relnotes updates probably

I will raise this to the sparse team on discord.

@tupui
Copy link
Member

tupui commented Jun 14, 2023

@jjerphan is going to help for the sparse part tomorrow 😃 Thanks!!

@jjerphan
Copy link
Contributor

Or later tonight. 🦉

ilayn pushed a commit that referenced this pull request Jun 14, 2023
…linux (#18677)

* CI: remove setuptools install from musllinux job

No longer used/needed, since we removed the need for it from Pythran.

* TST: improve seeding of problematic linalg tests + add `IS_MUSL`

These tests crash in a quite flaky way, as seen in gh-18671 and
previously also in gh-17630. So to make sure it's not due to
test ordering, avoid use of the global RandomState instance.
Copy link
Contributor

@mdhaber mdhaber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please consider tylerjereddy#73.

@jjerphan
Copy link
Contributor

I just opened tylerjereddy#74.

@tylerjereddy
Copy link
Contributor Author

Copy link
Member

@rgommers rgommers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM and CI is green modulo 3 unrelated failures, so good to go I'd say. I'd recommend either squash-merging this though or (preferably) squashing the ~10 separate commits that tweak the release notes entry for sparse array stuff.

tylerjereddy and others added 3 commits June 15, 2023 20:25
* update the SciPy 1.11.0rc2 release notes
following additional backports

DOC: suggestions for `scipy.sparse` release notes

Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>

Reword some sentences

Remove mentions of n-dimensional sparse arrays

Apply suggestions from code review

DOC: update release notes for scipy.stats

DOC: PR 18671 revisions

* remove `diags_array` from release notes per scipygh-18599

DOC: PR 18671 revisions

* update release notes after more activity
* release notes updates after another backport
to 1.11.0rc2 PR
@tylerjereddy
Copy link
Contributor Author

squashing the ~10 separate commits that tweak the release notes entry for sparse array stuff.

  • I took note of the status of the PR before the interactive rebasing adventure: 27 commits, +169 −158
  • then after doing the squasing/merge conflict resolution the PR now shows: 17 commits, +169 −158

That looks about right I think, a bit unfortunate that a backport got interwoven or I could have condensed even more, but that's a reduction by 10.

@rgommers
Copy link
Member

LGTM now, thanks @tylerjereddy. In it goes. The hang on CirrusCI is unrelated; there's one doc warning which seems to be due to a new version of Matplotlib. That's not blocking for the release, let's deal with that in main.

@rgommers rgommers merged commit a41ac77 into scipy:maintenance/1.11.x Jun 16, 2023
17 of 18 checks passed
@tylerjereddy tylerjereddy deleted the treddy_1_11_rc2_prep branch June 16, 2023 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet