This is an archive of the discontinued LLVM Phabricator instance.

[standalone-build-x86_64] Increase timeout
AbandonedPublic

Authored by kwk on Jul 18 2022, 4:02 AM.

Details

Summary

I'm seeing this error on my standalone-build-x86_64 builder:

[Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.]

To be fair, the machine isn't particularly fast because we tried to get
the configuration right first before we invest to much money.

I hope this change fixes the error from above.

Event Timeline

kwk created this revision.Jul 18 2022, 4:02 AM
Herald added a project: Restricted Project. · View Herald Transcript
Herald added subscribers: jsji, pengfei. · View Herald Transcript
kwk requested review of this revision.Jul 18 2022, 4:02 AM

Hi Konrad,

“Connection to the other side was lost in a non-clean fashion.“ means the network connection went down. It has nothing to do with the timeout value you are trying to tweak.

Is it possible that your worker goes down or gets overloaded so much that it cannot handle network traffic? Like swapping memory perhaps? Or VM gets recycled?

kwk abandoned this revision.Jul 27 2022, 10:25 AM

I've found the error and now my worker is running fine since yesterday. I started the worker container in detached mode but quit the SSH session. This eventually caused the container to get a SIGTERM (143).