Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
purr-data
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 147
    • Issues 147
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #504

Closed
Open
Opened Jan 31, 2019 by Jonathan Wilkes@jwilkes
  • Report abuse
  • New issue
Report abuse New issue

attempt to upgrade OSX runner and use valgrind with it

Go ahead and try to upgrade OSX runner to mojave.

If it works, try making valgrind a requirement in the CI instructions. Then track down any memory errors that valgrind catches.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: jwilkes/purr-data#504