From: fixed-term.Oleksij.Rempel <fixed-term.Oleksij.Rempel@de.bosch.com>
To: ltp@lists.linux.it
Subject: [LTP] updating message_queue_test_02_*
Date: Thu, 7 Jul 2016 15:04:31 +0200 [thread overview]
Message-ID: <577E535F.2040606@de.bosch.com> (raw)
In-Reply-To: <577E4340.4060208@de.bosch.com>
On 07.07.2016 13:55, fixed-term.Oleksij.Rempel wrote:
> Hallo all,
>
> it is kind of a duplication of this case:
> https://github.com/linux-test-project/ltp/issues/75
>
> some of message_queue_test_02_* are fail on our configuration, it looks
> like the reason is hardcoded tmp path, which is different in our test setup.
>
> Looks like this tests should be updated to use current ltp bindings..
> which should also fix this issue. Do any one already working on it? If
> not, me or some of us will try to do it.
>
hm...
to execute *message_queue_test_02_rcv* properly, first should be
*message_queue_test_02_snd* executed. And most important, target should
not be reseted after message_queue_test_02_snd. If this happens,
message_queue_test_02_rcv will hang forever.
It is not looks like proper behaviour (it is not theoretical assumption.).
May be message_queue_test_02_rcv should be wrapped by a script which
will start rcv in background and then send after short sleep?
And some how make sure that message_queue_test_02_rcv wont wait forever?
Any comments?
next prev parent reply other threads:[~2016-07-07 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 11:55 [LTP] updating message_queue_test_02_* fixed-term.Oleksij.Rempel
2016-07-07 13:04 ` fixed-term.Oleksij.Rempel [this message]
2016-07-08 9:24 ` Hoang Thi Thuy Nga
2016-07-08 10:57 ` FIXED-TERM Rempel Oleksij
[not found] ` <ce7e60e37813403a98b3594aec354d06@SGPMBX1022.APAC.bosch.com>
[not found] ` <57835D54.2020803@de.bosch.com>
2016-07-13 4:35 ` Hoang Thi Thuy Nga
2016-07-13 4:52 ` fixed-term.Oleksij.Rempel
-- strict thread matches above, loose matches on Subject: below --
2016-07-07 11:52 fixed-term.Oleksij.Rempel
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=577E535F.2040606@de.bosch.com \
--to=fixed-term.oleksij.rempel@de.bosch.com \
--cc=ltp@lists.linux.it \
/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