Conversation
c3777ac
to
69a8b8d
Compare
69a8b8d
to
5e8e6f5
Compare
This test failure appears to be unrelated. Is the media feature broken upstream? |
Judging by Travis' output, it looks like there might be a syntax error in composer.json? |
@phenaproxima There was, yes. It's been fixed. There is now a failing media test in this build: https://travis-ci.org/acquia/lightning/builds/100441364 |
That is one hell of a weird error; as far as I can tell, the x-factor appears to be the introduction of PhantomJS. Maybe PhantomJS is not compatible with the tests, or with our JS? (We are using a few relatively new techniques, like ES6 Promises -- although we have a polyfill for that.) |
Yeah, it's totally possible that PhantomJS doesn't play well with that. My main goal in this PR is to reduce the noise in the logs created by Selenium. A secondary goal is to make testing faster by making it headless. |
I think we had a few things going on here. Foremost, the media_library.feature was failing periodically (~20%). When we introduced phantom, it was failing ~80% of the time. Introducing a pause before trying to click on the media WYSIWYG button fixed this so I think we were runninginto an issue where CKEditor wasn't fully loaded some of the time (more often with phantom because it's faster(?)). Once I introduced that 1-second delay, everything passed locally 100% of the time using both selenium or phantomjs. But Travis was failing with a new error on the media_library.feature:
I swapped selenium back in and travis is happy. I'm happy to switch to phantomjs still (agree the cleaner logs are nice) but I'm not sure what's causing the above error. So, for now, we;re back to selenium. |
We're looking at including Lightning in all of our project by default, but we need resolve the issue with media_library that you encountered, since we use PhantomJS in PS. |
Great. We can re-prioritize this. It was a dead end for me if I remember correctly - couldn't find any clues as to why it was failing on travis specifically. Maybe some fresh eyes will help. I or @phenaproxima will take another look before the end of the week. Thanks. |
It looks like this is due to PhantomJS not having the prototype.bind() function that CKEditor relies on. This has been solved with non-PHP implementation of PhantomJS, gotta look into a solution for us. See:
Possible solution: |
No description provided.