You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been hitting our heads against a wall trying to get browser tests running on Jenkins with mocha and PhantomJS for our browser uploader. Basically, there is a known bug with PhantomJS where attaching a blob doesn't transfer the full file and fails to have correct content-length.
We were thinking about trying to run Chromium on linux in a headless mode to avoid the problems with PhantomJS.
We've seen your issue here and solutions here and here.
Would you be willing to upgrade this module to have a 'headless' option that runs chrome/chromium using xvfb?
The text was updated successfully, but these errors were encountered:
See also #20. This can be done already by starting an Xvfb window before you call karma (or npm-test, or grunt), and exposing the relevant DISPLAY environment variable.
To support this from within Karma, it would most likely have to be done within the core Karma framework. The launcher plugins just abstract discovery of the binary and configuration of relevant command line arguments. Not creation of the temp directory or launching of the process itself.
Hi there,
We have been hitting our heads against a wall trying to get browser tests running on Jenkins with mocha and PhantomJS for our browser uploader. Basically, there is a known bug with PhantomJS where attaching a blob doesn't transfer the full file and fails to have correct content-length.
We were thinking about trying to run Chromium on linux in a headless mode to avoid the problems with PhantomJS.
We've seen your issue here and solutions here and here.
Would you be willing to upgrade this module to have a 'headless' option that runs chrome/chromium using xvfb?
The text was updated successfully, but these errors were encountered: