Skip to content

Some WebGL jasmine tests start failing with Chrome 128 on master and other branches #7126

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

Closed
archmoj opened this issue Aug 22, 2024 · 1 comment · Fixed by #7129
Closed

Comments

@archmoj
Copy link
Contributor

archmoj commented Aug 22, 2024

That's the source of problem we (cc: @birkskyum) noticed in #6909 (comment).

Success yesterday:
https://app.circleci.com/pipelines/github/plotly/plotly.js/11164/workflows/627584e0-5d94-4566-acd6-79a85c7f66cf/jobs/246982

Fail today:
https://app.circleci.com/pipelines/github/plotly/plotly.js/11164/workflows/4411cbea-a676-48f4-a4e4-7fe4a388659a/jobs/247723

We should possibly pin down the version of Chrome in jasmine tests to have more robust/isolated testing environment.

@birkskyum
Copy link
Contributor

I quick local repro of this is to run npm run regl-codegen because it touches those areas of the code.

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