Skip to content
GitLab
Projects Groups 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
    • Contributors
    • Graph
    • Compare
  • Issues 855
    • Issues 855
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 55
    • Merge requests 55
  • 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
  • !3131

tests: Release GApplication a little later to avoid assertion failures

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Philip Withnall requested to merge pwithnall/glib:2835-gapplication-test-failure into main Dec 14, 2022
  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 1

If it takes one more GMainContext cycle than expected for the activate signals to be handled, the GApplication under test can be released too early, and the test will fail due to not seeing a high enough value of n_activations.

Hopefully avoid that by moving the release to a low priority idle callback.

This fix is only hopeful because I’ve only been able to reproduce the failure on FreeBSD CI and not locally.

Signed-off-by: Philip Withnall pwithnall@endlessos.org

Fixes: #2835 (closed)

Closes #2835 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: 2835-gapplication-test-failure