On Mon, 29 May 2023 at 16:37, Rebecca Cran <rebe...@bsdio.com> wrote: > > It looks like the agent or machine running the CI task crashed. > > "##[error]We stopped hearing from agent Azure Pipelines 18. Verify the > agent machine is running and has a healthy network connection. Anything > that terminates an agent process, starves it for CPU, or blocks its > network access can cause this error. For more information, see: > https://go.microsoft.com/fwlink/?linkid=846610"; >
Hmm, it would be nice if this thing could distinguish between 'error in your code' and 'internal error' where the latter does not mark your PR as being rejected. > > > > > The only way I've found to make CI run again is to do something to cause > the commit hash to change, for example by making a change to ReadMe.rst > then reverting it. > Mike Kinney mentioned last time that there is a button I could push. Mike? I am reluctant to make unnecessary changes to the state of the branch just to trick the CI into having another go at it. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#105384): https://edk2.groups.io/g/devel/message/105384 Mute This Topic: https://groups.io/mt/99199003/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
