Skip to content

GitLab

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

Closed
Open
Opened 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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: jwilkes/purr-data#666