Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1695484 - smoke fails with "Build root is locked by another process"
Summary: smoke fails with "Build root is locked by another process"
Status: NEW
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2019-04-03 08:15 UTC by Pranith Kumar K
Modified: 2019-04-03 15:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:

Attachments (Terms of Use)

Description Pranith Kumar K 2019-04-03 08:15:37 UTC
Description of problem:
Please check for more details. Smoke is failing with the reason mentioned in the subject.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Deepshikha khandelwal 2019-04-03 08:35:11 UTC
It happens mainly because your previously running build was aborted by a new patchset and hence no cleanup. 

Re-triggering might help.

Comment 2 M. Scherer 2019-04-03 10:29:53 UTC
Mhh, then shouldn't we clean up when there is something that do stop the build ?

Comment 3 M. Scherer 2019-04-03 15:09:52 UTC
So indeed, aborted the patch test, then failed. but the next run worked.

Maybe the problem is that it take more than 30 seconds to clean the build or something similar. Maybe we need to add some more time, but I can't seems to find a log to evaluate how long it does take when things are cancelled. Let's keep stuff opened if the issue arise again to collect the log, and see if there is a pattern.

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