Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P polkit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 122
    • Issues 122
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • polkit
  • polkit
  • Issues
  • #161

Closed
Open
Created Oct 28, 2021 by Simon McVittie@smcvContributor

Arbitrary test timeout is too short for polkitbackendjsauthority

From a Debian x86_64 autobuilder log:

1/5 polkitunixusertest            OK              0.01s
2/5 polkitunixgrouptest           OK              0.01s
3/5 polkitunixnetgrouptest        OK              0.01s
4/5 polkitidentitytest            OK              0.01s
5/5 test-polkitbackendjsauthority OK             26.41s

This is uncomfortably close to Meson's 30s default timeout: even on x86, it would only take a small amount of extra load (or a slightly slower CPU?) to make this test time out. On slower CPU architectures like mips and riscv64, it does time out.

It would probably be a good idea to raise this timeout, perhaps to more like 2 minutes.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking