search

openshift / origin-server

OpenShift 2 (deprecated)
888 stars 516 forks source link

Verbose assertion in console.js test #6426

Closed Miciah closed 8 years ago

Miciah commented 8 years ago

Make the assertion failure in the console.js content length test more verbose in order to diagnose this failure in https://github.com/openshift/li/pull/3147:

test_retrieve_the_main_javascript_resource(AssetsTest) [/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-console-1.35.4/test/integration/assets_test.rb:10]:
Failed assertion, no message given.

openshift-bot, please [test]!

Miciah commented 8 years ago

The problem is becoming clearer:

test_retrieve_the_main_javascript_resource(AssetsTest) [/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-console-1.35.4/test/integration/assets_test.rb:10]: 
response body was shorter than expected: throw Error("ExecJS::RuntimeError: node: error while loading shared libraries: libuv.so.0.10: cannot open shared object file: No such file or directory\n\n  (in /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-console-1.35.4/app/assets/javascripts/console/form.js.coffee)")

openshift-bot, please [test] again!

Miciah commented 8 years ago

During https://ci.dev.openshift.redhat.com/jenkins/job/test_pull_requests/9417/, I checked and saw that the libuv was not installed on the EC2 instance. After the Site Check Base test had failed once, I installed the libuv package on the EC2 instance. After that, during the second test run, the Site Check Base test succeeded.

Miciah commented 8 years ago

Please [test] again!

Miciah commented 8 years ago

Please [test] again!

Miciah commented 8 years ago

Please [test] again!

openshift-bot commented 8 years ago

Evaluated for online test up to 0fe172ced5f753e5dda695dc32d8657d18269ea7

openshift-bot commented 8 years ago

Online Test Results: FAILURE (https://ci.dev.openshift.redhat.com/jenkins/job/test_pull_requests/9428/) (Base Commit: 0a66575de22d26018ceb36d10823a76b08045854)

Miciah commented 8 years ago

The original problem has been fixed by fixing the package mirror so it has the right nodejs packages.