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

artifacts returns Error from upload stream: rpc error: code = Unknown desc = #913

Closed
1 of 2 tasks
trombik opened this issue Sep 12, 2021 · 4 comments · Fixed by cirruslabs/cirrus-ci-agent#183
Closed
1 of 2 tasks
Assignees
Labels

Comments

@trombik
Copy link

trombik commented Sep 12, 2021

Expected Behavior

What should have happened is artifacts uploads files.

Real Behavior

What ended up happening was ...

the following snippet:

  packages_artifacts: |
    path: "packages/All/binutils-esp32ulp*"
    type: application/octet-stream

ends up with:

Error from upload stream: rpc error: code = Unknown desc = 

the pattern matches a file, binutils-esp32ulp-2.28.51.20191205.txz and the file is there. interestingly, similar artifacts just works (/tmp/cirrus-ci-build/logs/*.log)

see the log at https://cirrus-ci.com/task/5852421034344448?logs=packages#L1

Related Info

i am in no way a go expert, but, after following the source, i found grpc-go included suspicious PR in v1.38.1, while the agent is using 1.38.0.

https://github.com/grpc/grpc-go/releases/tag/v1.38.1

internal/transport: do not mask ConnectionError (#4561)

grpc/grpc-go#4561

maybe related?

This is a (tick one of the following):

  • Website issue
    • Link to page:
  • Task issue
    • OS: FreeBSD
    • Task name: build_task
    • Script/cache name (if applies): packages_artifacts
@trombik
Copy link
Author

trombik commented Sep 14, 2021

@edigaryev was it deployed?

@edigaryev
Copy link
Contributor

@edigaryev was it deployed?

It is now. Can you re-run it to see if anything changed?

@trombik
Copy link
Author

trombik commented Sep 16, 2021

the same job reports the same error message. aside from the issue, it's interesting that while the library reports the error, but the UI says none.

@trombik
Copy link
Author

trombik commented Sep 16, 2021

as pointed out in the PR, it was | that caused the issue.

wrong:

  packages_artifacts: |
    path: "packages/*"

correct:

  packages_artifacts:
    path: "packages/*"

@trombik trombik closed this as completed Sep 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants