Thanks for clarifying. As long as it doesn’t happen too often, I don’t think there’s much we can do here – I think the test is valuable enough that we shouldn’t just disable it, I don’t see any obvious problem in the referenced line (repo/tests/selenium/specs/item.js:60), and I don’t think we should look deeper into this specific test at the moment. There is a longer-term task to migrate some of our browser tests, which might include migrating this and other tests away from Selenium towards a more stable platform – see T180228, especially T180228#7178058.