From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Charlton, John" <john.charlton@domain.hid>
Cc: "'jan.kiszka@domain.hid'" <jan.kiszka@domain.hid>,
xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [pull request] Fixes and workarounds for the cond issues
Date: Mon, 08 Mar 2010 17:32:16 +0100 [thread overview]
Message-ID: <4B952690.1060009@domain.hid> (raw)
In-Reply-To: <CF7FB0793253794F9F45991443E5FE2006483DE99F@us194mx002.tycoelectronics.net>
Charlton, John wrote:
> I merged some changes from git://git.xenomai.org/xenomai-jki.git
for-upstream to my xenomai-2.5.1 release distribution
> to include the rt_cond_wait and pthread_cond_[timed]wait work
> arounds.
I also merged changes to the mutex_torture.c. Everything builds and most
tests seem to pass but I get the following output from the mutex-torture
tests:
>
> root@domain.hid# ./mutex-torture-native
> simple_wait
> recursive_wait
> timed_mutex
> FAILURE: timed_waiter, waited 3.870 us
> root@domain.hid# ./mutex-torture-posix
> simple_wait
> recursive_wait
> errorcheck_wait
> timed_mutex
> FAILURE: timed_mutex mutex_destroy: 22 (Invalid argument)
>
> Do you have suggestions on how to resolve these errors hopefully
> without moving to the full development branch?
Ok. I found and fixed this bug. It was a bug in the testcase. It would
really help us, however, if you could pull the full development branch,
and just give it a quick test to see if it fixes the current issue. It
is our hope that this development branch is close to what 2.5.2 will be.
--
Gilles.
prev parent reply other threads:[~2010-03-08 16:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 22:54 [Xenomai-core] [pull request] Fixes and workarounds for the cond issues Jan Kiszka
2010-03-04 10:40 ` Gilles Chanteperdrix
2010-03-04 10:30 ` [Xenomai-core] ADEOS patch for LPC3250 Pierre Ficheux
2010-03-04 13:37 ` Gilles Chanteperdrix
2010-03-04 11:26 ` [Xenomai-core] [pull request] Fixes and workarounds for the cond issues Jan Kiszka
2010-03-04 11:28 ` Jan Kiszka
2010-03-04 13:45 ` Gilles Chanteperdrix
2010-03-04 13:53 ` Jan Kiszka
[not found] ` <CF7FB0793253794F9F45991443E5FE2006483DE99F@us194mx002.tycoelectronics.net>
2010-03-05 18:36 ` Gilles Chanteperdrix
2010-03-08 18:42 ` Charlton, John
2010-03-08 18:47 ` Gilles Chanteperdrix
2010-03-08 20:39 ` Charlton, John
2010-03-08 20:42 ` Gilles Chanteperdrix
2010-03-08 21:13 ` Charlton, John
2010-03-08 16:32 ` Gilles Chanteperdrix [this message]
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=4B952690.1060009@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=john.charlton@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.