Skip to content

Test flake: A Jasmine spec timed out. Resetting the WebDriver Control Flow. #2037

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

Closed
spadgett opened this issue Sep 8, 2017 · 6 comments
Closed
Assignees
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1

Comments

@spadgett
Copy link
Member

spadgett commented Sep 8, 2017

Running "protractor:default" (protractor) task
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://172.18.6.105:32806/wd/hub
Spec started
visiting url: create-project
A Jasmine spec timed out. Resetting the WebDriver Control Flow.
The last active task was: 
unknown

visiting url: create-project
A Jasmine spec timed out. Resetting the WebDriver Control Flow.
The last active task was: 
unknown
visiting url: create-project
A Jasmine spec timed out. Resetting the WebDriver Control Flow.
The last active task was: 
unknown

/data/src/github.com/openshift/origin-web-console/node_modules/selenium-webdriver/lib/webdriver/promise.js:1654
      var result = fn();
                   ^
Error: Wait timed out after 5046ms

https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin_web_console/151

@spadgett
Copy link
Member Author

spadgett commented Sep 8, 2017

@spadgett
Copy link
Member Author

spadgett commented Sep 8, 2017

The screenshots show the tests stuck on the login page. This is similar to what we were seeing on the mac.

cc @benjaminapetersen

@spadgett
Copy link
Member Author

The CORS headers are missing from discovery responses. This is what is breaking the integration tests.

@liggitt @deads2k FYI

screen shot 2017-09-11 at 7 39 02 am

@spadgett
Copy link
Member Author

Seems to be any request, not just discovery.

With oc cluster up --version=latest:

$ curl 'https://127.0.0.1:8443/oapi/v1/projects' -i -H 'Origin: https://localhost:9000' -H 'authorization: Bearer <token>' -H 'accept: application/json'
HTTP/1.1 200 OK
Cache-Control: no-store
Content-Type: application/json
Date: Mon, 11 Sep 2017 11:43:27 GMT
Content-Length: 121

{
  "kind": "ProjectList",
  "apiVersion": "v1",
  "metadata": {
    "selfLink": "/oapi/v1/projects"
  },
  "items": []
}

With oc cluster up --version=v3.7.0-alpha.1:

$ curl 'https://127.0.0.1:8443/oapi/v1/projects' -i -H 'Origin: https://localhost:9000' -H 'authorization: Bearer <token>' -H 'accept: application/json'
HTTP/1.1 200 OK
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Content-Type, Content-Length, Accept-Encoding, X-CSRF-Token, Authorization, X-Requested-With, If-Modified-Since
Access-Control-Allow-Methods: POST, GET, OPTIONS, PUT, DELETE, PATCH
Access-Control-Allow-Origin: https://localhost:9000
Access-Control-Expose-Headers: Date
Cache-Control: no-store
Content-Type: application/json
Date: Mon, 11 Sep 2017 11:47:26 GMT
Content-Length: 121

{
  "kind": "ProjectList",
  "apiVersion": "v1",
  "metadata": {
    "selfLink": "/oapi/v1/projects"
  },
  "items": []
}

@spadgett
Copy link
Member Author

Opened openshift/origin#16279

@benjaminapetersen
Copy link
Contributor

I feel a little less salty @ karma, protractor & all the things now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1
Projects
None yet
Development

No branches or pull requests

2 participants