Stuck on multi-pipeline stage

Hey team,

I’m stuck on Stage #xk3

“it works on my machine” but on the runner I’m just getting '“remote: [tester::#XK3] Received: “” (no line received)” Sometimes.

Sometimes it will pass the first multi pipeline stage and fail the second time.

Was wondering if there is anything in particular that triggers the end of stage check that I should be looking for?

Here are my logs:

remote: [tester::#XK3] Running ./your_program.sh
remote: [your-program] $ cat /tmp/baz/file-90 | head -n 5 | wc
remote: [tester::#XK3] Didn't find expected line.
remote: [tester::#XK3] Expected: "       5       5      35"
remote: [tester::#XK3] Received: "" (no line received)
remote: [tester::#XK3] Assertion failed.
remote: [tester::#XK3] Test failed

Locally this works fine on multiple computers and runtimes:

➜  codecrafters-shell-csharp git:(master) ./your_program.sh
   ....

$ cat /tmp/baz/file-50 | head -n 5 | wc
      5       5      42
$ exit

My code is available here: GitHub - PaulLocksley/codecrafters-shell-csharp

I added lots of print logging and the runner just seems to disappear into the black hole somewhere with no information.
Any tips on on what triggers the runner to think the command has ended or if you can see any errors that aren’t surfaced with debug=true would be helpful.

Hey @PaulLocksley, I’ll take a look early next week.

I added lots of print logging and the runner just seems to disappear into the black hole somewhere with no information.

That usually means the program crashed, and the error message got swallowed somewhere along the way.

yeah, I was hoping with debug = true, I would get an trace, dump or a report if my program ends early but no luck. Is there anyway to trigger anything else?

Like I said I’ve tried a few environments and can’t get the same thing to happen. But I don’t have the same test harness.

@PaulLocksley Looks like Stage #BR6 (Pipelines - Dual-command pipeline) is failing as well:

You can re-run previous tests using our CLI:

codecrafters test --previous

yeah, I was hoping with debug = true, I would get an trace, dump or a report if my program ends early but no luck. Is there anyway to trigger anything else?

That flag only controls the verbosity of the tester’s logs. Unfortunately, some stages don’t have detailed output even with debug = true.

One thing you could try is comparing your current code with a previous version that successfully passed Stage #BR6.

Closing this thread due to inactivity. If you still need assistance, feel free to reopen or start a new discussion!

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