e.g. https://travis-ci.org/PolymerElements/app-layout/builds/150077994
This is not what we want. phantom should be opt in on travis because its failures aren't a strong signal that anything is wrong, and if the other browsers pass we don't want to fail just for phantom.
Why not just disable phantom in wct.conf.json?
I need to run tests in phantom, but i could not because of the merged PR.
@azakus do you have any plans to re-enable PhantomJS support?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
Why not just disable phantom in wct.conf.json?
I need to run tests in phantom, but i could not because of the merged PR.