There seems to be something wrong with the test cases for stage “The type builtin: executable files #MG5”. I can run the code fine in my local machine but when I push my changes (or use the CLI) I get a few errors. As other threads have pointed out, it seems to be fixed with finding executables …

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

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

Thank you! I’ve updated the code to make it a tad more organized in case I’ve missed something, but still shows the same errors.

The executable from the tester is created after the input, (it’s weird, I know) so you should source the commands inside PATH after.

Sorry, I’m a little lost on what you mean. Are you saying that the tester program is updating the PATH variable, but only after the program it’s testing runs? That seems strange… but anyway, how can I source it during program execution? Thanks!

The value of PATH doesn’t change during program execution, but the executables available on the filesystem can change after the shell has started. This is exactly how shells like bash/zsh can pickup a new program soon after you’ve installed it using something like brew install <program>. Your shell…

Right, that’s what I understood as well. I’m running a function separately on every loop iteration, not preloading anything. When I print the contents of the PATH variable I get this: /tmp/banana/banana/grape:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin For readability: /tmp/bana…

I’ve found the issue with the second error regarding the my_exe command… it was completely my own fault, as I didn’t realize that I was calling strtok one extra time before actually starting going over the directories, effectively removing the first element in the PATH variable… Sorry everyone …

Since /bin files are all symlink to /usr/bin binaries, you could exclude paths that start by /bin, maybe the tester doesn’t mind. You could also reverse iterate so that /usr/bin comes first.

That’s what I’ve been doing to get around this, yeah. In the code from my repository I removed it to keep it cleaner, but when testing and submitting the challenge I put it back in just for this purpose. Hope it can get fixed!

@D10f here’s a reference implementation of the find_command() function FYI: char *find_command(const char* cmd) { char *path_var = getenv("PATH"); if (path_var == NULL) { return NULL; // PATH not set } char *path_env = strdup(path_var); if (path_env == NULL) { r…

Tests won't pass on #MG5

Challenges

Topic		Replies	Views
Unclear instructions surrounding path resolution on #IP1 Challenges challenge:shell	9	301	June 9, 2024
I randomly get Stage #MG5 (The type builtin: executable files) error: my_exe not found Bug Reports challenge:shell	13	328	April 6, 2025
#MG5 Test Case Issue Challenges challenge:shell	2	112	October 16, 2025
Unable to pass the Step number 6 Challenges challenge:shell	5	111	April 6, 2025
Stuck on #MG5 (problem finding executables). Language JS/TS Challenges challenge:shell	8	133	December 18, 2025

Tests won't pass on #MG5

Related topics