Closed timryanb closed 10 months ago
Merging #414 (a4fa1fc) into main (af05b30) will decrease coverage by
0.01%
. The diff coverage is93.10%
.
@@ Coverage Diff @@
## main #414 +/- ##
==========================================
- Coverage 94.51% 94.50% -0.01%
==========================================
Files 103 103
Lines 6420 6445 +25
==========================================
+ Hits 6068 6091 +23
- Misses 352 354 +2
Files Changed | Coverage Δ | |
---|---|---|
openaerostruct/mphys/aero_builder.py | 86.66% <86.66%> (-0.22%) |
:arrow_down: |
openaerostruct/mphys/utils.py | 100.00% <100.00%> (ø) |
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
Any idea what is going on with PETSc? It's happening in other builds too, so I don't think it's a change caused by this PR. Do you know of any updates to dependencies? I was going to take a look but I haven't had time to get around to it yet.
Other than that, this looks fine to me. I don't know the mphys side of things, so maybe @bernardopacini has some input. If not, we can merge it once the PETSc problem is sorted.
@eytanadler this is likely a problem with Cython 3.0 which was released recently released. There seems to be issue mentioning this on the petsc4py repo: https://gitlab.com/petsc/petsc/-/issues/1423. You might want to try pip installing cython 0.29 before installing petsc4py. We had a similar issue on TACS that @A-CGray discovered, he may have some other ideas
Yeah PETSc4py is the issue here, we fixed this in our docker builds by pip installing "cython<3.0"
. In the longer term though, why don't we just run these actions on one of our docker containers?
@eytanadler I tried making the fix in this PR, but there still seems to be issues with codecov: https://github.com/mdolab/OpenAeroStruct/actions/runs/5681691211/job/15398407295?pr=414
Thanks! For some reason that happens periodically. We tried updating the codecov action to the newest but it doesn't always work. I triggered the tests again to see if it'll work the second time.
@timryanb can you bump the version to 2.7.0 as this PR introduces a new backwards compatible feature. I would do it but can't push to your fork
I'm happy to do so @A-CGray, though the feature should be backwards-compatible (non-breaking) for the record
@eytanadler is it alright to do the version bump in this PR or is it easier to do a new PR dedicated to the bump after this PR?
I'm happy to do so @A-CGray, though the feature should be backwards-compatible (non-breaking) for the record
Yep, that's why I want to bump the minor version and not the major version. I don't think we have a consistent rule for this stuff but I try to follow the semantic versioning rules:
I'm happy to do so @A-CGray, though the feature should be backwards-compatible (non-breaking) for the record
Yep, that's why I want to bump the minor version and not the major version. I don't think we have a consistent rule for this stuff but I try to follow the semantic versioning rules:
Ah sorry, misread the "backwards compatible" comment...
Let's lump the minor version change in with #413. Feel free to update the version number here, but let's not make a new release yet.
Purpose
This is related to https://github.com/OpenMDAO/mphys/pull/158 and https://github.com/smdogroup/funtofem/pull/192 and allows for aerostructural analysis with multiple bodies
Expected time until merged
a week
Type of change
Testing
Checklist
flake8
andblack
to make sure the Python code adheres to PEP-8 and is consistently formattedfprettify
or C/C++ code withclang-format
as applicable