https://bugzilla.wikimedia.org/show_bug.cgi?id=60037

--- Comment #13 from Antoine "hashar" Musso <has...@free.fr> ---
Looking at the failing job:

https://wmf.ci.cloudbees.com/job/browsertests-en.wikipedia.beta.wmflabs.org-linux-chrome/619/

The console does not show anything relevant beside the job failing:

https://wmf.ci.cloudbees.com/job/browsertests-en.wikipedia.beta.wmflabs.org-linux-chrome/619/console

Looking at the test report we get way more details:

https://wmf.ci.cloudbees.com/job/browsertests-en.wikipedia.beta.wmflabs.org-linux-chrome/619/testReport/

With a nice stack trace and way more details for each tests:

https://wmf.ci.cloudbees.com/job/browsertests-en.wikipedia.beta.wmflabs.org-linux-chrome/619/testReport/(root)/Page/Move_existing_page_dialog/


config/cucumber.yml of qa/browsertests.git has:

ci: --format Cucumber::Formatter::Sauce --out reports/junit


That define a profile named 'ci' with options which are passed to cucumber. 
That configuration means cucumber will write output using the Sauce format to a
file (reports/junit) discarding output to the console.

It might be possible to add a second formatter and have write to stdout which
would show up on the console.


Another possibility is to intercept cucumber exit code and echo a clear message
saying the job has some failure and craft an URL pointing to the test report.
Something like:


bundle exec cucumber --backtrace --verbose --profile ci --tags
@en.wikipedia.beta.wmflabs.org || (echo -e "\nJob as failed (exit code:
$?).\nSee test report at $BUILD_URL/testReport/\n")


Jenkins env variables are listed at:

https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-JenkinsSetEnvironmentVariables

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to