Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
G
GLib
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 937
    • Issues 937
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 54
    • Merge Requests 54
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • GLib
  • Merge Requests
  • !2035

Merged
Created Apr 07, 2021 by Philip Withnall@pwithnallMaintainer

Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68

  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 1

When using TAP we want every single line to be one of the following:

  • a valid TAP clause
  • a comment
  • a blank line

Typical explicit test logs are single line comments, but in some cases we might end up printing debug messages from libraries, and those may contain multiple lines. When that happens, we break the TAP and fail the test in conditions entirely outside of our control.

One option to avoid outright failure is to always prepend each line of a messge with #, to ensure that the whole thing is considered a comment.


Trivial backport of !2026 (merged).

Assignee
Assign to
Reviewer
Request review from
2.68.1
Milestone
2.68.1 (Past due)
Assign milestone
Time tracking
Source branch: backport-2026-log-lines-glib-2-68