I report this in the unlikely case that the team wasn’t aware of this, but running tests on the Go track have been taking way longer than the estimated 4s. So long, in fact, that the web editor threw a timeout error (refreshing a page after waiting some time does shows that the tests was eventually completed, though).
Has anyone else also experienced this?
Best.
Edit: I should probably provide some of the exercises and solutions where this occurs for me.
The estimated time is a track-level average set manually to give a baseline estimate. All solutions submitted to the test runner get the same 15 seconds for the tests to be run and results reported before a time-out is reported to the student. The test runner runs in the cloud and may not be running on machines as powerful as your local workstation so some deviation in runtime is to be expected. An occasional time out isn’t that unusual, and I’d give it a couple of minutes and try submitting again.
Based on the timestamp submission of OP, that was when our infrastructure had some hiccup. I was helping someone on discord and they keep running into time out, so I tested for the quick “Hello World” on python and it was also timed out. Things should be normal now.