ordering problem with "system_func" test

[Quentin Barnes <qbarnes at urbana dot css dot mot dot com>]

I'm using 20070519 snapshot on a 2.6.21.1 ARM kernel.

The "system_func" test is giving me intermittent results.  I saw #4466
go by, but I'm running the test after that change.

What's happening for me is that the output messages can appear in
different orders, but the its expect script is always expecting the
messages in the same order -- "$user" -> "sys_open" -> "DONE".

Below shows sample successful and failed runs.  What's the bug here?
Is system_func.stp written in such a way to always guarantee the
output message order on all architectures (so the exp script is
right, but my Systemtap port or kernel is somehow broken) or is the
script broken always assuming only one output order is possible?

Quentin


Here's a successful run:
==========
root^M
sys_open^M
cat: __xyzzy123ABC__: No such file or directory^M
^M
Waititing for processes to exit^M
DONE^M
PASS: system_func
testcase /usr/src/systemtap-20070519/testsuite/systemtap.samples/system_func.exp completed in 74 seconds
==========

Here's a failed run:
==========
sys_open^M
DONE^M
^M
Waititing for processes to exit^M
cat: __xyzzy123ABC__: No such file or directory^M
root^M
FAIL: system_func (0,1,0)  

testcase /usr/src/systemtap-20070519/testsuite/systemtap.samples/system_func.exp completed in 114 seconds
==========

Quentin