Is it possible to get some help debugging this issue? My code can run from the first pipeline stage to GP4 without issue, but I can no longer pass even the first stage even though I used to be able to back in February. Did something change? I now fail even the first stage with Expected prompt (“$ “) but received “” I added a few additional logs to show that the test harness did not even finish compiling the program before the error prompt came in in the screenshot. Thanks!
Hey @Spiderpig86, could you upload your code to GitHub and share the link? It will be much easier to debug if I can run it directly.
I did some more testing with the test harness and I still can’t seem to pinpoint the issue. I was able to pass the first stage again by putting an artificial delay of 5 seconds in ShellExecutable start().However, there are more failures existing test cases I used to pass
I was able to make modifications to my program and was able to pass the tests locally. For some reason I can’t pinpoint what is delaying on the test runner. Either the compilation takes too long or the program is still not starting up in time (but I set the timeout from 15 → 5 seconds locally and it passes just fine)
Just tried resetting my own branch back to the setup you have here: build-your-own-shell/solutions/go/01-oo8/code at main · codecrafters-io/build-your-own-shell · GitHub
codecrafters test --previous still fails regardless if the only file I have left is main.go and all it does is print something. Is there something wrong with go-1.22? I can get the tester to run successfully locally but it doesn’t work remotely.
@Spiderpig86 Were you able to resolve the issue? I cannot access your repo on GitHub.
I have not been able to resolve it. The test runner runs the program fine locally but not remotely on your servers. I have made the repo available again.
1 Like
@Spiderpig86 It looks like the issue was caused by the old Go v1.22 setup.
I’ve now upgraded the buildpack for your repo to v1.24 and pushed a new commit to it. You can run git pull to sync the changes.
Let me know if the issue persists!
Ty! This issue has been resolved.
1 Like
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.