-
Notifications
You must be signed in to change notification settings - Fork 2
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
bump replay orchestrator launcher #310
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🤖 Meticulous replayed 1 user sessions and took 8 screenshots. Meticulous did not run on main of the main branch and so there was nothing to compare against. Please merge your pull request for setting up Meticulous in CI and ensure that it’s running on push events to the main branch. Test suite: test Meticulous with deployment url. Last updated for commit 8c50e28. This comment will update as new commits are pushed. |
✅ Meticulous spotted zero visual differences across 8 screens tested: view results. Test suite: test Meticulous with app url. Last updated for commit 8c50e28. This comment will update as new commits are pushed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if you already used it here, but Alex added a script that helps bump -- just run yarn bump-sdk-version
to bump too.
May be worth using it anyway to make sure that everything is bumped consistently across all packages?
I ran that in the monorepo but I don't think that script exists in report-diffs-action. Is it possible to execute that script from within this repo? |
Patch includes timeout on S3 download file call which should prevent replays from hanging.