Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
S
should
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • 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
  • vidjil
  • should
  • Issues
  • #23

Closed
Open
Opened Oct 31, 2018 by Mikaël Salson@mikael-sOwner

should.py doesn't timeout with launcher

On current version of Vidjil just launch: python3 should.py --launcher 'valgrind --tool=memcheck --leak-check=full --show-reachable=yes --trace-children=yes' should-get-tests/stanford-germlines.should-get

Valgrind produces lots of output (see #19 (closed)) and should.py hangs.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
2.0.0
Milestone
2.0.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: vidjil/should#23