bazelbuild / bazelbuild/reclient

Unable to start reproxy, context deadline exceeded

Open
#29 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
114
Forks
25
PR merge metrics
No merged PRs in 30d

Description

Hi, I'm using AOSP RBE 0.57.0.4865132 and buildfarm 2.4.0 to build.

Lately, Occasional failures occur, it‘s log like:
```
FAILED: RBE bootstrap failed with: exit status 1
E0116 11:54:26.839503 26020 bootstrap.go:98] Unable to start reproxy: ""
F0116 11:54:26.839852 26020 main.go:128] Error bootstrapping remote execution proxy: context deadline exceeded
```
I have two questions:
1. I'm not sure what's causing this, I guess the buildfarm is overloaded and RBE connect to buildfarm timeout,it's right?
2. I found that `bootstrap.StartProxyWithOutput()` has the `waitSeconds` param, can this error be reduced by increasing waitSeconds?
3. I know that the build will fallback to local when an exception occurs during connect to the remote execution server in bazel,but in AOSP RBE 0.57.0.4865132, in this case,the build will fail directly. Will fallback to the local be considered in the future?

Someone who can help me?

Contributor guide

Open the contributing guide

Research direction

Start with bootstrap.go around line 98 and main.go around line 128, then inspect bootstrap.StartProxyWithOutput and its waitSeconds parameter. Trace the context deadline failure and determine whether the issue is caused by proxy startup timing, whether increasing waitSeconds helps, and whether local fallback is expected; the issue does not name a test or a specific expected change.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.