diff options
| author | silverwind <me@silverwind.io> | 2022-08-12 22:13:31 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-12 16:13:31 -0400 |
| commit | 74515d3d17c578ee0083111951188cb159fd049b (patch) | |
| tree | 6aad8e94e2698f3b9b56dfd980bff2edb15755c2 | |
| parent | d30e02255f531200e57735b8b69fa389cbfad97a (diff) | |
| download | gitea-74515d3d17c578ee0083111951188cb159fd049b.tar.gz gitea-74515d3d17c578ee0083111951188cb159fd049b.zip | |
Remove debug output when coverage fails (#20733)
* Remove debug output when coverage fails
When coverage fails, it logs megabytes of debug to stdout, which seems
to break the drone ui as well as the log output download in drone,
presumably because of the size. I think with removal of this print, we
should still see any errors created by gocovmerge.go, but a few CI runs
may be necessary to get it to fail again.
* Update Makefile
* restart ci
* restart ci
* restart ci
* restart ci
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
| -rw-r--r-- | Makefile | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -364,7 +364,7 @@ test\#%: coverage: grep '^\(mode: .*\)\|\(.*:[0-9]\+\.[0-9]\+,[0-9]\+\.[0-9]\+ [0-9]\+ [0-9]\+\)$$' coverage.out > coverage-bodged.out grep '^\(mode: .*\)\|\(.*:[0-9]\+\.[0-9]\+,[0-9]\+\.[0-9]\+ [0-9]\+ [0-9]\+\)$$' integration.coverage.out > integration.coverage-bodged.out - $(GO) run build/gocovmerge.go integration.coverage-bodged.out coverage-bodged.out > coverage.all || (echo "gocovmerge failed"; echo "integration.coverage.out"; cat integration.coverage.out; echo "coverage.out"; cat coverage.out; exit 1) + $(GO) run build/gocovmerge.go integration.coverage-bodged.out coverage-bodged.out > coverage.all .PHONY: unit-test-coverage unit-test-coverage: |