"resource exhausted" in CI

Richard Eisenberg rae at cs.brynmawr.edu
Thu Jan 24 19:22:17 UTC 2019

Ah, yes -- I did push a rebase. OK: good to know that this is expected behavior after rebasing (makes sense).


> On Jan 24, 2019, at 2:01 PM, Ben Gamari <ben at smart-cactus.org> wrote:
> Richard Eisenberg <rae at cs.brynmawr.edu> writes:
>> Something is awry: https://gitlab.haskell.org/rae/ghc/-/jobs/16908 never got off the ground.
> It is possible that you pushed a rebase? This error generally means that
> the commit is no longer accessible which may happen when you push a
> rebase.
> I believe I cited the job for the current version of the patch [1] in my
> previous email. Note that the commit SHA is different between [1] and
> the job you cited.
> Cheers,
> - Ben
> [1] https://gitlab.haskell.org/rae/ghc/-/jobs/16913

More information about the ghc-devs mailing list