Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • G GLib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 853
    • Issues 853
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 43
    • Merge requests 43
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • GLib
  • Merge requests
  • !3108

gwakeuptest: Do not rely on alarm() to stop tests on timeout

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Marco Trevisan requested to merge 3v1n0/glib:gwakeup-cleanups into main Dec 06, 2022
  • Overview 2
  • Commits 2
  • Pipelines 3
  • Changes 2

Some cleanups while trying to figure out why those tests are flacky in CI (but I wasn't ever able to get a failure locally).

We have meson nowadays, so tests are timing out by default and test timeout may vary depending on the meson test parameters or test setups.

So don't hardcode it using alarm().

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: gwakeup-cleanups