-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Automated building fails since 2.12 #3878
Comments
As per this post (and others in the project), it is recommended to upgrade WebdriverIO to v5. |
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. |
Also ran into this. |
@BartVB I run into the same issue. I got no time looking into that (seems I need to upgrade WebdriverIO somewhere?) but i just wanted to point out that switching back to node v11.6.0 solves that issue. Hope that helps. |
Still fails with the node:latest Docker image (NodeJS v12.7). |
Failing for me too |
I got this on MacOS with node v12.10.0 too. Should this issue be reopened? |
I used "n" to install an alternate version of node with command "n 11.6.0" and made it default by using just "n" . Then rerun the command and it compiled fine. You can install n and use it with "npm i n" |
Installing build essentials for similar for your Linux variant seems to improve this as well. Node 11.15.0 seemed to be the last piece of the puzzle for me. |
Using the version from https://github.com/prebid/Prebid.js/blob/master/.nvmrc also works. Given that it is clearly the recommended version: nvm install Seems to be the way to go. |
In lieu of the above PR, I will be working on updating our version of webdriverio to 5 and implement the necessary changes in the e2e tests and config files (as there appear to be a few breaking changes from 4 > 5). I will create a new PR with the combined set of changes, which should allow us to use node 12. |
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. |
…ebid.js#3878) Fix drf port mapping Added note about applyDevData to README. If Demo is accessed without using applyDevData, a disabled veradmin will be created that will conflict with the initDev one.
…ebid.js#3878) Fix drf port mapping Added note about applyDevData to README. If Demo is accessed without using applyDevData, a disabled veradmin will be created that will conflict with the initDev one.
* updated docker-ui file to pull from node, commented out model import in init.py * Roll node version back to 11 to avoid "fibers" build error (prebid/Prebid.js#3878) Fix drf port mapping Added note about applyDevData to README. If Demo is accessed without using applyDevData, a disabled veradmin will be created that will conflict with the initDev one. * run instead of exec. Functions better as an independent command in the README * update authenticated logic in app component * Remove .vue processing from django-admin so that Vue mustache fields aren't affected. Co-authored-by: Andy Bryant <[email protected]>
* updated docker-ui file to pull from node, commented out model import in init.py * Roll node version back to 11 to avoid "fibers" build error (prebid/Prebid.js#3878) Fix drf port mapping Added note about applyDevData to README. If Demo is accessed without using applyDevData, a disabled veradmin will be created that will conflict with the initDev one. * run instead of exec. Functions better as an independent command in the README * rolled node back to 11, audited packages * update authenticated logic in app component * added templatetag verbatims to vue template strings * updated template tags with spacing * updated string template formatting and spacing Co-authored-by: Andy Bryant <[email protected]>
This should be fixed with Prebid.js 3.22.0 where a number of the packages were updated to support newer node versions. Closing this for now. |
…ebid.js#3878) Fix drf port mapping Added note about applyDevData to README. If Demo is accessed without using applyDevData, a disabled veradmin will be created that will conflict with the initDev one.
…ebid.js#3878) Fix drf port mapping Added note about applyDevData to README. If Demo is accessed without using applyDevData, a disabled veradmin will be created that will conflict with the initDev one.
Type of issue
Since Prebid 2.12, our automated building process has been failing. It runs on a GitLab worker with a Docker node:latest image.
Description
The culprit is the
fibers
module:Steps to reproduce
As far as I can tell, this module started to appear with the inclusion of the
wdio-mocha-framework
module.Other information
fibers
module in thewdio-mocha-framework
issues (already updated inwdio-sync
)The text was updated successfully, but these errors were encountered: