Open bschilder opened 7 months ago
This seems strange since there hasn't been any changes to the telemetry action in >10 months. It's possible something changed with the GH runners themselves that caused the error. Or perhaps there was some temporary bug with the GH runners. I've checked the workflow file of @vjcitn and everything seems to be ok there.
Another possibility is that there's some weird interactions going on between the Docker container ghcr.io/bioconductor/bioconductor_salt:devel-jammy-bioc-3.19-r-4.4.0
and this particular action, though I have no idea what that might be.
Reached out to the telemetry action authors to investigate.
Potentially related Issues:
Got a suggested solution from the subaction authors: https://github.com/catchpoint/workflow-telemetry-action/issues/57#issuecomment-1916597573
Going to try see if this something I can implement in rworkflows
. In the meantime, this might be something you can add directly to your rworkflows.yml file @vjcitn
Additional examples of setting the "privileged" flag in GHA: https://github.com/actions/container-action/issues/2#issuecomment-854057781
1. Bug description
First brought to my attention by @vjcitn An error arises during the telemetry step in the rworkflows action.
Console output
https://github.com/tempbioc/parody/actions/runs/7700556648/job/20984649706
Expected behaviour
Telemetry actions runs all the way through and produces reports.
2. Reproducible example
https://github.com/tempbioc/parody/actions/runs/7700556648/workflow