From: Michal Simek <michal.simek@petalogix.com>
To: Mike Frysinger <vapier@gentoo.org>,
"subrata@linux.vnet.ibm.com" <subrata@linux.vnet.ibm.com>,
LTP <ltp-list@lists.sourceforge.net>
Subject: [LTP] Fake test result
Date: Mon, 03 Aug 2009 16:03:22 +0200 [thread overview]
Message-ID: <4A76EE2A.201@petalogix.com> (raw)
Hi Subrata and Mike,
As I wrote in my previous email (no response on it - Subject getcontext,
add_key, fcntl24, fcntl25, fcntl26, open10)
there is wrong reporting PASS/FAIL for latest LTP code.
There is one broken Mike's commit "extend the test result to a bit field
so we can extend the output further"
http://developer.petalogix.com/git/gitweb.cgi?p=ltp-microblaze.git;a=commit;h=8b4a8c10b4ec8576a470b9886c7e96a084fb68e0
There is one more patch which relate with that one above -"convert errno
handling to new tst errno helpers" - mmap09.c
http://developer.petalogix.com/git/gitweb.cgi?p=ltp-microblaze.git;a=commit;h=92029c333858cefc3b2e03f84a1a74d946f81803
I am running ./runltp -q -f syscalls. Please look at tests which failed
on your arch (the new one are the best).
If you see the same problem as I, please revert these two patches.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
reply other threads:[~2009-08-03 14:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A76EE2A.201@petalogix.com \
--to=michal.simek@petalogix.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=subrata@linux.vnet.ibm.com \
--cc=vapier@gentoo.org \
/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