-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
cypress-split always uses average duration #267
Comments
Mind opening a PR with a test that shows the problem and the fix?Sent from my iPhoneOn Apr 12, 2024, at 07:49, Adam Bozzay ***@***.***> wrote:
I think this solves it, but probably it would make sense to revisit the specAbsoluteToRelative approach
image.png (view on web)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
I check if I can write a test that indicates the issue. The fix I suggested works, but I think it's more of a workaround. It's even possible that the best place for the fix is in find-cypress-specs. |
Any luck with this one ? :) hitting same thing. |
Hey, @bahmutov 👋 The issue is still relevant. I am currently investigating the I am using the test analytics db query to prepare ![]() Any opportunity to review and release the plugin new version with the @KleaTech suggested fix 🔝 ? |
cypress-split finds and reads the timings file correctly, but cannot find the individual specs in it. The reason is that the path in the timings file and the path that cypress-split compares with are different, see image.
The text was updated successfully, but these errors were encountered: