Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

travis run for chrome unstable (as for now version 54) fails on qx.test.ui.embed Flash:testEvents #9167

Closed
level420 opened this issue Sep 7, 2016 · 16 comments
Labels
bug Errors

Comments

@level420
Copy link
Member

level420 commented Sep 7, 2016

See https://travis-ci.org/qooxdoo/qooxdoo/jobs/158131683

The log says:

Chrome 54.0.2840 (Linux 0.0.0) qx.test.ui.embed Flash:testEvents FAILED
    expected loaded to have been called at least once but was never called: Called fail().
        qx.core.AssertionError.constructor:43:38
        qx.core.Assert.__fail:71:19
        qx.core.Assert.fail:139:12
        qx.type.BaseString.fail:50:22
        qx.dev.unit.Sinon.failAssertion:4754:20
        anonymous()
        anonymous()
        qx.dev.unit.TestResult.run:237:36
        anonymous()
        anonymous()
        qx.event.dispatch.Direct.prototype.dispatchEvent()
        wrappedFunction()
        qx.event.Manager.prototype.dispatchEvent()
        qx.event.Registration.fireEvent()
        qx.core.Object.prototype.fireEvent()
        anonymous()
        qx.event.Timer.prototype._oninterval()
        anonymous()
@level420
Copy link
Member Author

level420 commented Sep 7, 2016

This may be due to the upcoming changes in flash support for chrome:

https://chrome.googleblog.com/2016/08/flash-and-chrome.html

@level420
Copy link
Member Author

level420 commented Sep 9, 2016

I've run the failing test (and all others) with testrunner on Windows 7 with Chrome 54.0.2840.16 beta-m (distrubuted today via the beta channel) where the tests succeeded.

So it seems to be specific to either the travis environment or the linux version of Chrome.

We should maybe wait for the next beta to see if this is a bug in chrome.

Also note that all other flash related tests work.

@cajus
Copy link
Contributor

cajus commented Sep 20, 2016

Looks like it's no more reproducible locally. I had it yesterday, but now as I want to debug it, the test is green and I can't get it to fail in chrome 45. Doh.

@level420
Copy link
Member Author

level420 commented Sep 20, 2016

@cajus how did you serve? both tests with php server?

@cajus
Copy link
Contributor

cajus commented Sep 20, 2016

yes

@cajus
Copy link
Contributor

cajus commented Sep 20, 2016

So it looks like the tests are enabled, but the PercentLoaded() method returns a TypeError.

@level420
Copy link
Member Author

@cajus is it reproducible again?

@cajus
Copy link
Contributor

cajus commented Sep 20, 2016

only on travis

@cajus
Copy link
Contributor

cajus commented Sep 21, 2016

Ok. It's only on Ubuntu. No idea why I've seen it exactly once on my Fedora installation, though.

On a recent Ubuntu system, it can be fixed by installing the adobe-flashplugin package. As travis' ubuntu is stock old, that will not work and the flashplugin-installer method doesn't seem to install the chromium pepper hooks, so it does not replace the chrome base flash.

Sigh. The travis base system is really frustrating. Looks like I've to install a stock old ubuntu vm to see what flashplugin-installer installs in which location to be able to add the pepper hook.

Edit: it's a bug in the chrome*deb packages

@level420
Copy link
Member Author

@cajus I don't know if it is worth finding out why it doesn't work on travis old ubuntu. Could we maybe detect that we are running on travis and disable this specific test for this environment?

@level420
Copy link
Member Author

level420 commented Sep 22, 2016

It also may be worth considering to use the "TRUSTY BETA" test environment as per documentation https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments if the old ubuntu version is the problem. TRUSTY BETA is v 14 while the standard docker is on v 12.

TRUSTY BETA is slow on startup compared to the docker based environment, but our tests run 8 to 10 minutes anyway, so one minute more does not matter.

@cajus
Copy link
Contributor

cajus commented Sep 22, 2016

@level420 I've described why it fails in the last comment. And I described what could be done to make it work again. Working it around in travis is possible, but it's a waste of time IMHO. Lets just deprecate flash. It's dead. Or wait until google fixes the embedded flash.

@cajus
Copy link
Contributor

cajus commented Sep 22, 2016

@level420 the trusty beta will not help. you can only install whitelisted packages. The ones we need are not whitelisted. So it makes no difference. Or we go back to complete installations instead of docker images - but this is much slower than the current approach. Building a custom docker image is a way to solve it. But I doubt that we'll get it running smoothly in a couple of days. That much too much for one failing test in chrome.

@level420
Copy link
Member Author

OK so I'll create a PR which disables the failing test for chrome on linux.

@level420
Copy link
Member Author

The chrome travis runs succeed again with my PR. See https://travis-ci.org/qooxdoo/qooxdoo/builds/161873683

johnspackman added a commit that referenced this issue Sep 27, 2016
…g-on-new-chrome

issue #9167 fix travis run failing on new chrome
@level420
Copy link
Member Author

Fixed via #9184

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Errors
Projects
None yet
Development

No branches or pull requests

2 participants