Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote execution builds are failed on grpc status code UNAVAILABLE #1845

Open
abderrahim opened this issue May 26, 2023 · 7 comments
Open

Remote execution builds are failed on grpc status code UNAVAILABLE #1845

abderrahim opened this issue May 26, 2023 · 7 comments

Comments

@abderrahim
Copy link
Contributor

Trying to use remote execution to build, I often get these errors (often to the point I can't get a full build done, especially that there seems to be a bug in caching elements)

        [--:--:--] START   freedesktop-sdk.bst:components/pixman.bst: Uploading input root
        [00:00:09] SUCCESS freedesktop-sdk.bst:components/pixman.bst: Uploading input root
        [--:--:--] START   freedesktop-sdk.bst:components/pixman.bst: Waiting for the remote build to complete
        [00:01:00] FAILURE freedesktop-sdk.bst:components/pixman.bst: Waiting for the remote build to complete
        [00:01:09] FAILURE freedesktop-sdk.bst:components/pixman.bst: Running commands
        [00:01:12] FAILURE [87a4afe9] freedesktop-sdk.bst:components/pixman.bst: Failed contacting remote execution server at http://ab84137533a384b2ea288af9529636c2-1891086637.us-east-1.elb.amazonaws.com:8980.UNAVAILABLE/: Socket closed

Looking at the grpc documentation, the UNAVAILABLE status code should be retried.

@nanonyme
Copy link
Contributor

@nanonyme
Copy link
Contributor

@abderrahim are there any automated tests for RE?

@abderrahim
Copy link
Contributor Author

There are some tests indeed. See

btw, I had a patch to fix this (or at least work around it) but I don't remember if I ever opened a merge request.

@nanonyme
Copy link
Contributor

I couldn't see PR at least of brief look

@abderrahim
Copy link
Contributor Author

Yeah, it was just a side branch: 6205b41

@nanonyme
Copy link
Contributor

nanonyme commented Mar 17, 2024

I don't have test environment. I assumed it was correct to remove UNAVAILABLE from the set or statuses to raise for. Then if resume is not supported, lower condition raises as expected.

@nanonyme
Copy link
Contributor

@abderrahim in other words like #1901

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants