Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 2
    • Merge requests 2
  • Requirements
    • Requirements
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #31437

Closed
Open
Created Apr 26, 2017 by Rémy Coutable@rymaiMaintainer

Transient failure in `features/project/merge_requests.feature:312`

As seen in https://gitlab.com/gitlab-org/gitlab-ce/builds/15020376.

It seems that we check that the record is closed before asserting something one the page, meaning that if the closing takes longer than expected, the first assertion fails. We should get rid of the first assertion since feature specs shouldn't assert underlying DB data.

See the screenshot that confirms this:

screenshot_2017-04-25-21-17-13.500

Assignee
Assign to
Time tracking