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

Issue with Publishing Artifacts #2009

Closed
ilyas1974 opened this issue Feb 12, 2024 · 6 comments
Closed

Issue with Publishing Artifacts #2009

ilyas1974 opened this issue Feb 12, 2024 · 6 comments

Comments

@ilyas1974
Copy link
Contributor

I am getting reports of an issue within the Publish Intermediate Artifacts step in runtime.

Error being seen:

This job was abandoned. We have detected that logs from the agent may have not finished uploading. We have included our in-memory record of all log lines uploaded before we lost contact with the agent: Starting: Publish intermediate artifacts

Build for Reference: https://dev.azure.com/dnceng/internal/_build/results?buildId=2376277&view=logs&j=46718cb1-cc84-5b44-d4ae-44c5afdef23a

@garath
Copy link
Member

garath commented Feb 12, 2024

Any feel for how widespread it is?

@ilyas1974
Copy link
Contributor Author

I do not believe it's too widespread at this time (couldn't find metrics about it in known issues) but would like to understand what going on - if its related to the work we recently did with the publishing pools.

@riarenas
Copy link
Member

riarenas commented Feb 12, 2024

Any reason to believe this isn't related to the other million issues with mac vms in the microsoft hosted pools? This amounts to "generic mac machine disconnect"

This is not related at all with the publishing pool, as this is not happening during publishing, so it's not using the publishing pool.

@riarenas
Copy link
Member

See #1886. This build was picked up by that known issue.

@epananth
Copy link
Member

This is already part of known issue, @ilyas1974 can I close this?

@ilyas1974
Copy link
Contributor Author

Absolutely - if this is being tracked elsewhere, let's close the duplicate.

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

No branches or pull requests

4 participants