Marco Ferrari

We can do either what you suggest, or control where the file path gets added using the `{}` token. `{}` is the way GNU Parallel uses to say `place the...

I can > Hmm, I thought it's as simple as > > ```diff > diff --git a/lib/functions/linterCommands.sh b/lib/functions/linterCommands.sh > index 352f3233..f26bdae9 100755 > --- a/lib/functions/linterCommands.sh > +++ b/lib/functions/linterCommands.sh > @@...

Ok, for `test-bash-exec-library-expect-success`, skipping the libraries is expected because they all have `bad` in their file name, on purpose.

This is for the "expect failures" case: ``` 2024-02-20T10:39:52.1979326Z 2024-02-20 10:39:11 [DEBUG] Started GitHub Actions log group: BASH_EXEC 2024-02-20T10:39:52.1980567Z 2024-02-20 10:39:11 [INFO] Linting BASH_EXEC items... 2024-02-20T10:39:52.1982069Z 2024-02-20 10:39:11 [DEBUG] PARALLEL_RESULTS_FILE_PATH...

Ah! I think I got the `environment: line 6: B: unbound variable` error. In `HasNoShebang`, you're calling the `debug` function, which depends on `${F[B]}` (which is an associative array): https://github.com/super-linter/super-linter/blob/947c92a513a48655c16e4d1c8e66accdeeca88f4/lib/functions/log.sh#L62...

Thanks @bewuethr ! Running workflows now.

Ok, new failure in the `Run test cases (test-bash-exec-library-expect-failure, super-linter-latest, standard)` job: ``` environment: line 28: CREATE_LOG_FILE: unbound variable ``` Can you please Add `export CREATE_LOG_FILE` in `log.sh`?

The two that are failing are: - `test/linters/bash_exec/shell_bad_1.sh`: this is expected - `test/linters/bash_exec/libraries/shebang_bad.sh`: this is also expected, I suppose? ``` 2024-02-23 11:29:24 [DEBUG] Parallel output file (/tmp/super-linter-worker-results-BASH_EXEC.json) contents for BASH_EXEC:...

@bewuethr I think we're good to go then. Anything else left to do?

> Just rebasing on latest **trunk** and squashing, I think! Ah! You just brought me back to SVN! :D