We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug description
Running accessible::tests::test_accessible_update_state causes a critical that looks a little concerning.
accessible::tests::test_accessible_update_state
Maybe it could be useful to set fatal criticals in tests? Or would that cause too many flaky tests?
test accessible::tests::test_accessible_update_state ... ok (process:1000119): GLib-GObject-CRITICAL **: 18:07:29.862: g_value_get_pointer: assertion 'G_VALUE_HOLDS_POINTER (value)' failed
The text was updated successfully, but these errors were encountered:
Generally a good idea to make criticals fatal and we do that in gtk-rs-core (I hope!) and gstreamer-rs (definitely)
Sorry, something went wrong.
I wanted to get a backtrace and now I can't reproduce it anymore. sigh.
Feel free to close if you can't either, I've been doing too much stuff with my screenreader today that might have messed up gtk in some way.
No branches or pull requests
Bug description
Running
accessible::tests::test_accessible_update_state
causes a critical that looks a little concerning.Maybe it could be useful to set fatal criticals in tests? Or would that cause too many flaky tests?
The text was updated successfully, but these errors were encountered: