Troubleshooting¶
Tips¶
Increasing Verbosity¶
Increasing verbosity may help you figure out what’s wrong. Use the --verbose option to trace your output.
To further increase verbosity, see the --verbose option, or use the --debug option.
Problems¶
My program completes successfully, but still has a non-zero exit code.¶
At the moment, you’ll need to fix your tool or wrap it in a script/executable that handles the error and returns a non-zero exit code.
Simplistically, the pattern (command) || true is often used in shell scripts, but this is not recommended. A script discerning from real
errors and spurious errors is required.
This is a common problem with a number of tools (e.g. mypy); and oftentimes, the tool itself should be fixed.
I see lines starting with ERROR OUTPUT: when running makex¶
Makex prefixes any errors written to the standard error output (stderr) by subprocesses with ERROR OUTPUT:. This helps identify problems quickly.
If you don’t want to see these messages, address the warnings, use a flag to quiet, or improve the executable you are trying to run.
Makex seems slow handling large files¶
Makex generates checksums of input/output files. At the moment, this is currently done in a single process.
It’s usually best to just wait for the file hashing to complete for the set of input files.
You may omit large output files from the Task’s outputs and this will prevent hashing them.
Makex hangs while running a command¶
NOTE: If a shell/execute/command waits for input, Makex will hang. This is by design. Several executables may be run in parallel, and it is indeterminable which one needs or will wait for standard input.
Repeat, all executables Makex runs must not require and wait user input (e.g. using readline()).
Some steps to debug a hang:
Increase your verbosity, to see which commands are run.
Find the last thing running before makex hangs. Stop/cancel Makex (usually ctrl+c, but may depend on terminal).
If it’s a shell/execute/command, check if running the command in another shell completes successfully.
If the command hangs or waits for input, you’ll need to figure out a way to make it run without waiting for input.
If the command completes, this may be a problem with Makex.
Makex hangs during copying a folder¶
This can happen if the folder or its contents has recursive symlinks.
Makex hangs, prints an exception, stack trace, or does something unexpected¶
Please send us a text copy of the output of the run with the --debug arguments enabled.
You may email this text as an attachment to makex@googlegroups.com or post it (as an attachment) using Google Groups.
I have some other problem¶
You may email them to makex@googlegroups.com or post it using Google Groups.