tweag/asterius

Rerun the OOM `ghc-testsuite` tests individually

Open

#284 opened on Sep 15, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Haskell (56 forks)batch import
P2good first issuetype: bug

Repository metrics

Stars
 (1,949 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Currently, we run ghc-testsuite on CI with -j2 to speed things up. This also means less available memory to individual tests, so for some tests which require much memory or when the yolo mode is on, non-deterministic OOM failures do occur.

The simplest solution is simply removing -j2, but we don't want the CI pipeline to extend for another couple of hours; we should only rerun the individual tests after OOM failure.

Contributor guide

Research direction
Locate the CI script (e.g., `.github/workflows/ci.yml`) where the `ghc testsuite` is invoked with ` j2`. Then implement a wrapper that reruns a failing test individually when it fails due to OOM.
Tech stack
haskell
Domain
testing qa
Issue type
DevOps
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitCI/CD concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75