Clean up the library testing story
Our story for testing libraries is in disarray, and needs cleaning up. Tests for libraries can now be placed in the repositories with the libraries themselves, and these tests are picked up when you say make in testsuite/tests/ghc-regress.
The following tests need to be moved into their respective packages, and in some cases given appropriate .T scripts:
- everything in
testsuite/tests/libraries - everything in
testsuite/tests/ghc-regress/lib
tests that are package-specific but are really GHC regression tests should stay in the testsuite, and use the reqlib option.
Trac metadata
| Trac field | Value |
|---|---|
| Version | 6.7 |
| Type | Task |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Test Suite |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Unknown |
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information