Closed christophfroehlich closed 7 months ago
@fmauch have you had time to look into this?
I had only a quick look now.
I realized that the workflow is designed to cache the target_ws itself, before anything is checked out (happens in the ici step itself). This means, that the hash function returns an empty string. Does it make sense to cache the workspace at all, how much is the speed benefit compared to only caching ccache?
Maybe we should remove the workspace cache and avoid such strange cache errors.
Summarizing tests
name: Reusable test contexts
on:
workflow_call:
jobs:
reusable-test:
runs-on: ubuntu-latest
steps:
- run: |
echo "Reusable Github.job ${{ github.job }}"
echo "Reusable Github.workflow ${{ github.workflow }}"
name: Test contexts
on:
workflow_dispatch:
jobs:
test:
runs-on: ubuntu-latest
steps:
- run: |
echo "Github.job ${{ github.job }}"
echo "Github.workflow ${{ github.workflow }}"
call_reusable_test:
uses: ./.github/workflows/reusable_test_contexts.yml
gives
| Github.job test
| Github.workflow Test contexts
| Reusable Github.job reusable-test
| Reusable Github.workflow Reusable test contexts
--> github.workflow does not help here because we still don't get the name of the calling workflow.
I'll try to have a look tonight