Test failures, possibly related to PySide 6.6.1

[corranwebster]

Some errors I haven’t seen before:

======================================================================
FAIL: test_propagate_errors (traitsui.tests.editors.test_instance_editor.TestInstanceEditor)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/runner/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/traitsui/tests/editors/test_instance_editor.py", line 324, in test_propagate_errors
    self.assertFalse(ok_button.inspect(IsEnabled()))
AssertionError: True is not false

======================================================================
FAIL: test_propagate_errors_switch_selection (traitsui.tests.editors.test_instance_editor.TestInstanceEditor)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/runner/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/traitsui/tests/editors/test_instance_editor.py", line 348, in test_propagate_errors_switch_selection
    self.assertFalse(ok_button.inspect(IsEnabled()))
AssertionError: True is not false

----------------------------------------------------------------------

On MacOS and Windows (but less reliably), Python 3.8-3.11, PySide 6.6.1

[corranwebster]

Can replicate locally on MacOS by running the test suite.

[corranwebster]

Errors don't occur for PySide6 6.6.0.

I have also tested the classes manually and they behave correctly, so this is an issue with the test, not with the underlying TraitsUI code.

[corranwebster]

Digging in to the test, it looks like the error flag is getting set and then reset, and the field ends up containing just the last letter typed.

ETA: on PySide6 6.6.0 the error flag is set twice, but the reset is after the values are being tested - and the field contains the expected text - it seems like there may be an issue with timing/event ordering/dispatch, where the error status is being reset before the state testing takes place.

For now, the simple fix may be to skip the tests for PySide 6.6.1.

[corranwebster]

Seem to be seeing for PySide 6.6.3 as well, after not seeing it on 6.6.2.

[mdickinson]

I'm also seeing it on 6.6.3 (specifically, 6.6.3.1).