havior after rebasing (makes sense).
>>
>> Does not make sense (yet) to me.
>>
>> Can someone explain (and perhaps document) the workflow here?
>>
>> Simon
>>
>> | -Original Message-
>> | From: ghc-devs On Behalf Of Richard
>> | Eisenbe
e).
>
> Does not make sense (yet) to me.
>
> Can someone explain (and perhaps document) the workflow here?
>
> Simon
>
> | -Original Message-
> | From: ghc-devs On Behalf Of Richard
> | Eisenberg
> | Sent: 24 January 2019 19:22
> | To: Ben Gamari
&g
| Sent: 24 January 2019 19:22
| To: Ben Gamari
| Cc: GHC developers
| Subject: Re: "resource exhausted" in CI
|
| Ah, yes -- I did push a rebase. OK: good to know that this is expected
| behavior after rebasing (makes sense).
|
| Thanks,
| Richard
|
| > On Jan 24, 2019, at 2:01 P
Ah, yes -- I did push a rebase. OK: good to know that this is expected behavior
after rebasing (makes sense).
Thanks,
Richard
> On Jan 24, 2019, at 2:01 PM, Ben Gamari wrote:
>
> Richard Eisenberg writes:
>
>> Something is awry: https://gitlab.haskell.org/rae/ghc/-/jobs/16908 never got
>>
Richard Eisenberg 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
