add additional "crucible log" command tests to the integration-tests …

[k-rister]

…action

[rafaelfolco]

wonderign what "force" means

[k-rister]

wonderign what "force" means

Part of what the run_cmd does is that by default it will only run the command if the job is still passing -- so if a job fails then future run_cmd invocations will skip running the command in order to "optimize" the runtime. The "force" parameter is used to modify that behavior and commands that have "force" set will run anyway. Commands that are short running and/or potentially useful for debugging purposes have "force" set so that they will always execute no matter what has previously happened.

The most obvious use case for "force" not being present is when there are multiple run commands present. If the first run command fails then skipping subsequent run commands can significantly reduce the runtime of the job.

Also, when "force" is set the logged commands will note that they were forced:

Which can be helpful in noticing where the actual failure happened. In this case you can work backwards from the first "forced" line (983) and find that the run command on line 795 is where the actual failure occured (lines 976, 978, and 981 are just logging entries and not run_cmd invocations: