Bug 1627624

Summary:	Run gd2-smoke only after smoke passes
Product:	[Community] GlusterFS	Reporter:	Prashanth Pai <ppai>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, sankarshan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-27 00:59:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Prashanth Pai 2018-09-11 05:26:12 UTC

Sometimes compilation/build itself fails on glusterfs patches. It's wasted resources to run other tests/jobs if basic smoke doesn't pass.

On an unrelated note:
It is unfortunate to see developers (re)trigger centos7 regression *before* they have witnessed smoke test passing.

Comment 1 Nigel Babu 2018-10-03 08:53:51 UTC

I have plans to fix this once distributed testing is in production. It will all be one pipeline job which will stop executing when it sees one failure.