actions: run: Set postprocess working directory to artifact directory

[obbardc]

Currently any run action tagged as postprocess will be ran in the recipe
directory. The artifacts are stored in this directory by default, unless
--artifactdir is passed to Debos to change where the artifacts are stored.

The run action documentation states:

postprocess -- if set script or command is executed after all other
commands and has access to the recipe directory ($RECIPEDIR) and the
artifact directory ($ARTIFACTDIR). The working directory will be set to
the artifact directory.

But this is wrong; currently the working directory of postprocess commands
is set to the recipe directory. Set the working directory to the artifact
directory instead to allow postprocess commands to be ran in the correct
location.

Fixes: #345
Closes: #617
Closes: #618
Closes: #619

[evelikov]

Adding the reproducer (or variant thereof) as a test case would be great.

[sjoerdsimons]

We should really ensure this get exercised in at least one of the tests

[sjoerdsimons]

@obbardc will you have to time to nudge this forward? the outstanding comments were quite small

[obbardc]

@obbardc will you have to time to nudge this forward? the outstanding comments were quite small

yes, I will be able to take a look at the beginning of March, along with my other outstanding PRs :-)

[obbardc]

Not sure what test I can write for this. Other than a run action with postprocess confirming the artifact dir. Any ideas @sjoerdsimons @daissi ?

[sjoerdsimons]

Not sure what test I can write for this. Other than a run action with postprocess confirming the artifact dir. Any ideas @sjoerdsimons @daissi ?

I think that's it right? Just confirming the postprocess cwd matches what you'd expect ? e.g. by writing an artifact in an action and then checking you can access in a postprocessing step

[Copilot]

@sjoerdsimons I've opened a new pull request, #617, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

@sjoerdsimons I've opened a new pull request, #618, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

@sjoerdsimons I've opened a new pull request, #619, to work on those changes. Once the pull request is ready, I'll request review from you.

[obbardc]

I've added the changes from #618 and #619 as a draft commit to see if the test works fine in CI. It will need squashing once it works.

[obbardc]

@sjoerdsimons added some fixes for the partitioning test; hope it's ok. Disabled auto merge so you can review before merging... Cheers!

[obbardc]

For some reason it fails as the image can't be found in artifactdir in CI (but of course it works locally). Added some test commits to check...

hmm, in the CI run, ls -la $ARTIFACTDIR returns:

2025/12/07 23:19:30 ==== test ====
2025/12/07 23:19:30 ls -la ${ARTIFACTDIR} | total 4
2025/12/07 23:19:30 ls -la ${ARTIFACTDIR} | drwxrwxrwt  4 root root   80 Dec  7 23:19 .
2025/12/07 23:19:30 ls -la ${ARTIFACTDIR} | drwxrwxrwt 15 root root  440 Dec  7 23:19 ..
2025/12/07 23:19:30 ls -la ${ARTIFACTDIR} | drwxr-xr-x  3 root root 4096 Dec  7 23:19 mnt
2025/12/07 23:19:30 ls -la ${ARTIFACTDIR} | drwxr-xr-x  2 root root   40 Dec  7 23:19 root

[obbardc]

For some reason it fails as the image can't be found in artifactdir in CI (but of course it works locally). Added some test commits to check...

hmm, in the CI run, ls -la $ARTIFACTDIR returns:

2025/12/07 23:19:30 ==== test ====
2025/12/07 23:19:30 ls -la ${ARTIFACTDIR} | total 4
2025/12/07 23:19:30 ls -la ${ARTIFACTDIR} | drwxrwxrwt  4 root root   80 Dec  7 23:19 .
2025/12/07 23:19:30 ls -la ${ARTIFACTDIR} | drwxrwxrwt 15 root root  440 Dec  7 23:19 ..
2025/12/07 23:19:30 ls -la ${ARTIFACTDIR} | drwxr-xr-x  3 root root 4096 Dec  7 23:19 mnt
2025/12/07 23:19:30 ls -la ${ARTIFACTDIR} | drwxr-xr-x  2 root root   40 Dec  7 23:19 root

OK, fixed it!