Bug 1699712 - regression job is voting Success even in case of failure
Summary: regression job is voting Success even in case of failure
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-15 04:11 UTC by Amar Tumballi
Modified: 2019-04-22 03:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-22 03:18:12 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Amar Tumballi 2019-04-15 04:11:40 UTC
Description of problem:
Check : https://build.gluster.org/job/centos7-regression/5596/consoleFull

----
09:15:07 1 test(s) failed 
09:15:07 ./tests/basic/uss.t
09:15:07 
09:15:07 0 test(s) generated core 
09:15:07 
09:15:07 
09:15:07 2 test(s) needed retry 
09:15:07 ./tests/basic/quick-read-with-upcall.t
09:15:07 ./tests/basic/uss.t
09:15:07 
09:15:07 Result is 124
09:15:07 
09:15:07 tar: Removing leading `/' from member names
09:15:10 kernel.core_pattern = /%e-%p.core
09:15:10 + RET=0
09:15:10 + '[' 0 = 0 ']'
09:15:10 + V=+1
09:15:10 + VERDICT=SUCCESS
----

Version-Release number of selected component (if applicable):
latest master

Comment 1 Deepshikha khandelwal 2019-04-15 05:16:15 UTC
Thank you Amar for pointing this out. It turned out to behave like this because of the changes in config we made last Friday evening. Now that it is fixed, I re-triggered on three of the impacted patches.

Sorry for this.


Note You need to log in before you can comment on or make changes to this bug.