[lmi] wine-6.0.3 "fixme" and "err:rpc"

[Greg Chicares]

I don't think there's any actual problem here, but it seems best
to get this on the record.

With SHA1 ee23febbac1481 (HEAD -> master, origin/master, origin/HEAD),
in a new 'bookworm' chroot created three days ago, which provides
  wine-6.0.3 (Debian 6.0.3~repack-1)
numerous 'wine' messages appear with a nychthemeral test:

/opt/lmi/src/lmi[0]$make raze; time ./nychthemeral_test.sh
rm --force --recursive /opt/lmi/gcc_x86_64-pc-linux-gnu
rm --force --recursive /opt/lmi/clang_x86_64-pc-linux-gnu
rm --force --recursive /opt/lmi/gcc_x86_64-w64-mingw32
LMI_TRIPLET = "x86_64-pc-linux-gnu"
LMI_TRIPLET = "x86_64-w64-mingw32"
0024:fixme:event:wait_for_withdrawn_state window 0x50078/a00006 wait timed out
0024:fixme:shell:SHAutoComplete stub
0024:fixme:shell:SHAutoComplete stub
0024:fixme:event:wait_for_withdrawn_state window 0x20470/a00025 wait timed out
0024:fixme:shell:SHAutoComplete stub
0024:fixme:shell:SHAutoComplete stub
0024:fixme:event:wait_for_withdrawn_state window 0x3049a/a0004f wait timed out
0024:fixme:shell:SHAutoComplete stub
0024:fixme:shell:SHAutoComplete stub
0024:fixme:event:wait_for_withdrawn_state window 0x603f4/a00079 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0xc0442/a0014e wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0xd0442/a0017b wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0xe0442/a001ab wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0xf0442/a001cd wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x100442/a001f1 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x110442/a00218 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x120442/a0023c wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x130442/a00260 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x140442/a00284 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x150442/a002a8 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x160442/a002c9 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x170442/a002ea wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x220404/a0030d wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x230404/a00329 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x270404/a00346 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x2500a4/a00348 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x2c045e/a00365 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x2d045e/a00381 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x2e045e/a0039d wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x2800d4/a0039e wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x2900d4/a0039f wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x4100d2/a003a1 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x10056/a00004 wait timed out
0094:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003
./nychthemeral_test.sh  23457.01s user 928.10s system 1164% cpu 34:54.92 total

The return code is '0', and everything appeared to work.
I imagine that the "fixme" messages can probably be ignored,
but the "err:rpc" one seems graver.

Output is saved separately for each of these nychthemeral tests,
and the "err:rpc" message is printed while building default targets
with glibc warning macros:

  /opt/lmi/gcc_x86_64-w64-mingw32/logs/default_targets_safestdlib

  x86_64-w64-mingw32-g++ -MMD -MP -MT dbnames.o -MF dbnames.d  -c -I 
/opt/lmi/src/lmi -I /opt/ ...
  0094:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003
  x86_64-w64-mingw32-g++ -MMD -MP -MT dbo_rules.o -MF dbo_rules.d  -c -I 
/opt/lmi/src/lmi -I />...

Because the "fixme" messages all occur during the GUI test, I suppose
the "err:rpc" thing is just a delayed consequence of that test, and
has nothing to do with the target being built when it prints.

At the bottom of the GUI-test log I see:

  /opt/lmi/gcc_x86_64-w64-mingw32/logs/gui_test

  SUCCESS: 21 tests successfully completed.
  NOTE: 4 tests were skipped
  0024:fixme:event:wait_for_withdrawn_state window 0x10056/a00004 wait timed out
  X connection to :99 broken (explicit kill or server shutdown).

so that test was successful. The "X connection to :99 broken" message
is routine and expected (it's been discussed earlier on this list).