Slow hosts (e.g., Scratchbox, under emulation) can trigger warnings in
both directions, and also `unexpected-challenge', depending on how far
the key exchange has progressed by the time the other end gets the
`FORCEKX' command.
m4_define([AWAIT_KXDONE], [
## Ignore some reports caused by races.
m4_define([AWAIT_KXDONE], [
## Ignore some reports caused by races.
- TRIPECTL -d$3 WARN test PUSH
- TRIPECTL -d$3 WARN test IGNORE WARN KX $2 incorrect cookie
- TRIPECTL -d$3 WARN test IGNORE WARN KX $2 unexpected pre-challenge
+ for d in $1 $3; do
+ TRIPECTL -d$d WARN test PUSH
+ TRIPECTL -d$d WARN test IGNORE WARN KX $2 incorrect cookie
+ TRIPECTL -d$d WARN test IGNORE WARN KX $2 unexpected pre-challenge
+ TRIPECTL -d$d WARN test IGNORE WARN KX $2 unexpected challenge
+ done
## Watch for the key-exchange completion announcement in the background.
COPROCESSES([wait-$1], [
## Watch for the key-exchange completion announcement in the background.
COPROCESSES([wait-$1], [
AT_CHECK([echo $waitrc],, [0[]nl])
## Be interested in key-exchange warnings again.
AT_CHECK([echo $waitrc],, [0[]nl])
## Be interested in key-exchange warnings again.
- TRIPECTL -d$3 WARN test POP
+ for d in $1 $3; do TRIPECTL -d$d WARN test POP; done
])
## ESTABLISH(adir, aname, aopts, bdir, bname, bopts, [aport], [bport])
])
## ESTABLISH(adir, aname, aopts, bdir, bname, bopts, [aport], [bport])