Separate job for tests

ghc-tests were originally tests in GHC's own test suite (not surprising, I guess). They relied on other packages, which made them fragile, so they got moved into head.hackage, where they would always have access to freshly built packages. But at the end of the day, they are GHC tests, unrelated to the question of "Did GHC HEAD break any packages."

Now that the tests are still proving fragile (e.g. ghc#22248, #49), I'd like to let head.hackage pass even if ghc-tests fail. Since we don't have access to the same fragility system in the GHC test suite, I'm going to just split those tests into a separate GitLab job and mark that one allowed-to-fail.

Ideally they just wouldn't be fragile, but in terms of priority I'd rather have CI green first, and then fix fragile tests.

added 1 commit

• e367c283 - Split build and test

Compare with previous version

added 3 commits

• 9a518520 - Prevent duplicate merge request pipelines
• be56dc5e - Mark build tasks as interruptible
• 56d9d913 - CI: Upgrade dependencies to needs

Compare with previous version

added 1 commit

• 80a95b66 - CI: Allow test jobs to fail

Compare with previous version

changed title from WIP: Add BUILD_MODE argument to Separate job for tests

changed the description

added 1 commit

• f1917d23 - Also run tests in QUICK, as before

Compare with previous version

added 8 commits

• a7a158bf - 1 commit from branch master
• fb23c9ec - Add BUILD_MODE argument
• 9958050a - Split build and test
• e61a3c92 - Prevent duplicate merge request pipelines
• db9d57a4 - Mark build tasks as interruptible
• f983657a - CI: Upgrade dependencies to needs
• 0c19134d - CI: Allow test jobs to fail
• 7af92257 - Also run tests in QUICK, as before

Compare with previous version

mentioned in issue ghc#22248

merged