You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 29, 2024. It is now read-only.
[phabricator:process-build-result] No line coverage found, skipping...
[phabricator:process-build-result] No coverage provider available.
[phabricator:file-fetcher] no files found by path: '.phabricator-lint'
[phabricator:harbormaster] Sending Harbormaster RUN_DISPLAY_URL via PHID: PHID-HMBT-5fmffgo4b7rm5de5nie6
[phabricator:process-build-result] Publishing unit results to Harbormaster for 162 tests.
[phabricator:process-build-result] Sending build result to Harbormaster with PHID PHID-HMBT-5fmffgo4b7rm5de5nie6, success: false
I am producing a report named coverage-cobertura.xml using lcov+lcov_cobertura.
Now phabricator-jenkins-plugin can see there is a Cobertura result, but does not process it:
14:53:23 [phabricator:uberalls] Using coverage metrics from Cobertura Jenkins Plugin
14:53:23 [phabricator:process-build-result] No line coverage available to post to Harbormaster.
14:53:23 [phabricator:harbormaster] Sending Harbormaster BUILD_URL via PHID: PHID-HMBT-3igswi54yvbltbttvold
14:53:24 [phabricator:process-build-result] Publishing unit results to Harbormaster for 8 tests.
14:53:24 [phabricator:process-build-result] Sending build result to Harbormaster with PHID PHID-HMBT-3igswi54yvbltbttvold, success: true
14:53:25 [phabricator:file-fetcher] no file configured
I think you have to rename your coverage file to coverage-xxx.xml, it not the case. The pattern of file is hardcoded in the plugin code.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Has anyone gotten coverage information out from Jenkinsfile? I always get this:
but after that
I'm calling cobertura like
and Phabricator plugin like
Any ideas what I'm doing wrong?
The text was updated successfully, but these errors were encountered: