Closed thechrisrobinson closed 7 years ago
Should be stable -- the last merge fixed the legitimate UI test failure.
See 294-297 builds.
If this pops up again, let's backlog the issue as it's not a show stopper for production build or any builds. It is not a code issue either -- 100% bug with protractor, xvfb, and chrome interaction.
Workaround for future: ==> Add additional build machine (Windows or Ubuntu with desktop) and execute the GUI unit tests there.
@benrogers-kpmg @robertlevy
New e2e.js updates have unmasked a system level bug causing chrome to crash in xvfb.
Unit tests on GUI are failing due to this (locally succeed).