Bug 1758139

Summary:	Modify logging at Gluster regression tests
Product:	[Community] GlusterFS	Reporter:	Barak Sason Rofman <bsasonro>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7	CC:	amukherj, bugs, gluster-infra, pasik, sheggodu
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:	2020-03-12 12:15:45 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 Barak Sason Rofman 2019-10-03 11:42:19 UTC

Description of problem:

We're currently investigation the affect of Gluster logging on runtime.
In an effort to reduce regression testing runtime, a suggestion came up to start the run with no logging (GF_LOG_NONE) and if a test fails, modify the logging level to debug (GF_LOG_DEBUG), retry the test and then lower the logging level again to no logging (GF_LOG_NONE).
This requires changes to the Jenkins script that runs regression tests (by command "run full regression").

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


How reproducible:
Run regression using "run full regression" command on gerrit


Steps to Reproduce:
1.
2.
3.

Actual results:
Regression testing takes over 4 hours

Expected results:
Trying to reduce regression testing time

Additional info:

Comment 1 Worker Ant 2020-03-12 12:15:45 UTC

This bug is moved to https://github.com/gluster/project-infrastructure/issues/8, and will be tracked there from now on. Visit GitHub issues URL for further details