-
Notifications
You must be signed in to change notification settings - Fork 20.6k
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
Add tests certifying offset isn't broken after a recent revert #2909
Comments
mm, doesn't seem worth it, but okay |
Thanks. :) |
@markelog Those tests are broken on all browsers, both on |
This seems to be caused by using |
Also, I've noticed this only now but the variable to which you assign |
For some reason that does work with amd, that's reason i missed it.
I think it is fine as is. |
For some reason that works with `amd` but not with builded version Fixes gh-2909
For some reason that works with `amd` but not with builded version Fixes gh-2909
It's not stopping anything, it just notifies the test runner it's finished. It was called It's also almost universally called |
And that whole process is called stopping, whereas "stop" is synonym of "finish". I think we are free to choice the name of our variables as long as those names sufficiently reflects their purpose. |
Basically, we need tests certifying #2828 & #2836 work after the revert done in 49833f7. We should land them on all 3 branches.
The text was updated successfully, but these errors were encountered: