9abc87b416
* fix: always execute closeContainer() executor During our earlier refactoring in #984 we accidentally changed the behaviour in such a way that the `closeContainer()` executor was never called. This commit restores the earlier behaviour. Ref: * https://github.com/nektos/act/pull/984/files#diff-c057d66dc9657d8428e290c69871596e2b567bb8fecad62a99cab54398131a84L294 * https://github.com/nektos/act/pull/984/files#diff-ea9d5c93d769ef9b268932dd9990363e97fc3bec8a00114979d049bead5dd718R68 * test: add testcases to ensure job containers are started/stopped This commit adds tests to ensure that the executors of `startContainer`, `stopContainer`, `interpolateOutputs` and `closeContainer` are always called in the correct order. |
||
---|---|---|
.. | ||
res | ||
testdata | ||
action.go | ||
action_test.go | ||
command.go | ||
command_test.go | ||
expression.go | ||
expression_test.go | ||
job_executor.go | ||
job_executor_test.go | ||
logger.go | ||
run_context.go | ||
run_context_test.go | ||
runner.go | ||
runner_test.go | ||
step_context.go | ||
step_context_test.go |