From: Kang Kai <Kai.Kang@windriver.com>
To: oe-core <openembedded-core@lists.openembedded.org>
Subject: Design document for Posix test
Date: Tue, 22 Nov 2011 17:59:29 +0800 [thread overview]
Message-ID: <4ECB7281.1030900@windriver.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1315 bytes --]
Hi all,
The attachment files are the POSIX test result for Yocto 1.1 on non-x86
platform. And the POSIX test suit is from ltp-full-20110915.
According to POSIX tests for Yocto 1.1 milestones, group
SIG SEM THR TMR MSG TPS MEM
are tested, and AIO is excluded.
There are 1794 test cases in total. Most of them can pass, and others
have some problems.
1 There are 21 failed items need to be fixed(some occur on different
platform), they are:
THR(8):
pthread_cond_broadcast/1-2
pthread_create/1-6
pthread_create/10-1
pthread_create/14-1
pthread_mutex_lock/3-1
pthread_rwlock_rdlock/2-1
pthread_rwlock_rdlock/2-1
pthread_rwlock_unlock/3-1
TMR(2):
timer_getoverrun/2-3
clock_getcpuclockid/5-1
MSG(3):
mq_timedreceive/5-2
mq_timedreceive/10-2
mq_timedsend/5-1
TPS(3):
sched_getparam/6-1
sched_getscheduler/7-1
sched_yield/1-1
MEM(5):
mmap/11-4
mmap/11-5
mmap/28-1
mmap/31-1
shm_open/23-1
2 Items need more research
*
2.1 sem_init/7-1
*
3.1 pthread_cond_broadcast/1-2
*
3.4 pthread_create/1-6
*
3.1 pthread_cond_broadcast/1-2
There are some items about
*
SCHED_SPORADIC
this needs more research too.
Any suggestion is welcome!
Regards,
Kai
[-- Attachment #1.2: Type: text/html, Size: 15497 bytes --]
[-- Attachment #2: POSIX-results_and_analysis.odt --]
[-- Type: application/vnd.oasis.opendocument.text, Size: 18307 bytes --]
[-- Attachment #3: posix_test_results.ods --]
[-- Type: application/vnd.oasis.opendocument.spreadsheet, Size: 14949 bytes --]
reply other threads:[~2011-11-22 10:06 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=4ECB7281.1030900@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.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