You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This affects our development speed and quality of our platform significantly. As things currently stand, this might even be more important than ripping out our NFS bottleneck for multi-node (and if not, it is just behind that).
I should be able to know if changes to this repository will affect the solvability of dojos.
We need an interface for dojos to declare testcases. This will need a mechanism for those testcases to be private, because probably most of the tests will be "does my solution script work?". And then we need infrastructure that runs those testscases against production.
Phase 1: Button that can be pressed to run CI
Phase 2: Run all the tests every night / after every update
Phase 3: Staging server to get a before-it-goes-live understanding
No seriously.
This affects our development speed and quality of our platform significantly. As things currently stand, this might even be more important than ripping out our NFS bottleneck for multi-node (and if not, it is just behind that).
I should be able to know if changes to this repository will affect the solvability of dojos.
We need an interface for dojos to declare testcases. This will need a mechanism for those testcases to be private, because probably most of the tests will be "does my solution script work?". And then we need infrastructure that runs those testscases against production.
Picture this ultra fancy system:
Make it all automatic and delete @zardus's keys. Bumo.
Seriously, we should at least get a system that supports phase 1.
The text was updated successfully, but these errors were encountered: