I can't run tests

Challenges
1

When I run codecrafters test I get this error:
Initiating test run…

:hourglass_not_done: Turbo test runners busy. You are in queue.

Upgrade to skip the wait: Turbo test runs - CodeCrafters

Running tests. Logs should appear shortly…

CodeCrafters internal error: failed to get HEAD commit SHA: exit status 128. Output:
Try again? Contact us at hello@codecrafters.io if this persists.
unexpected submission status: error

We couldn’t fetch the results of your submission. Please try again?
Let us know at hello@codecrafters.io if this error persists.
unexpected submission status: error

I’ve tried everything from here: github - git status shows fatal: bad object HEAD - Stack Overflow

4

Hey @danilovict2, thanks for highlighting the issue! We’ll looked into it and update you when we have a fix.

5

@danilovict2 The issue was caused by **/.git in .dockerignore:

image
image1098×1334 144 KB

This line prevented Docker from copying .git into the image where your code runs.

I’ve removed it and pushed a few commits to your repo. You can run git pull to get the latest changes. Let me know if you’re still experiencing the issue!

7

Nope, that didn’t work for me. Although there is a new error:
Initiating test run…

:hourglass_not_done: Turbo test runners busy. You are in queue.

Upgrade to skip the wait: Turbo test runs - CodeCrafters

Running tests. Logs should appear shortly…

CodeCrafters internal error: failed to get HEAD commit SHA: exit status 128. Output: fatal: not a git repository (or any of the parent directories): .git

Try again? Contact us at hello@codecrafters.io if this persists.
unexpected submission status: error

We couldn’t fetch the results of your submission. Please try again?
Let us know at hello@codecrafters.io if this error persists.
unexpected submission status: error

8

And I’ve tried to do git init but that didn’t work

9

@danilovict2 Not sure how **/.git got back in .dockerignore. Could you try removing that line and give it another shot? Let me know how it goes!

10

It magically works now somehow, even though I did absolutely nothing.

1 Like
11

Oh, I just reset the test runner for your repo.

12

That’s great, thanks!

1 Like
13

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.

14

@danilovict2 We’ve made changes to our test runner to ignore .dockerignore before building images.

You can now use a .dockerignore in your repo without worrying about it interfering with the test runner.