From: Cyril Hrubis <chrubis@suse.cz>
To: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [REPORT] fs_perms.c issue
Date: Wed, 17 Dec 2014 09:05:24 +0100 [thread overview]
Message-ID: <20141217080523.GA23215@rei> (raw)
In-Reply-To: <1418780643.28978.64.camel@G08JYZSD130126.localdomain>
Hi!
> I have test fs_perms in the latest version, but output:
> "Segmentation fault"
> In commit 9fa8ad01f33c6390cc08626a185111631c8df495
> -------------------------------------------------------------------------------------
> - tst_resm((exp_res == res1) && res2 ? TPASS : TFAIL,
> - "%c a %03o file owned by (%d/%d) as user/group (%d/%d)",
> + tst_brkm((exp_res == res1) && res2 ? TPASS : TFAIL,
> + tst_rmdir, "%c a %03o file owned by (%d/%d) as user/group (%d/%d)",
> fperm[0], fmode, fuser_id, fgroup_id, user_id, group_id);
> -
> - tst_rmdir();
> - tst_exit();
> -------------------------------------------------------------------------------------
> TPASS should not be return from tst_brkm. We should use tst_resm still.
Right, I've missed that in the automatic cleanup. Will fix ASAP.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
parent reply other threads:[~2014-12-17 8:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1418780643.28978.64.camel@G08JYZSD130126.localdomain>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141217080523.GA23215@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=zenglg.jy@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox