Skip to content
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

CT has a number of grey cells and tests seem slow/not being done #148

Closed
KatieWoe opened this issue Jun 20, 2022 · 3 comments
Closed

CT has a number of grey cells and tests seem slow/not being done #148

KatieWoe opened this issue Jun 20, 2022 · 3 comments

Comments

@KatieWoe
Copy link

KatieWoe commented Jun 20, 2022

From Slack:

[Kathryn Woessner]
[1 hour ago]
CT looks like not many tests are being done (lots of grey cells). Is this an issue?
[Sam Reid]
[1 hour ago]
Maybe the lint failure is preventing builds?
[Kathryn Woessner]
[1 hour ago]
Should I make an issue somewhere?
[Sam Reid]
[1 hour ago]
Yes please. Perhaps in the aqua repo?

@samreid
Copy link
Member

samreid commented Jun 20, 2022

I'll try pulling aqua on CT.

UPDATE: CT commands are running very slowly, including logging in, authenticating, etc. I've been waiting 60+ seconds for pm2 stop continuous-server to complete.
UPDATE: I abandoned that command.
UPDATE: I was able to pull aqua anyways, even though it seems pm2 didn't stop/restart. That may correct the lint issue.
UPDATE: pm2 start continuous-server seemed to succeed.

Leaving assigned to @zepumph to see if there is a performance/storage issue on bayes.

UPDATE: I also noticed the lint problem was in a separate directory /data/share/phet/continuous-quick-server/aqua/js/patient-snapshotter.ts so I stop/pull/started there as well.

@samreid samreid removed their assignment Jun 20, 2022
@zepumph
Copy link
Member

zepumph commented Jun 24, 2022

I think this is likely related to @pixelzoom's post on slack, but things got worse over time. I made #150 to track it.

@zepumph zepumph removed their assignment Mar 3, 2023
@marlitas
Copy link
Contributor

@zepumph... this seems like we might be able to close? I can at least removed the automated-testing label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants