-
Can you please demonstrate the issue via a test project on this OneDev instance?
-
Can you please demonstrate the issue via a test project on this OneDev instance?
A demo project with a fake test and some useless php files did not show the problem as the pipeline completes successfully (though without showing a tab with coverage results): https://code.onedev.io/test_project_Issue_OD-2579/~builds/4
I will do another attempt on monday.
-
Never mind. Found the issue.
-
State changed as code fixing the issue is committed (64e83d99)
-
OneDev
changed state to 'Closed' 3 months ago
Previous Value Current Value Open
Closed
-
State changed as build OD-6728 (13.0.9) is successful
-
OneDev
changed state to 'Released' 3 months ago
Previous Value Current Value Closed
Released
-
I can confirm that this fixes the issue. Thank you very much for the quick fix!
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
13.0.6
|
| Labels |
No labels
|
Issue Votes (0)
Hello onedev team, We set up a CI in which phpunit produces unit test coverage data through a clover.xml file. Feeding this into the publish step for clover yields the error "Invalid input stream" in the job log.
Job log:
The onedev server logs show an error and the "caused by" stacktraces seems to be similar to the stacktrace in a recently fixed issue (OD-2318):
The CI yaml file: