-
Notifications
You must be signed in to change notification settings - Fork 36
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
Figure out and fix failing CI test for udunits. #50
Comments
The failing build is udunits with clang on macOS. |
Do you think there's any relation to NOAA-EMC/NCEPLIBS-external#85? Maybe the common factor is Xcode 12? |
I think so @kgerheiser. Xcode 12 might be exposing a bug in udunits. |
You should also contact unidata or at least post on udunits issues list. Do not assume that someone is actively maintaining this - I'm not sure anyone is. |
@aerorahul I think just turning off udunits is not a great fix for this. Do you plan on fixing it further? If udunits is not a critical package, why are we building it at all? |
I cannot fix it without UDUNITS group on fixing it. It is used in JEDI as an optional package. |
Did you open an issue with udunits group? Are they planning in fixing it? If so, when? If not, can you submit a PR to udunits with a fix? |
For reference, this is the build log for udunits and clang
|
Issue opened at Udunits |
fixed by updating udunits. |
Describe the bug
The udunits CI test on macOS is failing.
To Reproduce
Create a branch and push. This will trigger the CI.
Watch it fail.
Expected behavior
The test should have passed.
System:
Have not experienced this bug on any of the systems we are currently running on.
Additional context
Issue has been opened with udunits at Unidata/UDUNITS-2#97
The text was updated successfully, but these errors were encountered: