Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Regression] Sometimes after creating a workspace a project is not valid #6353

Closed
SkorikSergey opened this issue Sep 20, 2017 · 6 comments
Closed
Labels
e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@SkorikSergey
Copy link
Contributor

SkorikSergey commented Sep 20, 2017

Reproduction Steps:

  1. Create a workspace with 2 or more projects
  2. Wait while the workspace started

Observed behavior:
Sometimes the project is not valid. Basically this issue is reproduced in ** codenvy **.

Che version: 5.19.0-SNAPSHOT
OS and version: Fedora 25
Failed test: CreateAndDeleteProjectsTest

Additional information:
May be depend on #6344
Problem happens randomly: [Yes]
org eclipse che selenium dashboard createanddeleteprojectstest createanddeleteprojecttest_9lpqazfl
teams-24

@SkorikSergey SkorikSergey added kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. labels Sep 20, 2017
@ghost ghost added severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Sep 20, 2017
@ghost
Copy link

ghost commented Sep 20, 2017

Related to #6075

@SkorikSergey SkorikSergey changed the title Sometimes after creating a workspace a project is not valid [Regression] Sometimes after creating a workspace a project is not valid Sep 20, 2017
@SkorikSergey SkorikSergey added the e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. label Sep 20, 2017
@riuvshin riuvshin added this to the 5.19.0 milestone Sep 20, 2017
@vparfonov vparfonov added team/ide status/in-progress This issue has been taken by an engineer and is under active development. labels Sep 21, 2017
@SkorikSergey
Copy link
Contributor Author

This bug is still reproduced.

@SkorikSergey SkorikSergey reopened this Sep 26, 2017
@ghost
Copy link

ghost commented Sep 26, 2017

@SkorikSergey steps to reproduce please

@vparfonov
Copy link
Contributor

@SkorikSergey
Copy link
Contributor Author

SkorikSergey commented Sep 26, 2017

Reproduction Steps:

  1. Create a workspace with 2 or more projects
  2. Wait while the workspace started
    teams-11-2

Test failed on https://ci.codenvycorp.com/view/qa/job/nightly-onprem-selenium-tests/45/Selenium_tests_report/.

@vparfonov vparfonov removed the status/in-progress This issue has been taken by an engineer and is under active development. label Sep 28, 2017
@SkorikSergey
Copy link
Contributor Author

This issue is still reproduced.

@SkorikSergey SkorikSergey reopened this Oct 4, 2017
@SkorikSergey SkorikSergey added severity/P1 Has a major impact to usage or development of the system. and removed severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Oct 11, 2017
@riuvshin riuvshin removed this from the 5.19.0 milestone Oct 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants