Rob Cowsill

> To start, I'd like to make pull requests for two fixes that should resolve the signup test flakiness: Both these fixes were merged into `master` in c44bbd64cac539bb5d24f3c4a65025f7fc1690d2. The fix...

Just made PR #230 which adds video recording/upload to the github actions CI workflow. Video recording is off by default for local test runs, but can be activated like this...

Yes, it does look like the shared cache is causing the problem in the case above. That said, it's possible to get the same error on a single-job workflow if...

See discussion #97 for more detail on a proposed fix for this.

This error means the runner's SSD is filling up during the post run step. There's no way to avoid using the SSD, but you might be able to avoid the...

> I'm getting the same error here: [...] > Is it because I'm not specifying a key? That looks like the same issue as the OP; the [kuma_base Dockerfile](https://github.com/mdn/kuma/blob/master/docker/images/kuma_base/Dockerfile#L1) specifies...

> One thing to also consider is to keep support for specifying the tag AND the hash. I've just confirmed that docker does treat that form exactly the same as...

> When trying `master` > ``` > Run satackey/action-docker-layer-caching@master > ``` I think the version needs to be `master-release` (or maybe `latest`?) for that to work.

> Just tried again with v0.0.11 same result. > > https://github.com/DefectDojo/django-DefectDojo/runs/1584256485?check_suite_focus=true Running this workflow with ACTIONS_STEP_DEBUG set to `true` shows the following: ``` ##[debug]{"log":"getExistingImages", [...],"repotags":[[...],"mysql:", [...],"rabbitmq:", [...],"python:", [...]]} ``` This...

> The error also happens for us, using v0.0.11, see for example [this Actions run](https://github.com/pywbem/pywbemtools/runs/1828508609?check_suite_focus=true#step:3:1): In this case it looks like the cache really wasn't there. The previous run (teste2e#2)...