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
  • #19

Closed
Open
Opened Jul 19, 2018 by Mikaël Salson@mikael-sOwner

Timeout with large outputs

When the output (either on stdout or stderr) is quite large the test systematically timeouts.

Here is a simple example:

# Displays 65,537 random ACGT
cat /dev/urandom | tr -dc ACGT | head -c 65537

rwl65537: [ACGT] 

There is no timeout for 65,536 characters (hmm… this value reminds me of something…)

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#19