-
Notifications
You must be signed in to change notification settings - Fork 513
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
[Bug] Web based karma tests are no longer running #1135
Comments
@MSNev if you have it handy can you post the failure? If not i'll just run it myself |
…1135 ci: [Bug] DNS Lookup and Promise Lookup test for error NOT_FOUND failing open-telemetry#1136
The normal documented way to avoid this issue is to set the webpack
However, these options did not work for the contrib repo |
Is that a windows-specific issue? I ask because it didn't get caught during the initial PR to update to webpack 5. It's a bummer that we have to roll back to a previous testing version just for a single plugin. |
No it's not, it's just a little more obvious because of the drive letter embedded in the resulting path that it uses to understand what is going on. And in the contrib repo #1129 also hit it on a non-windows box #1129 (comment) |
Interesting. That looks really similar to an error I was having on macos with temp directories in the main repo with webpack 5. any idea why this has taken so long to be a problem? |
I think it's environmental, the main tests on GitHub seem to be passing. So it's really just as people start contributing their setup's (including mine) have issues with the defaults. |
What version of OpenTelemetry are you using?
Current rebase of the contribu repo
What version of Node are you using?
16.14.0
What did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: