Sort of similar to #3508. We have a project with many packages and test suites, some of which are very quick unit tests and some of which are long integration tests. When doing a full build +test (especially for newcomers to the project, the natural thing is to do something like stack build --test after getting the repository), the whole thing just looks like it's hanging when it's running the tests. In reality, nearly all tests have completed almost immediately but there are some long ones which don't. So we see e.g.
> stack test
long-tests-0.1.0.0: configure (test)
short-tests-0.1.0.0: configure (test)
long-tests-0.1.0.0: build (test)
long-tests-0.1.0.0: test (suite: long-test-suite)
short-tests-0.1.0.0: build (test)
short-tests-0.1.0.0: test (suite: short-test-suite)
with no indication of which one is hanging. A notification of a test suite completing would help to diagnose this. The situation is a bit better with just builds, but the copy/register line indicates when a particular build is finished.
I can submit a pull request if you think this is an appropriate change, looks simple enough - just adding another call to announce in Stack.Build.Execute.singleTest.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4