BuildStream-Migration-Bot opened a new issue #1392: URL: https://github.com/apache/buildstream/issues/1392
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/1392) In GitLab by [[Gitlab user @Qinusty]](https://gitlab.com/Qinusty) on Sep 3, 2020, 14:34 ## Summary [//]: # (Summarize the bug encountered concisely) Currently, the error message is simply "Failed contacting remote execution server at <URL>.". This can mean a wide range of things and doesn't really narrow down the problem. In my case, the problem was due to the platform properties not matching the server deployment. ## Steps to reproduce [//]: # (How one can reproduce the issue - this is very important) Force an UNNAVAILABLE GRPC response from the remote execution server. ## What is the current bug behavior? [//]: # (What actually happens) "Failed contacting remote execution server at URL." ## What is the expected correct behavior? [//]: # (What you should see instead) "Failed contacting remote execution server at URL: Internal GRPC error message" ## Relevant logs and/or screenshots [//]: # (Paste any relevant logs - please use code blocks ``` to format console output, logs, and code as it's hard to read otherwise. You can also add a Snippet and link it here. Check the markdown giude on Gitlab for further tips) https://gitlab.com/BuildStream/buildstream/-/jobs/718108839#L3472 is from a branch where I added temporary logging of the entire error. ## Possible fixes [//]: # (If you can, link to the line of code that might be responsible for the problem) Decide an appropriate level of detail to report and append it to the format string. https://gitlab.com/BuildStream/buildstream/-/blob/master/src/buildstream/sandbox/_sandboxremote.py#L218 ## Other relevant information [//]: # (Add the BuildStream version. Substitute below the "x" by "1", "2" or the right version. Add more than one version if necessary) * BuildStream version affected: master ---- ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
