Why did this get marked as a failure? It looks like all the tests passed. On Dec 14, 2013 12:08 AM, jenkins-no-reply@cloudbees.com wrote:
See < https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.org-linux-fir...
Changes:
[jrobson] Hygiene: Document less files with kss, generate style guide
Started by timer Building remotely on s-d73dafcd in workspace < https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.org-linux-fir...
Fetching changes from the remote Git repository Fetching upstream changes from https://gerrit.wikimedia.org/r/mediawiki/extensions/MobileFrontend Checking out Revision 7588d2a5a4fba0f47c6701666d0919e76fa558de (origin/master) [MobileFrontend-en.m.wikipedia.org-linux-firefox] $ /bin/sh -xe /tmp/hudson3015446263875462020.sh
- export MEDIAWIKI_USER=Selenium_user
- MEDIAWIKI_USER=Selenium_user
- export
MEDIAWIKI_PASSWORD_VARIABLE=MEDIAWIKI_PASSWORD_SELENIUM_USER_WIKIPEDIA_ORG
MEDIAWIKI_PASSWORD_VARIABLE=MEDIAWIKI_PASSWORD_SELENIUM_USER_WIKIPEDIA_ORG
- export BROWSER_LABEL=firefox
- BROWSER_LABEL=firefox
- export MEDIAWIKI_URL=http://en.m.wikipedia.org/wiki/
- MEDIAWIKI_URL=http://en.m.wikipedia.org/wiki/
- curl -s -o use-ruby
https://repository-cloudbees.forge.cloudbees.com/distributions/ci-addons/rub...
- RUBY_VERSION=2.0.0-p247
- source ./use-ruby
++ [[ -z 2.0.0-p247 ]] ++ ruby187='1.8.7-*' ++ [[ 2.0.0-p247 == 1.8.7-* ]] ++ BASE=/scratch/jenkins/addons ++ mkdir -p /scratch/jenkins/addons ++ '[' '!' -f /scratch/jenkins/addons/use.sh ']' ++ . /scratch/jenkins/addons/use.sh ++ mkdir -p /scratch/jenkins/addons/ruby +++ addon_architecture +++ uname -m ++ ruby_name=ruby-2.0.0-p247-x86_64 ++ '[' '!' -f /scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64.tar.bz2 ']' ++ '[' '!' -f /scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64/bin/ruby ']' ++ export RUBY_HOME=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64 ++ RUBY_HOME=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64 ++ export PATH=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64/bin:/opt/jdk/latest/bin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/opt/maven/latest/bin:/opt/ant/latest/bin:/opt/android/android-sdk-linux/tools:/opt/gradle/latest/bin:/home/jenkins/bin:/opt/jdk/jdk.latest/bin ++ PATH=/scratch/jenkins/addons/ruby/ruby-2.0.0-p247-x86_64/bin:/opt/jdk/latest/bin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/opt/maven/latest/bin:/opt/ant/latest/bin:/opt/android/android-sdk-linux/tools:/opt/gradle/latest/bin:/home/jenkins/bin:/opt/jdk/jdk.latest/bin ++ unset GEM_PATH ++ unset GEM_HOME ++ unset BUNDLE_PATH
- gem install bundler --no-ri --no-rdoc
Successfully installed bundler-1.3.5 1 gem installed
- '[' -d tests/browser/ ']'
- cd tests/browser/
- bundle install
Using builder (3.2.2) Using ffi (1.9.3) Using childprocess (0.3.9) Using chunky_png (1.2.9) Using diff-lcs (1.2.4) Using multi_json (1.8.2) Using gherkin (2.12.2) Using multi_test (0.0.2) Using cucumber (1.3.8) Using i18n (0.6.5) Using faker (1.2.0) Using yml_reader (0.2) Using data_magic (0.16.1) Using json (1.8.1) Using net-http-persistent (2.9) Using page_navigation (0.9) Using rubyzip (1.0.0) Using websocket (1.0.7) Using selenium-webdriver (2.37.0) Using watir-webdriver (0.6.4) Using page-object (0.9.3) Using mime-types (2.0) Using rest-client (1.6.7) Using rspec-expectations (2.14.3) Using syntax (1.0.0) Using mediawiki-selenium (0.1.12) Using bundler (1.3.5) Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
- bundle exec cucumber --verbose --profile ci --tags @en.m.wikipedia.org
Code:
- features/support/env.rb
- features/support/hooks.rb
- features/support/modules/url_module.rb
- features/support/pages/article_page.rb
- features/support/pages/beta_page.rb
- features/support/pages/create_article_page.rb
- features/support/pages/create_user_page.rb
- features/support/pages/edit_page.rb
- features/support/pages/home_page.rb
- features/support/pages/language_page.rb
- features/support/pages/login_page.rb
- features/support/pages/notification_page.rb
- features/support/pages/random_page.rb
- features/support/pages/search_page.rb
- features/support/pages/uploads_page.rb
- features/step_definitions/common_steps.rb
- features/step_definitions/create_article_steps.rb
- features/step_definitions/external_links_steps.rb
- features/step_definitions/footer_steps.rb
- features/step_definitions/header_logged_in_steps.rb
- features/step_definitions/header_steps.rb
- features/step_definitions/image_resolves_steps.rb
- features/step_definitions/language_steps.rb
- features/step_definitions/login_required_uploads_steps.rb
- features/step_definitions/login_required_watchlist_steps.rb
- features/step_definitions/menu_opens_page_steps.rb
- features/step_definitions/notification_steps.rb
- features/step_definitions/random_ua_steps.rb
- features/step_definitions/search_steps.rb
- features/step_definitions/uploads_steps.rb
- features/step_definitions/watchlist_steps.rb
Features:
- features/create_article.feature
- features/external_links.feature
- features/footer.feature
- features/footer_logged_in.feature
- features/header.feature
- features/header_logged_in.feature
- features/image_resolves.feature
- features/language.feature
- features/language_logged_in.feature
- features/login_required_uploads.feature
- features/login_required_watchlist.feature
- features/menu_opens_page.feature
- features/notification.feature
- features/random_ua.feature
- features/search.feature
- features/uploads.feature
- features/watchlist.feature
Parsing feature files took 0m0.130s
Build step 'Execute shell' marked build as failure Recording test results
On Sat, Dec 14, 2013 at 6:08 PM, Arthur Richards arichards@wikimedia.orgwrote:
Why did this get marked as a failure? It looks like all the tests passed.
This is another problem that we have noticed but we were never able to figure out what is causing it. As far as I remember, sometimes a Jenkins shell script would for no reason return non zero value, breaking the build.
I believe Chris even reported this to Cloudbees. Chris, did they reply?
Željko
I have talked with Chris about this and as far as he remember, the last time this happened we said we will contact Cloudbees support if it happens again. Since it happened again, I have now contacted support. I will let you know as soon as they reply.
Željko
On Mon, Dec 16, 2013 at 3:21 PM, Željko Filipin zfilipin@wikimedia.orgwrote:
On Sat, Dec 14, 2013 at 6:08 PM, Arthur Richards arichards@wikimedia.orgwrote:
Why did this get marked as a failure? It looks like all the tests passed.
This is another problem that we have noticed but we were never able to figure out what is causing it. As far as I remember, sometimes a Jenkins shell script would for no reason return non zero value, breaking the build.
I believe Chris even reported this to Cloudbees. Chris, did they reply?
Željko
On Sat, Dec 21, 2013 at 6:31 PM, Željko Filipin zfilipin@wikimedia.orgwrote:
I have talked with Chris about this and as far as he remember, the last time this happened we said we will contact Cloudbees support if it happens again. Since it happened again, I have now contacted support. I will let you know as soon as they reply.
Cloudbees support suggested to add --backtrack to cucumber[1]. Let's see if it helps.
Željko -- 1: https://gerrit.wikimedia.org/r/#/c/106260/