The XEventsQueued test purpose #3 assumes that calls to XCreatePixmap won't be
immediately flushed. Xlib/XCB always immediately moves requests from Xlib's
output queue into XCB's. This test blames the fact that those requests aren't in
Xlib's queue any more on XEventsQueued, and reports FAIL.
I think the correct result in this case is UNTESTED, following the example of
the similar XFlush test. I've patched the test to check for this kind of
"auto-flush" behavior, and not run the rest of the test in that case. After
applying the patch, the test continues to PASS on X.org Xlib while producing
UNTESTED on Xlib/XCB.
Created attachment 3200 [details] [review]
Check for "auto-flush" behavior and report UNTESTED instead of FAIL.
Patch tested and committed.