-
Notifications
You must be signed in to change notification settings - Fork 2
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
Continuous testing should be mostly green #1106
Comments
I want check in on how I should interpret the above ... are the only sim-specific repos that currently need attention just the top 9 rows? Should ignore the 7/4 column? Or is 7/4 more accurate because it had more tests done and I should add those rows? (e.g. light versus dark shades). |
I fixed 3 separate CT issues today. I pushed a proposed fix for the acid-base-solutions CT error in phetsims/acid-base-solutions#174 |
I pushed a fix for phetsims/build-a-molecule#232 |
After the fixes, my local CT has been been pretty green, I'll put on hold and check again in the coming week. |
I also fixed phetsims/energy-forms-and-changes#416 |
Since last week, I have fixed or worked around 10 CT issues. I'll continue monitoring these as I have time. |
I kept an eye on this again this week and addressed several issues. |
Nov 17, 2022
|
Today I made some changes that added some metrics to each column, now we can see how many tests are complete and how many are failing: I hope this helps with this issue. There are ~40 problems on CT right now, but much of that is duplicated, and some of that is because of sparky weirdness that @jonathanolson and I are still sorting out over in https://github.com/phetsims/special-ops/issues/234. |
CT was mostly green for a while, closing. (We agreed on this as a developer meeting team). Nice work everyone! |
As discussed at today's dev meeting, we would like to invest more resources into getting CT to show more green more of the time so there is less trouble and less noise. This will take coordination from many developers in fixing sim-specific code, common code, etc, so it is an epic-level issue. I opened this so it can be triaged and scheduled for 2022 Q2.
The text was updated successfully, but these errors were encountered: