Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • H head.hackage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell Compiler
  • head.hackage
  • Issues
  • #28
Closed
Open
Created Jan 27, 2021 by Ryan Scott@RyanGlScottMaintainer

CI consistently fails on gitlab-ci-linux-x86-64-2 runner (but not others)

Every time a head.hackage CI job is assigned to the gitlab-ci-linux-x86-64-2 runner, it will fail with the following error message (example):

$ nix-build ./ci -j$CPUS --no-build-output # collapsed multi-line command
error: configuration setting 'max-jobs' should be 'auto' or an integer
Try 'nix-build --help' for more information.

It appears that $CPUS isn't being expanded for some reason. Other runners do not appear to suffer from this issue, so a workaround is to restart the job and pray that it isn't assigned to gitlab-ci-linux-x86-64-2. This is tedious, however, and shouldn't be necessary.

Assignee
Assign to
Time tracking