Bug 1613310 - line coverage tests need increased timeouts
Summary: line coverage tests need increased timeouts
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1608564
TreeView+ depends on / blocked
 
Reported: 2018-08-07 11:52 UTC by Shyamsundar
Modified: 2018-09-17 07:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1608564
Environment:
Last Closed: 2018-09-17 07:16:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Shyamsundar 2018-08-07 11:52:24 UTC 
+++ This bug was initially created as a clone of Bug #1608564 +++

Multiple tests take more time to as instrumented code (lcov) takes more time to complete.

This patch https://review.gluster.org/#/c/20648/ adds a "-t" option to provide a timeout to run-tests.sh, to facilitate changing the default across different test strategies.

The bug is opened to use the above in line-coverage tests to increase the default timeout from 200 to 300 seconds.
Comment 1 Nigel Babu 2018-08-07 14:27:28 UTC 
posted review https://review.gluster.org/20655
Note You need to log in before you can comment on or make changes to this bug.