Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1791407

Summary: Tests are getting killed during setup phase while extracting the repo
Product: [Retired] Restraint Reporter: Rachel Sibley <rasibley>
Component: generalAssignee: beaker-dev-list
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: asavkov, bpeck, breilly, cbeer, jbastian, pkis
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-01-15 20:25:51 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 Rachel Sibley 2020-01-15 18:43:31 UTC 
Description of problem:

We are seeing long durations during the setup phase while extracting our test repo https://github.com/CKI-project/tests-beaker, in many cases it will take up to an hour to extract the repo and the tests are later aborted by watchdog.

From Martin Styk:
Restraint is sending really small chunks back to Beaker all the time. So in case something happening with network, this may take forever due to retries (and let's say you had to do retry for few bytes).

See https://bugzilla.redhat.com/show_bug.cgi?id=1727850 for more details.

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

How reproducible:
Easily reproducible

Steps to Reproduce:
1. In our case, we see it when extracting using fetch_url
2.
3.

Actual results:
Test aborts during setup phase

Expected results:
Setup phase completes in a timely manner with no aborts

Additional info:
See https://beaker.engineering.redhat.com/recipes/7800321#task104832841 for example job.
Comment 1 Rachel Sibley 2020-01-15 20:25:51 UTC 

*** This bug has been marked as a duplicate of bug 1782422 ***