Has anyone else seen this issue happen?
It started happening again on one of our private instances. I uninstalled Chrome, manually deleted the profile directories, and then let wptdriver handle the chrome installation. Once installed it continued showing the profile error.
So I cleared Chrome and profiles down again, instead of letting wptdriver install Chrome I manually installed it myself. I’ve not seen the profile error since.
Incidentally our private instances sit there all day running tests for WPT, the only time we ever login to them is if we notice tests are going wrong.
Would be good to get acknowledgment from a WPT dev that this is a bug, at least to confirm that it’s not something I am doing to cause it.