-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Fix ci failures #2006
Fix ci failures #2006
Conversation
components/dash-core-components/tests/integration/calendar/test_date_picker_single.py
Show resolved
Hide resolved
Any idea how adding one package to dash-table caused its package-lock to get 6000 lines SMALLER? |
dash/testing/plugin.py
Outdated
action="store", | ||
default="tests/assets", | ||
help="configure how Percy will discover your app's assets", | ||
) |
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.
Does the new percy runner have a different way of collecting assets so it doesn't need this?
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.
I think that was specific to the old percy client, can't find something similar for the new one. Do you think it would be better to make the migrate in a separate PR with a proper percy baseline build to compare ?
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.
If they can make do without that it's way better... let's just verify that assets like images are in fact making it into the snapshots, and keep going.
f246801
to
b06c700
Compare
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.
💃 what a slog. Thanks for all the iterations @T4rk1n - let's see what Percy support says, whether there's a way for us to bring back their new SDK or not... for now at least this gets us onto the new rendered Firefox.
no_update
callbacks.pytest-rerunfailures
to automatically reruns flaky tests.