I saw this same error earlier too, and then my build got stuck. Seems like there’s some kind of outage with actions right now.

This looks like a bug. Looking into this. Will update soon. Thanks!

@davidjdixon @pixelmatrix Could you each send me the repository this is happening on (owner + name)?

mscoutermarsh AT github dot com.

Thanks :slight_smile:

Also running into this issue here https://github.com/qawolf/examples/commit/f3e2f49400e0f60d4bf495d5ccd55a60bd2cc7c1/checks

No problem. Done.

I’ve had this happen to me too.

You need to add new step:

- name: Create artifact dir
        run: |
          mkdir -partifacts

You means fixes this bug? Or you updates docs? Even that, Currently there are no way to remove artifacts to reclaim the storage.

I can’t use workflow to create archives right now because of that. Could you look at it asap?

Hi @mscoutermarsh, I’m still experiencing this issue. Could you provide more details on the resolution?

Stumbled into this issue today, super annoying… 

And I didn’t find any info on how to fix or why this is happening.

Interesting, so I figured out, that under https://github.com/settings/billing it says how much artifact space you have, it’s 1GB in my case, and I ran out of it. But I don’t see a way to delete artifacts…

Same here. Our team was already a bit over the limit, so I’m a bit confused why it only started giving errors now, after we’ve already been allowed to go over the limit and get charged.

I’m also very confused at how the cache action plays into this, especially since it has it’s own limit.

We’ve been caching test reports and failure screenshots, which are all farily small, so it’s strange that we hit over 2 GB of storage used, which is why I think the cache action (which caches our node_modules) might contribute to that. But again, it has it’s own limits, so I have no clue.

I am also seeing storage going up but no way to delete old artifacts.

Is this WIP?

For anyone still looking for a solution, there is a workaround. It might seem a bit dirty, but it works. Instead of pushing your artifacts using the upload-artifact, just push it to a special private repo. Worked just fine for me :slight_smile:

we are still getting this same problem on our private repo http://github.com/kylemath/EEGEdu

Please advise how to remedy