search for: random_project

Displaying 4 results from an estimated 4 matches for "random_project".

2019 Feb 20
2
Clarification on expectations of buildbot email notifications
...many forms. They can link directly to an LLVM buildbot, > which should be self-explanatory as far as reproduction goes. It can be > an unreduced crash report. If they're nice, they can use CReduce to make > it smaller. But, a reverter can't just say "Revert rNNN, breaks > $RANDOM_PROJECT on x86_64-linux-gu". If they add, "reduction forthcoming" > and they deliver on that promise, I think we should support that. > > In other words, the bar to revert should be low, so we can do it fast > and save downstream consumers time and effort. If someone isn't ma...
2019 Feb 19
5
Clarification on expectations of buildbot email notifications
Hi all, Over the past year or so, all of us have broken the buildbots on many occasions. Usually we get notified on IRC, or via an buildbot email notification sent to everyone on the blamelist. If I happen to be on IRC I'll see the notification, but if not, the next best thing is an email that was automatically sent to me (along with everyone else on the blamelist) from the buildbot with
2019 Feb 20
2
Clarification on expectations of buildbot email notifications
...bug. This can take many forms. They can link directly to an LLVM buildbot, which should be self-explanatory as far as reproduction goes. It can be an unreduced crash report. If they're nice, they can use CReduce to make it smaller. But, a reverter can't just say "Revert rNNN, breaks $RANDOM_PROJECT on x86_64-linux-gu". If they add, "reduction forthcoming" and they deliver on that promise, I think we should support that. In other words, the bar to revert should be low, so we can do it fast and save downstream consumers time and effort. If someone isn't making a good faith e...
2019 Feb 20
2
Clarification on expectations of buildbot email notifications
...to an LLVM buildbot, > >> which should be self-explanatory as far as reproduction goes. It can be > >> an unreduced crash report. If they're nice, they can use CReduce to make > >> it smaller. But, a reverter can't just say "Revert rNNN, breaks > >> $RANDOM_PROJECT on x86_64-linux-gu". If they add, "reduction > forthcoming" > >> and they deliver on that promise, I think we should support that. > >> > >> In other words, the bar to revert should be low, so we can do it fast > >> and save downstream consumers...