Non-Docker provides Chrome 57, Docker provides Chrome 63.
This is problematic when these different browser versions give different responses to unit tests.
VisualEditor core code is tested in Docker on Chrome 63 and then again as part of the VisualEditor-MediaWiki unit test suite on Chrome 57.
For now we've commented out the test that fails, but we'd like to re-enable it later.
"migrate qunit for extensions to Docker" is part of T190097: Migrate all CI jobs from Nodepool, deprecate its use and seems to be happening soon?
Indeed T190097 has been fixed, we no more have any jobs running on Nodepool. That being said, some jobs use a Docker container based on Jessie which ships with Chromium v57.
Some of those tests have a value since they exercise code paths on the backend that are not otherwise testing. Then for when testing javascript frontend, that is definitely a stopper :-(
Maybe the test can be made to skip when Chrome is too old? We can also look at skipping the Chrome tests entirely when running on Jessie.