Bug 5698

Summary: bash: ptest cases failed
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Chong Lu <chong.lu>
Component: coreAssignee: Yi Zhao <yi.zhao>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Medium CC: liezhi.yang, mark.hatle, markus.boos, meta.mr.watcher, meta.watcher, sgw, yi.zhao
Version: 1.6   
Target Milestone: Future   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
bash ptest log none

Description Chong Lu 2013-12-31 08:37:46 UTC
Created attachment 1699 [details]
bash ptest log

Many bash ptest cases failed

FAIL: run-assoc
FAIL: run-coproc
FAIL: run-execscript
FAIL: run-intl
FAIL: run-lastpipe
FAIL: run-nquote1
FAIL: run-read
FAIL: run-test
FAIL: run-trap
FAIL: run-type

10 test cases fail. Please check the attachment log.
Comment 1 Hongxu Jia 2015-12-14 03:59:07 UTC
commit a74258671f63f0d61e494ee7aa42b8756967a60a
Author: Hongxu Jia <hongxu.jia@windriver.com>
Date:   Sat Nov 28 14:53:40 2015 +0800

    bash: fix testcase run-coproc/run-execscript/run-test/run-heredoc failed
    
    Add user 'test' to fix the failure of 'the test suite should not
    be run as root'(run-execscript and run-test)
    
    Backport test case from git://git.sv.gnu.org/bash.git to fix run-execscript
    and run-heredoc
    
    Still failed cases:
    FAIL: run-intl
    FAIL: run-lastpipe
    FAIL: run-trap
    
    YOCTO: 5698
    
    (From OE-Core rev: 1096140cb1d2532ecb38ac5fbbbe13d40fdaf6af)
    
    Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
    Signed-off-by: Ross Burton <ross.burton@intel.com>
    Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Comment 2 dengke 2016-11-29 01:40:09 UTC
run-lastpipe and run-trap are failed on oe, I have communicate with the maintainer, he said fine for him, maybe others things affect the behavier of bash. I still work on it.
Comment 3 Yi Zhao 2017-11-28 01:21:25 UTC
Duplicate to bug 8832

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