Skip to content
This repository has been archived by the owner on Aug 20, 2023. It is now read-only.

[BUG] 'npm test' times out #4399

Open
ProjectHSI opened this issue Dec 8, 2021 · 11 comments
Open

[BUG] 'npm test' times out #4399

ProjectHSI opened this issue Dec 8, 2021 · 11 comments
Labels
bug Something isn't working

Comments

@ProjectHSI
Copy link

ProjectHSI commented Dec 8, 2021

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

  1. Make a fork and clone that fork into a local directory.
  2. run 'npm test'

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.

@ProjectHSI ProjectHSI added the bug Something isn't working label Dec 8, 2021
@welcome
Copy link

welcome bot commented Dec 8, 2021

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)

picture of dog

@M-S-10
Copy link

M-S-10 commented Jan 15, 2022

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.

@ProjectHSI
Copy link
Author

lmao i didn't care about this repo in the first place
i just did it for twilioquest
the only """useful""" thing i did with this was make the pixel art display on a cozmo, and even that doesn't count as anything
useful (that's why i put it in quotes)

@ProjectHSI
Copy link
Author

also this isn't the pull request, this an issue related with the jest testing suite lol

@stale
Copy link

stale bot commented Apr 16, 2022

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 stale bot added the stale label Apr 16, 2022
@ProjectHSI
Copy link
Author

Stale keeper - not closed by admin

@stale stale bot removed the stale label Apr 17, 2022
@brianjpatterson
Copy link

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 )

@stale
Copy link

stale bot commented Sep 21, 2022

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 stale bot added the stale label Sep 21, 2022
@ProjectHSI
Copy link
Author

A

@stale stale bot removed the stale label Sep 29, 2022
@ProjectHSI
Copy link
Author

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 )

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.
Is this repo abandoned?

@ProjectHSI
Copy link
Author

@brianjpatterson

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants