-
Notifications
You must be signed in to change notification settings - Fork 19
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
CI: create test_file.nc
before step to run test suite
#291
CI: create test_file.nc
before step to run test suite
#291
Conversation
Opening and closing to trigger the CI jobs... |
Codecov Report
@@ Coverage Diff @@
## master #291 +/- ##
==========================================
+ Coverage 73.80% 73.90% +0.11%
==========================================
Files 85 88 +3
Lines 19179 19632 +453
==========================================
+ Hits 14153 14507 +354
- Misses 5026 5125 +99
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
The fix applied, which seems to work now for the Now applying the working fix to the |
Re-triggering... |
Again... |
Now the ======================================================================
FAIL: test_relative_vorticity_latlong (test_Maths.MathTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/runner/tmp/test_cf-python/cf/test/test_Maths.py", line 105, in test_relative_vorticity_latlong
self.assertTrue(numpy.allclose(rv.array, rv_array))
AssertionError: False is not true
----------------------------------------------------------------------
Ran 337 tests in 793.486s
FAILED (failures=1) which I will raise elsewhere. So that workflow can be considered done for the purposes of this PR. |
Ditto for the |
Hi Sadie. Ah - that makes sense, and I should have tested for it in #290. The fix there will change the results of relative vorticity calculations. I'll have a look at |
b77e5a2 should fix this for now. The whole vorticity thing needs overhauling, so it's not worth doing a more thorough job at this time. |
A netCDF file for testing on,
test_file.nc
is written out and used by therun_test.py
script that runs the full test suite, and locally this works fine, but for the Actions jobs it is not being recognised, at least within thetest_Field
module:This PR aims to fix this so that the required file is generated by the Actions jobs and available for use by that script (as wrapped by the coverage-checking script), as opposed to committing it permanently to the repo which is a simple solution but is not preferred for various reasons.
Some trial-and-error is anticipated to get this working.