Skip to content

Conversation

@dmadisetti
Copy link
Collaborator

@dmadisetti dmadisetti commented Jan 5, 2026

📝 Summary

Pytest flakiness failures are related to timeout errors in windows. This reduces the number of frame calls needed (and hopefully) fixes the windows issues observed.

@vercel
Copy link

vercel bot commented Jan 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
marimo-docs Ready Ready Preview, Comment Jan 6, 2026 0:04am

@dmadisetti dmadisetti changed the title fix: address windows flakiness by reducting introspection calls fix: address windows flakiness by reducing introspection calls Jan 5, 2026
@dmadisetti dmadisetti mentioned this pull request Jan 5, 2026
4 tasks
mscolnick
mscolnick previously approved these changes Jan 5, 2026
Copy link
Contributor

@akshayka akshayka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved if CI failure is unrelated

@dmadisetti dmadisetti merged commit 968f3f8 into main Jan 7, 2026
32 of 48 checks passed
@dmadisetti dmadisetti deleted the dm/windows-pytest-timeout branch January 7, 2026 14:08
@github-actions
Copy link

github-actions bot commented Jan 7, 2026

🚀 Development release published. You may be able to view the changes at https://marimo.app?v=0.18.5-dev155

@mscolnick
Copy link
Contributor

@dmadisetti those ci failures look related to the change in pixi maybe?

@dmadisetti
Copy link
Collaborator Author

Ah dang. I though pixi lock lagged. I'm getting ✔ Lock-file was already up-to-date on main, so maybe a version mismatch

@mscolnick
Copy link
Contributor

it does not lag as far as i am aware, and yes seems like version mismatch

@dmadisetti dmadisetti added the bug Something isn't working label Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants