Can someone explain to me the following error, which the tester expects to receive? Apparently my program returns the correct response, but the tester indicates that it receives only an empty string. [your-program] $ ls -1 nonexistent >> /tmp/foo/bar.md [tester::#UN3] Output does not match expecte…

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

Hi @ferwirrow , could you upload your code to GitHub and share the link? It will be much easier to debug if I can run it directly.

@ferwirrow Looks like you’ve got past this stage. Do you happen to remember what was wrong? Would love to see if we can improve the tester / instructions.

Error in Append stderr #UN3

Challenges

Topic		Replies	Views
Shell challenge,clarification in test case of #UN3 Append STDERR, tester is not expecting content in file mentioned as target for stderr appending for a command which gives error Challenges challenge:shell	2	62	June 13, 2025
Tests for Stage #UN3 (Redirection - Append stderr) Challenges challenge:shell	2	63	May 26, 2025
#UN3 \| Error final stage test \| Go Challenges challenge:shell	2	97	January 23, 2025
I am stuck at Stage #UN3 (Redirection - Append stderr). what is the problem? Challenges challenge:shell	3	94	November 25, 2025
[Go] [Builtin completion Stage #qp2] Redirection test of stdout fails after implementing raw terminal mode Challenges challenge:shell	7	93	April 16, 2025

Error in Append stderr #UN3

Related topics