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

Test on 1.9 instead of 1.6 #733

Merged
merged 3 commits into from
Nov 21, 2023
Merged

Test on 1.9 instead of 1.6 #733

merged 3 commits into from
Nov 21, 2023

Conversation

TorkelE
Copy link
Member

@TorkelE TorkelE commented Nov 21, 2023

No description provided.

@isaacsas
Copy link
Member

If everything passes feel free to merge.

@isaacsas
Copy link
Member

Oh, you also need to update Julia to 1.9 in the Project.toml.

@isaacsas
Copy link
Member

@TorkelE nonlinear solve tests are failing...

@TorkelE
Copy link
Member Author

TorkelE commented Nov 21, 2023

Yeah, I am not sure if it is related to #728, Avik said that looked strange

@isaacsas
Copy link
Member

The error comes from the first let block in the nonlinear solve tests. If I manually run that code I get the error, but then if I rerun it everything works fine.

@TorkelE
Copy link
Member Author

TorkelE commented Nov 21, 2023

Just running the block on my computer it is fine, and #721 passed as well. I still think it must have been something with that compact update that was added in.

@TorkelE
Copy link
Member Author

TorkelE commented Nov 21, 2023

The only otehr alternatvie I can come up with is that StableRNGs have started generating some other rnd number, and this one somehow is problmatic.

@TorkelE
Copy link
Member Author

TorkelE commented Nov 21, 2023

Ok, I had another chat with Avik, we now have a test that NonlinearSolve should solve stabily.

@isaacsas
Copy link
Member

Great, maybe just make the changes in this PR? Then we can merge this and hopefully get CI fixed.

@TorkelE
Copy link
Member Author

TorkelE commented Nov 21, 2023

done, yeah, hopefully, this shoudl settle things. Should I try rebase the other PRs (that currently fail 1.6) on master afterwards?

@TorkelE TorkelE merged commit 5b6efd3 into master Nov 21, 2023
6 of 9 checks passed
@isaacsas
Copy link
Member

Yes, start updating your PRs as we merge stuff in.

@isaacsas isaacsas deleted the 1.6_to_1.9 branch November 21, 2023 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants