Open awasthishubh opened 4 years ago
I think there are two independent questions here. The test stuff can at least get rum from the test
command. Even without that though, the build-summary
and build-log
don't seem to get generated at all from my experiments? What's the correct way to get them in v2?
@jneira could you comment on the label “not our bug” (which you added): I don’t quite get why it’s not “our”…
me neither 😅 it was a misclick I suppose, thanks for noting it
Looks similar to #5901.
TIL about --run-tests
; it seems confusing though as the documentation says "Run the package test suite upon installation" but there's no installation if you pass it to cabal build
; it also mentions a hash maybe it means the store? It sounds dangerous to mix up installation with the cabal store as they are different concepts.
Describe the bug I am currently working on updating Hackage builder to cabal v2 as a part of GSoC Project. The objective was to build the package, run tests, create Haddock doc and run code-coverage. I need the report of each of these tasks in the specified files. I tried setting the flags to make cabal write test log, build-summary, logs and docs at the specified location but it doesn't seem to work.
To Reproduce In the root directory of a package (async in this case), I ran the following code.
Expected behavior Specified files must have a log or report content.
System information
Additional context How can we set coverage report, doc tarball location?