Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-devtools gst-devtools
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 35
    • Issues 35
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • 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
  • GStreamerGStreamer
  • gst-devtoolsgst-devtools
  • Issues
  • #52
Closed
Open
Issue created Jun 02, 2020 by Edward Hervey@bilboed🤘Owner

Don't copy massive gstdebug file contents into summary markdown

There should be an option to NOT copy over the gstdebug file into the resulting markdown. When using high debugging levels copying over GBs of content takes more time than running the actual tests (and saturate local storage with redundant data).

Or better yet, if it exceeds a certain threshold (say 1MB), don't ever copy it and instead use a link to it.

Assignee
Assign to
Time tracking