Skip to content

ci: harden windows static export readiness#403

Open
RedZapdos123 wants to merge 1 commit into
plotly:mainfrom
RedZapdos123:fix/windows-static-export-readiness
Open

ci: harden windows static export readiness#403
RedZapdos123 wants to merge 1 commit into
plotly:mainfrom
RedZapdos123:fix/windows-static-export-readiness

Conversation

@RedZapdos123
Copy link
Copy Markdown
Contributor

@RedZapdos123 RedZapdos123 commented Jun 2, 2026

Description:

A flaky windows-latest Chrome CI run timed out waiting for document.readyState during plot::tests::image_to_svg_string even though the page finished loading immediately afterward.

This PR slightly hardens the Windows-only static export readiness path by widening the Windows-only document.readyState wait and fixing the #plotly-html-element timeout loop so the timeout path behaves as intended.

Checklist:

  • I have run cargo +nightly fmt --all -- --check in WSL.
  • I have run cargo test -p plotly plot::tests::image_to_svg_string --features plotly_ndarray,plotly_image,static_export_chromedriver,debug -- --nocapture in WSL.

A flaky windows-latest Chrome CI run timed out waiting for document.readyState during image_to_svg_string even though the page finished loading immediately afterward.

Increase the Windows-only document readiness timeout and fix the plotly container wait loop so the timeout path behaves as intended.

Signed-off-by: Mridankan Mandal <xerontitan90@gmail.com>
@RedZapdos123 RedZapdos123 marked this pull request as ready for review June 2, 2026 09:09
@RedZapdos123 RedZapdos123 changed the title fix: harden windows static export readiness ci: harden windows static export readiness Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant