Skip to content
This repository has been archived by the owner on Jan 14, 2019. It is now read-only.

Rspec failed but jenkins report success #884

Closed
cpanato opened this issue Nov 29, 2016 · 7 comments
Closed

Rspec failed but jenkins report success #884

cpanato opened this issue Nov 29, 2016 · 7 comments

Comments

@cpanato
Copy link

cpanato commented Nov 29, 2016

The rspec usign allure fails but the overall jenkins is set as sucess.
How i can marke the build fail?

2 processes for 3 specs, ~ 1 specs per process
Cleaning output directory '/tmp/results/allure-reports'...
D, [2016-11-29T16:37:11.975520 #11817] DEBUG -- : Starting case_or_suite Contacts with labels {}
D, [2016-11-29T16:37:14.805913 #11817] DEBUG -- : Starting test Contacts.Contacts create a new Contact with all mandatory fields with labels {}
D, [2016-11-29T16:37:14.806201 #11817] DEBUG -- : Stopping test Contacts.Contacts create a new Contact with all mandatory fields
D, [2016-11-29T16:37:14.806298 #11817] DEBUG -- : Starting test Contacts.Contacts fail when missing mandatory fields with labels {}
D, [2016-11-29T16:37:14.806418 #11817] DEBUG -- : Stopping test Contacts.Contacts fail when missing mandatory fields
D, [2016-11-29T16:37:14.806514 #11817] DEBUG -- : Starting test Contacts.Contacts search a contact with labels {}
D, [2016-11-29T16:37:14.806584 #11817] DEBUG -- : Stopping test Contacts.Contacts search a contact
D, [2016-11-29T16:37:14.806664 #11817] DEBUG -- : Starting test Contacts.Contacts update a contact with labels {}
D, [2016-11-29T16:37:14.806733 #11817] DEBUG -- : Stopping test Contacts.Contacts update a contact
D, [2016-11-29T16:37:14.806814 #11817] DEBUG -- : Starting test Contacts.Contacts fail when update a contact but remove mandatory fields with labels {}
D, [2016-11-29T16:37:14.806910 #11817] DEBUG -- : Stopping test Contacts.Contacts fail when update a contact but remove mandatory fields
D, [2016-11-29T16:37:14.807029 #11817] DEBUG -- : Starting test Contacts.Contacts can use autocomplete to search for editions with labels {}
D, [2016-11-29T16:37:14.807104 #11817] DEBUG -- : Stopping test Contacts.Contacts can use autocomplete to search for editions
D, [2016-11-29T16:37:14.807188 #11817] DEBUG -- : Starting test Contacts.Contacts can use autocomplete to search for countries with labels {}
D, [2016-11-29T16:37:14.807262 #11817] DEBUG -- : Stopping test Contacts.Contacts can use autocomplete to search for countries
D, [2016-11-29T16:37:14.807358 #11817] DEBUG -- : Starting test Contacts.Contacts can paginate with labels {}
D, [2016-11-29T16:37:14.807429 #11817] DEBUG -- : Stopping test Contacts.Contacts can paginate
D, [2016-11-29T16:37:14.903900 #11817] DEBUG -- : Stopping case_or_suite Contacts
D, [2016-11-29T16:37:14.910083 #11817] DEBUG -- : Writing file '/tmp/results/allure-reports/02332c60-9880-0134-7f0d-4a841037f8f6-testsuite.xml'...
Cleaning output directory '/tmp/results/allure-reports'...
D, [2016-11-29T16:37:12.980356 #11820] DEBUG -- : Starting case_or_suite Login with labels {}
D, [2016-11-29T16:37:15.303364 #11820] DEBUG -- : Starting test Login.Login failed with labels {}
D, [2016-11-29T16:37:15.762815 #11820] DEBUG -- : Stopping test Login.Login failed
D, [2016-11-29T16:37:15.763300 #11820] DEBUG -- : Starting test Login.Login succeeded with labels {}
D, [2016-11-29T16:37:16.040581 #11820] DEBUG -- : Stopping test Login.Login succeeded
D, [2016-11-29T16:37:16.139608 #11820] DEBUG -- : Stopping case_or_suite Login
D, [2016-11-29T16:37:16.139779 #11820] DEBUG -- : Starting case_or_suite Signals_V2_Page with labels {}
D, [2016-11-29T16:37:18.033390 #11820] DEBUG -- : Starting test Signals_V2_Page.Signals_V2_Page can display the cards for signalsv2 with labels {}
D, [2016-11-29T16:37:18.033621 #11820] DEBUG -- : Stopping test Signals_V2_Page.Signals_V2_Page can display the cards for signalsv2
D, [2016-11-29T16:37:18.128942 #11820] DEBUG -- : Stopping case_or_suite Signals_V2_Page
D, [2016-11-29T16:37:18.131660 #11820] DEBUG -- : Writing file '/tmp/results/allure-reports/041ec5f0-9880-0134-7f0e-4a841037f8f6-testsuite.xml'...
D, [2016-11-29T16:37:18.134451 #11820] DEBUG -- : Writing file '/tmp/results/allure-reports/041f3470-9880-0134-7f0f-4a841037f8f6-testsuite.xml'...
Tests Failed
....
[Tests] $ /home/jenkins-slave/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/1.4.23.HOTFIX1/bin/allure generate "/home/jenkins-slave/workspace/Tests/kermit/regression/results/allure-reports" "/home/jenkins-slave/workspace/Tests/allure3342929295082506833.tmp/environment" -o "/home/jenkins-slave/workspace/Tests/allure3342929295082506833.tmp/allure-report"
Report successfully generated to the directory </home/jenkins-slave/workspace/Tests/allure3342929295082506833.tmp/allure-report>. Use `allure report open` command to show the report.
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
[INFO] HipChat notification sent to the following rooms: TeamBots
Finished: SUCCESS
@vania-pooh
Copy link
Contributor

@cpanato I think only your tests failed according to log. Report with failed tests was successfully generated. So I think it's an RSpec issue to return non-zero status code.

@cpanato
Copy link
Author

cpanato commented Nov 29, 2016

yes, my test fail and then the whole build should set as fail not as success

@vania-pooh
Copy link
Contributor

What is your RSpec version? This was fixed two years ago. rspec/rspec-rails#1016

@cpanato
Copy link
Author

cpanato commented Nov 29, 2016

$ bundle exec rspec -v
3.5.3

@smecsia
Copy link
Contributor

smecsia commented Nov 29, 2016

@cpanato I doubt it is an allure-rspec issue. Please try to run your tests without it and see what happens.

@vania-pooh
Copy link
Contributor

@smecsia I also doubt.

@cpanato
Copy link
Author

cpanato commented Nov 30, 2016

rake issue :(

thanks guys for your support

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants