-
Notifications
You must be signed in to change notification settings - Fork 8.2k
[BUG] 'npm test' times out #4399
Comments
Thank you so much for opening your first issue in this project! We'll try to get back to it as quickly as possible. While you are waiting...here's a random picture of a corgi (powered by dog.ceo) |
Hey, I've created a pixel today at (y=4,x=10), tested it & pushed it to remote repo also. @ProjectHSI Assign me this issue or you can try for yourself with different value and make sure that they're unique. |
lmao i didn't care about this repo in the first place |
also this isn't the pull request, this an issue related with the jest testing suite lol |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please re-open the issue if this issue is still relevant. Thank you for your contributions. |
Stale keeper - not closed by admin |
pixel at 7x,8y = npm test timeout. It worked before that. I think it has something to do with the repo being out of sync, try to merge, or delete, create, merge your open commits/PRs whatever. (also just doing for video I'm making for my daughter of me playing twilio quest. :P ) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please re-open the issue if this issue is still relevant. Thank you for your contributions. |
A |
While it'd be great if we could merge it, only admins of the org / those that have write access can merge with the remote repo. Creating or deleting won't do any thing. |
Description
'npm test' times out, and with a 60000ms timeout time still times out, this is an issue with the repo, as it freezes on the mergePixels test.
Expected Behavior
The test should succeed
Actual Behavior
The test times out.
Steps to Reproduce
Context
Trying to make a pull request with a new pixel at 53, 0 [XY] with the correct name and all.
Notes
All other tests succeed.
The text was updated successfully, but these errors were encountered: