Automatic report discovery failing on Windows environment.
See original GitHub issueWhen trying to discover reports automatically on AppVeyor I get the following error on the FIND command:
FIND: Parameter format not correct
child_process.js:1389
throw err;
^
Error: Command failed: find . -type f \( -name '*coverage.*' -or -name 'nosetests.xml' -or -name 'jacoco*.xml' -or -name 'clover.xml' -or -name 'report.xml' -or -name 'cobertura.xml' -or -name 'luacov.report.out' -or -name 'lcov.info' -or -name '*.lcov' -or -name 'gcov.info' -or -name '*.gcov' -or -name '*.lst' \) -not -name '*.sh' -not -name '*.data' -not -name '*.py' -not -name '*.class' -not -name '*.xcconfig' -not -name 'Coverage.profdata' -not -name 'phpunit-code-coverage.xml' -not -name 'coverage.serialized' -not -name '*.pyc' -not -name '*.cfg' -not -name '*.egg' -not -name '*.whl' -not -name '*.html' -not -name '*.js' -not -name '*.cpp' -not -name 'coverage.jade' -not -name 'include.lst' -not -name 'inputFiles.lst' -not -name 'createdFiles.lst' -not -name 'coverage.html' -not -name 'scoverage.measurements.*' -not -name 'test_*_coverage.txt' -not -path '*/vendor/*' -not -path '*/htmlcov/*' -not -path '*/home/cainus/*' -not -path '*/virtualenv/*' -not -path '*/js/generated/coverage/*' -not -path '*/.virtualenv/*' -not -path '*/virtualenvs/*' -not -path '*/.virtualenvs/*' -not -path '*/.env/*' -not -path '*/.envs/*' -not -path '*/env/*' -not -path '*/envs/*' -not -path '*/.venv/*' -not -path '*/.venvs/*' -not -path '*/venv/*' -not -path '*/venvs/*' -not -path '*/.git/*' -not -path '*/.hg/*' -not -path '*/.tox/*' -not -path '*/__pycache__/*' -not -path '*/.egg-info*' -not -path '*/$bower_components/*' -not -path '*/node_modules/*' -not -path '*/conftest_*.c.gcov'
FIND: Parameter format not correct
at checkExecSyncError (child_process.js:1346:13)
at execSync (child_process.js:1386:13)
at Object.upload (C:\projects\test-codecov\node_modules\codecov\lib\codecov.js:260:18)
at Object.<anonymous> (C:\projects\test-codecov\node_modules\codecov\bin\codecov:24:9)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
AppVeyor runs in a Windows environment and I can see in the source that the module uses cat
and the syntax of find
is *nix style. Is this testet on a Windows environment?
I have not been able to get the windows shell to find any files with the syntax used in the search of reports.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:7
- Comments:8
Top Results From Across the Web
Report for failed Windows Discovery in SNOW - ServiceNow
I am currently trying to pull out a report for windows discovery failure in SNOW which needs to be run by EOD everyday...
Read more >Troubleshooting Cloud Discovery errors - Microsoft Learn
Log collector errors · 1. Check to see if there are failed parsing tasks in the Governance log. · 2. If not, check...
Read more >Troubleshoot ongoing server discovery, software inventory ...
9012: The file containing the discovered metadata on the server is empty. This issue could be transient because of an internal error. The...
Read more >Troubleshoot SQL Server database discovery - Microsoft Learn
Describes how to diagnose and fix SQL Server database discovery issue in System Center 2012 Operations Manager and later versions.
Read more >Troubleshoot hybrid Azure AD-joined devices - Microsoft Learn
This article helps you troubleshoot hybrid Azure Active Directory-joined Windows 10 and Windows Server 2016 devices.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@eddiemoore This is still an issue. You are still using a Unix specific command for file discovery as mentioned in the initial issue description: https://github.com/codecov/codecov-node/blob/master/lib/codecov.js#L224
As proposed in #12 you should do this with something like
globby
instead as this is cross platform.I’ve set up a minimal project for testing here: https://github.com/Crevil/test-codecov And an AppVeyor (Windows) build here: https://ci.appveyor.com/project/Crevil/test-codecov-mgdew
I just hit this issue. Too bad it was closed.