GHC issueshttps://gitlab.haskell.org/ghc/ghc/-/issues2021-12-23T08:55:15Zhttps://gitlab.haskell.org/ghc/ghc/-/issues/20032Make a separate test package for reqlib tests which is run by head.hackage2021-12-23T08:55:15ZMatthew PickeringMake a separate test package for reqlib tests which is run by head.hackageTODOTODO⊥Matthew PickeringMatthew Pickeringhttps://gitlab.haskell.org/ghc/ghc/-/issues/16787Terminal title is not reset after running the test suite2019-07-07T18:00:03ZÖmer Sinan AğacanTerminal title is not reset after running the test suite# Summary
5cf8032e2fd2a2f35b8de9016c6e38e92c524394 implemented updating the terminal title while running the tests. The problem is it doesn't reset the title, so after running the test suite once I see the last test run in the title for...# Summary
5cf8032e2fd2a2f35b8de9016c6e38e92c524394 implemented updating the terminal title while running the tests. The problem is it doesn't reset the title, so after running the test suite once I see the last test run in the title forever.
# Steps to reproduce
Just run any test and check the terminal title.
# Expected behavior
Terminal title should be reset after the tests finish.
# Environment
* GHC version used: HEAD
Optional:
* Operating System:
* System Architecture:⊥https://gitlab.haskell.org/ghc/ghc/-/issues/5024Improve testsuite summary output2019-07-07T18:57:17ZIan Lynagh <igloo@earth.li>Improve testsuite summary outputSuggested in http://www.haskell.org/pipermail/cvs-ghc/2011-February/060071.html
The testsuite should say what directory test failures are in, and what sort of failure it was ("run.stderr mismatch", "timeout", "expected exit(0) but saw 1...Suggested in http://www.haskell.org/pipermail/cvs-ghc/2011-February/060071.html
The testsuite should say what directory test failures are in, and what sort of failure it was ("run.stderr mismatch", "timeout", "expected exit(0) but saw 139", etc).
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | -------------- |
| Version | 7.0.2 |
| Type | FeatureRequest |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Test Suite |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | |
</details>
<!-- {"blocked_by":[],"summary":"Improve testsuite summary output","status":"New","operating_system":"","component":"Test Suite","related":[],"milestone":"⊥","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"7.0.2","keywords":[],"differentials":[],"test_case":"","architecture":"","cc":[""],"type":"FeatureRequest","description":"Suggested in http://www.haskell.org/pipermail/cvs-ghc/2011-February/060071.html\r\n\r\nThe testsuite should say what directory test failures are in, and what sort of failure it was (\"run.stderr mismatch\", \"timeout\", \"expected exit(0) but saw 139\", etc).\r\n","type_of_failure":"OtherFailure","blocking":[]} -->⊥