Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.core beat.core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.corebeat.core
  • Issues
  • #108
Closed
Open
Issue created Feb 23, 2022 by Samuel GAIST@samuel.gaistOwner

Nightlies are failing for several reasons

The nightlies are currently failing for several unrelated reasons:

  • Looks like some keys have gone missing
  • Some tests cannot be run because of database environment missing.

The first one is likely related to the use of cgroup v2 based on the name of the fields missing and the information given on the Container Stats information for the Docker v1.41 API.

As for the database environments, the likely reasons is that all the runners and test machines had previous versions of the database images and thus the tests were run successfully although the test image pull method used later versions of them.

Assignee
Assign to
Time tracking