Nick Desaulniers via llvm-dev
2020-Oct-21 18:16 UTC
[llvm-dev] failed assertion after e372a5f
Simon, idk if you have your email notifications from github turned off, but there's at least two reports on e372a5f about failed assertions; please address: https://github.com/llvm/llvm-project/commit/e372a5f86f6488bb0c2593a665d51fdd3a97c6e4#commitcomment-43425310 -- Thanks, ~Nick Desaulniers
Simon Pilgrim via llvm-dev
2020-Oct-21 20:33 UTC
[llvm-dev] failed assertion after e372a5f
This should have been fixed by the reversions by @mstorsjo finishing at rG4de215ff1877 I'm sorry about this - I've been having a few problems both with email and the new buildbot webview isn't refreshing properly for me so it hasn't been easy to see when one of my commits has caused reds. On 21/10/2020 19:16, Nick Desaulniers wrote:> Simon, > idk if you have your email notifications from github turned off, but > there's at least two reports on e372a5f about failed assertions; > please address: > https://github.com/llvm/llvm-project/commit/e372a5f86f6488bb0c2593a665d51fdd3a97c6e4#commitcomment-43425310 >
Nick Desaulniers via llvm-dev
2020-Oct-22 20:16 UTC
[llvm-dev] failed assertion after e372a5f
No worries, thanks! (I'll confirm the fix later) On Wed, Oct 21, 2020 at 1:33 PM Simon Pilgrim <llvm-dev at redking.me.uk> wrote:> > This should have been fixed by the reversions by @mstorsjo finishing at > rG4de215ff1877 > > I'm sorry about this - I've been having a few problems both with email > and the new buildbot webview isn't refreshing properly for me so it > hasn't been easy to see when one of my commits has caused reds. > > On 21/10/2020 19:16, Nick Desaulniers wrote: > > Simon, > > idk if you have your email notifications from github turned off, but > > there's at least two reports on e372a5f about failed assertions; > > please address: > > https://github.com/llvm/llvm-project/commit/e372a5f86f6488bb0c2593a665d51fdd3a97c6e4#commitcomment-43425310 > >-- Thanks, ~Nick Desaulniers