Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
vidjil
vidjil
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,696
    • Issues 1,696
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 89
    • Merge Requests 89
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • vidjil
  • vidjilvidjil
  • Issues
  • #3117

Closed
Open
Opened Apr 04, 2018 by Mathieu Giraud@magiraudOwner

should --retry

Depuis #3033 (closed), on affiche les tests loupés, ce qui est prêt à copier-coller pour relancer.

On pourrait avoir plus simplement la commande should --retry qui relance ces tests (avec les mêmes dernières options passées à should). Cela demande d'avoir quelque part un should.log avec ces tests stockés de manière re-parsable.

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