Bug 1036283 - [] always can not generate /TESTOUT.log in one case
Summary: [] always can not generate /TESTOUT.log in one case
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: develop
Hardware: All
OS: Linux
unspecified
urgent vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-30 12:47 UTC by JianHong Yin
Modified: 2018-02-06 00:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-03 02:11:30 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description JianHong Yin 2013-11-30 12:47:09 UTC 
Description of problem:
Always can not generate /TESTOUT.log in one case.
https://beaker.engineering.redhat.com/jobs/554466

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

How reproducible:
100%

Steps to Reproduce:
1. run case /CoreOS/nfs-utils/Regression/bz869400-nfsv4-referrals-fail-if-nfs-server-returns-hostnames-rather-than-ip
2. check the result: always can not generate /TESTOUT.log
3.

Actual results:
Always can not generate /TESTOUT.log in one case.

Expected results:
normal

Additional info:
  why??
Comment 1 JianHong Yin 2013-12-01 00:10:19 UTC 
the beaker RUN ID:   
T:17640559    aborted
T:17640561    aborted
Comment 2 Petr Muller 2013-12-02 12:26:37 UTC 
This is not BeakerLib. Beaker is the piece creating TESTOUT.log.
Comment 4 JianHong Yin 2013-12-03 02:11:30 UTC 
by analyse I notice that, the test mount point is /mnt/testarea;
maybe this dir is reserved for beaker, I changed the mountpoint dir,
and test again, it works fine;
Note You need to log in before you can comment on or make changes to this bug.