I’m stuck on Stage #(IP1). The test used to pass but now always fails I even tried to checkout to the same commit that used to pass and it still fails!! Here are my logs: [tester::#IP1] Running tests for Stage #IP1 (Run a program) [tester::#IP1] Running ./your_shell.sh [your-program] $ my_exe Emi…

OK I found the problem I was populating the executable apparently before the command is created by the tester so when it gets tested it isn’t found, The current hack is to repopulate the the executable every time before invoking every command though it’s pretty inefficient but works for now I guess.…

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

Thanks for sharing your code! I’ll take a look and get back to you by the end of the week.

Thank you so much! I wasted way to much time on this xD I looked through all paths on startup and my_exe did not exist. Now I do it when the first command is run and the tests pass… :sweat_smile:

(Rust) "Build your own shell" - Stage Run a program #IP1 always fails despite working before

Challenges

omagdy7 December 17, 2024, 3:21pm 3

Yes here it is: GitHub - omagdy7/tiny-shell

#IP1 Python custom_exe command not found

Topic		Replies	Views
Test Case failing for #IP1 Challenges challenge:shell	5	168	December 21, 2024
Can't proceed with Tests due to tester using wrong path? Challenges challenge:shell	4	73	June 5, 2026
Using Command in Rust Challenges challenge:shell	2	87	July 8, 2025
Unclear instructions surrounding path resolution on #IP1 Challenges challenge:shell	8	308	June 4, 2024
Build your Own shell, The type builtin: executable files challenge Challenges challenge:shell	4	168	May 9, 2025

(Rust) "Build your own shell" - Stage Run a program #IP1 always fails despite working before

Related topics