Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • T telepathy-gabble
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 289
    • Issues 289
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TelepathyTelepathy
  • telepathy-gabble
  • Issues
  • #256
Closed
Open
Issue created Jun 03, 2013 by Bugzilla Migration User@bugzilla-migration

tests will fail with Automake 1.13

Submitted by Simon McVittie

Assigned to Simon McVittie

Link to original bug (#65290)

Description

Automake 1.12 introduces a new parallel "test driver" and Automake 1.13 makes it the default.

Unfortunately, this is a compatibility break for projects like telepathy-gabble, telepathy-mission-control, telepathy-haze and telepathy-salut that relied on being able to do obscure tricks with the check-TESTS target and TESTS_ENVIRONMENT. We can't even switch back to the old test driver without a dependency on Automake 1.12.

For telepathy-gabble, the quickest way to get tests passing again seems to be to adapt run-tests.sh so it can be used to run installed tests as well as uninstalled ones, and use that instead of playing with check-TESTS.

Later, we could consider providing our own "test driver". I think we would still have to run the tests serially, because they all listen on the same TCP port, unless we can adapt the framework to have them listen on a dynamic port (and somehow avoid the port used by the test that is meant to connect to a wrong port and fail).

Depends on

  • Bug 65131
Assignee
Assign to
Time tracking