Closed sadielbartholomew closed 2 years ago
Opening and closing to re-trigger the CI jobs...
Merging #39 (ccf5d0d) into master (fb7982a) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #39 +/- ##
=======================================
Coverage 81.10% 81.10%
=======================================
Files 2 2
Lines 677 677
=======================================
Hits 549 549
Misses 128 128
Flag | Coverage Δ | |
---|---|---|
unittests | 81.10% <ø> (ø) |
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update fb7982a...ccf5d0d. Read the comment docs.
And again...
OK the issue remains whatever cftime we use, so setuptools
needs to be updated for the Ubuntu 18.04 job, though when I try that manually I get a different error:
Running setup.py install for cftime: started
Running setup.py install for cftime: finished with status 'error'
Complete output from command /usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-995k8piz/cftime/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-gvnwd773-record/install-record.txt --single-version-externally-managed --compile --user --prefix=:
running install
/home/runner/.local/lib/python3.6/site-packages/setuptools/command/install.py:37: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
setuptools.SetuptoolsDeprecationWarning,
So not entirely sure what to do here. Let me try grabbing a later setuptools
from pip
, which is not ideal but I can't see what else can be done...
Open-close to re-trigger again...
OK updating setuptools
via pip
also doesn't work, and since I don't have time to debug this, for the sake of progress I will comment out the Ubuntu 18.04 dist-only run for now and create an issue to reinstate it when we know how.
We already test that cfunits can run via conda installations on that dist anyway, so we already have a good coverage of installation testing on the CI.
I won't squash all of these commits together like I ordinarily would because they each show a solution I tried and that failed to get the cftime
distribution to build given the older default setuptools
, which will be useful to reference when we do get onto resolving the underlying issue.
Ultimately this PR now comments out the relevant lines to stop the Ubuntu 18.04 dist. job (only) from the un-test-suite_ubuntu_default_packages.yml
workflow. I will merge it now and open the issue.
Working out a solution, and testing it via re-running the CI jobs, to bypass or fix the
setup.py bdist_wheel
build ofcftime
which fails for the Ubuntu 18.04 (only, i.e. not 20.04 too) distribution job. It seems to occur becausedistutils
ends up being run, and that is old enough that it doesn't recognise a(t least one) metadata key in thecftime
v.1.5.0setup.py
(namely"long_description_content_type"
).Details
Specifically, the Actions log produced the following output: