Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

make coverage.html; make coverage-report fails

See original GitHub issue

make coverage.html 
make coverage-report fails

these commands fail due to the following error:

Finished processing dependencies for cwltool==1.0.20170309164828
export COVERAGE_PROCESS_START=/home/manu/github/cwltool/.coveragerc; \
       cd ; ./run_test.sh RUNNER=cwltool
/bin/sh: 2: ./run_test.sh: not found
Makefile:110: recipe for target '.coverage' failed
make: *** [.coverage] Error 127

related line of code in makefile: https://github.com/common-workflow-language/cwltool/blob/master/Makefile#L111

Issue Analytics

State:
Created 7 years ago
Comments:22 (22 by maintainers)

Top GitHub Comments

1reaction

manu-chromacommented, Aug 14, 2017

@mr-c Working now. Need to remove hardcoded paths though

(venv) manu@hp:~/.../cwltool/common-workflow-language$ coverage report --omit="*/site-packages/*","*/schema_salad/*"
Name                                                         Stmts   Miss  Cover
--------------------------------------------------------------------------------
/home/manu/github/cwltool/cwltool.py                             5      0   100%
/home/manu/github/cwltool/cwltool/__init__.py                    2      0   100%
/home/manu/github/cwltool/cwltool/builder.py                   190    163    14%
/home/manu/github/cwltool/cwltool/cwlrdf.py                     84     71    15%
/home/manu/github/cwltool/cwltool/docker.py                     99     85    14%
/home/manu/github/cwltool/cwltool/docker_id.py                  46     32    30%
/home/manu/github/cwltool/cwltool/draft2tool.py                476    424    11%
/home/manu/github/cwltool/cwltool/errors.py                      4      0   100%
/home/manu/github/cwltool/cwltool/expression.py                174    144    17%
/home/manu/github/cwltool/cwltool/flatten.py                    19     16    16%
/home/manu/github/cwltool/cwltool/job.py                       314    274    13%
/home/manu/github/cwltool/cwltool/load_tool.py                 151    124    18%
/home/manu/github/cwltool/cwltool/main.py                      560    395    29%
/home/manu/github/cwltool/cwltool/mutation.py                   37     25    32%
/home/manu/github/cwltool/cwltool/pack.py                      125    112    10%
/home/manu/github/cwltool/cwltool/pathmapper.py                175    135    23%
/home/manu/github/cwltool/cwltool/process.py                   548    466    15%
/home/manu/github/cwltool/cwltool/resolver.py                   40     30    25%
/home/manu/github/cwltool/cwltool/sandboxjs.py                 211    185    12%
/home/manu/github/cwltool/cwltool/software_requirements.py      74     53    28%
/home/manu/github/cwltool/cwltool/stdfsaccess.py                51     25    51%
/home/manu/github/cwltool/cwltool/update.py                    377    329    13%
/home/manu/github/cwltool/cwltool/utils.py                     104     84    19%
/home/manu/github/cwltool/cwltool/workflow.py                  635    575     9%
--------------------------------------------------------------------------------
TOTAL                                                         4501   3747    17%

1reaction

manu-chromacommented, Mar 22, 2017

In summary, please don’t use the conformance tests inside cwltool/cwltool/schemas as they are out of date 😃

@mr-c thanks for pointing this out. I was using them yesterday while debugging my PR: https://github.com/common-workflow-language/cwltool/pull/337

Yes, we should explain how to run the conformance tests in the README – PR gladly accepted

I’m thinking of adding short description on running tox locally. And adding essential contents from https://github.com/common-workflow-language/cwltool/blob/master/cwltool/schemas/CONFORMANCE_TESTS.md

Top Results From Across the Web

Code Coverage report fails to load index.html

Hi! In my latests builds, although Publish Code Coverage task ends successfully and artifacts are being published (I'm even able to download them), ......

Not able to generate ".coverage" report while running code ...

I'm trying to run code coverage testing from command line using below commands: vstest.console.exe CoverTest.dll /EnableCodeCoverage ...

Command line usage — Coverage.py 6.4.4 documentation

html – Produce annotated HTML listings with coverage results. ... --data-file=OUTFILE Write the recorded coverage data to this file. Defaults to '.coverage' ...

python coverage error during html report (NoSource

I encounter the following error during reporting html coverage. myrepo>coverage report html html NoSource: No source for code: ...

About Code Coverage

Please make sure to enable preview packages in the Package Manager, otherwise it won't be listed. Coverage HTML Report. Shown below is an...