Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P purr-data
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 362
    • Issues 362
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 54
    • Merge requests 54
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #666

Closed
Open
Created Aug 04, 2020 by Sam Thursfield@samthursfieldContributor2 of 3 tasks completed2/3 tasks

ci logs are too long for GitLab CI

git.purrdata.net has a limit of 4194304 bytes for CI logs and this is sometimes exceeded by CI jobs, e.g. https://git.purrdata.net/jwilkes/purr-data/-/jobs/18898 and https://git.purrdata.net/jwilkes/purr-data/-/jobs/18862

Here are some things to investigate to reduce the size of logs:

  • Enable Automake's silent mode so compiler/linker commandlines are only shown when an error occurs
  • fix the many dpkg-shlibdeps warnings that occur
  • modify the tests to only show output when there's a problem (i don't know how the tests work, but maybe it's simple to do)
Edited Sep 17, 2020 by Sam Thursfield
Assignee
Assign to
Time tracking