-
Notifications
You must be signed in to change notification settings - Fork 90
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
Generate BOUT++ tar via boutpp backend #2708
Conversation
#2709 fixes the failures |
* master: Update src/solver/impls/snes/snes.cxx Update src/solver/impls/snes/snes.cxx Update src/solver/impls/snes/snes.cxx Ensure we can compile PETSc Remove unchecked petsc_test_runs Remove _TEST_ variables Set PETSc options before initialize beuler: Recalculate Jacobian on solver failure snes solver: Check if PETSc has Hypre Apply clang-format changes Solver documentation cvode solver: Add linear and nonlinear convergence options beuler: Fix stencils, pre-allocation and hypre defaults Get mesh outputs after physics init Apply clang-format changes The additional check is not needed Fix findPetsc.cmake remove more unused code Do not run PETSc and SLEPc in cmake step
@@ -166,6 +173,10 @@ def build_sdist(sdist_directory, config_settings=None): | |||
enable_xz = True | |||
else: | |||
raise ValueError(f"unknown option {v} for {k}") | |||
if k == "dist": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might make sense to use something like argparse
for this in a future version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably, but I was lazy 🙈
The new PETSc test failed only on this branch with some |
Yes, it seems they use different CPUs, and with a bit of bad luck you
get the old ones, so the cached SLEPc (I assume they add -march=native)
fail sometimes. Seen that before, triggering a rerun solves the issue.
…On 6/14/23 18:52, Peter Hill wrote:
The new PETSc test failed only on this branch with some |Illegal
instruction| -- @dschwoerer <https://github.com/dschwoerer> did you
encounter this recently somewhere else?
—
Reply to this email directly, view it on GitHub
<#2708 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLAMHW6TPNNTAWSKH3VD53XLHT4FANCNFSM6AAAAAAXSYJHJY>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Any idea if we can turn that flag off?
…On Wed, 14 Jun 2023, 20:12 David Bold, ***@***.***> wrote:
Yes, it seems they use different CPUs, and with a bit of bad luck you
get the old ones, so the cached SLEPc (I assume they add -march=native)
fail sometimes. Seen that before, triggering a rerun solves the issue.
On 6/14/23 18:52, Peter Hill wrote:
> The new PETSc test failed only on this branch with some |Illegal
> instruction| -- @dschwoerer <https://github.com/dschwoerer> did you
> encounter this recently somewhere else?
>
> —
> Reply to this email directly, view it on GitHub
> <
#2708 (comment)>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/ABLAMHW6TPNNTAWSKH3VD53XLHT4FANCNFSM6AAAAAAXSYJHJY
>.
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#2708 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALLAXS4Q45OFOCK5KN2353XLIEH7ANCNFSM6AAAAAAXSYJHJY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Co-authored-by: Peter Hill <peter.hill@york.ac.uk>
Fixed - I copy pasted from our instructions, but |
Allows to drop a bash script for a python script, that we anyway need to maintain (and regularly use)