runtime icon indicating copy to clipboard operation
runtime copied to clipboard

Git error when checking out repo

Open hoyosjs opened this issue 3 years ago • 5 comments

{
  "ErrorMessage": "Git fetch failed with exit code: 128",
  "BuildRetry": true
}

Report

Build Definition Step Name Console log
23613 dotnet/runtime Checkout dotnet/runtime@refs/pull/75806/merge to s Log
23600 dotnet/runtime Checkout dotnet/runtime@refs/pull/75806/merge to s Log
22894 dotnet/runtime Checkout dotnet/runtime@refs/pull/68610/merge to s Log
23584 dotnet/runtime Checkout dotnet/runtime@refs/pull/75142/merge to s Log
19771 dotnet/runtime Checkout dotnet/runtime@refs/pull/75612/merge to s Log
18394 dotnet/runtime Checkout dotnet/runtime@refs/pull/75421/merge to s Log
18382 dotnet/runtime Checkout dotnet/runtime@refs/pull/75678/merge to s Log
18361 dotnet/runtime Checkout dotnet/runtime@refs/pull/74754/merge to s Log
12641 dotnet/runtime Checkout dotnet/runtime@main to s Log
12634 dotnet/runtime Checkout dotnet/runtime@refs/pull/75012/merge to s Log
12665 dotnet/runtime Checkout dotnet/runtime@refs/pull/75443/merge to s Log
12670 dotnet/runtime Checkout dotnet/runtime@refs/pull/75443/merge to s Log
12648 dotnet/runtime Checkout dotnet/runtime@refs/pull/75181/merge to s Log
12643 dotnet/runtime Checkout dotnet/runtime@main to s Log
12016 dotnet/runtime Checkout dotnet/runtime@main to s Log
12025 dotnet/runtime Checkout dotnet/runtime@refs/pull/75421/merge to s Log
12024 dotnet/runtime Checkout dotnet/runtime@refs/pull/75421/merge to s Log
12022 dotnet/runtime Checkout dotnet/runtime@refs/pull/75421/merge to s Log
8965 dotnet/runtime Checkout dotnet/runtime@refs/pull/75284/merge to s Log
8964 dotnet/runtime Checkout dotnet/runtime@refs/pull/75284/merge to s Log
8684 dotnet/runtime Checkout dotnet/runtime@release/7.0 to s
6305 dotnet/runtime Checkout dotnet/runtime@main to s Log
6368 dotnet/runtime Checkout dotnet/runtime@refs/pull/74623/merge to s Log
3771 dotnet/runtime Checkout dotnet/runtime@refs/pull/75043/merge to s Log
3772 dotnet/runtime Checkout dotnet/runtime@refs/pull/75043/merge to s Log
3773 dotnet/runtime Checkout dotnet/runtime@refs/pull/75043/merge to s Log
3779 dotnet/runtime Checkout dotnet/runtime@refs/pull/74963/merge to s Log
3778 dotnet/runtime Checkout dotnet/runtime@refs/pull/74963/merge to s Log
2930 dotnet/runtime Checkout dotnet/runtime@refs/pull/74705/merge to s Log
2577 dotnet/runtime Checkout dotnet/runtime@refs/pull/74983/merge to s Log
1967931 dotnet/runtime Checkout dotnet/runtime@refs/pull/74614/merge to s Log
1968012 dotnet/runtime Checkout dotnet/runtime@refs/pull/74428/merge to s Log
1959664 dotnet/runtime Checkout dotnet/runtime@main to s Log
1959699 dotnet/runtime Checkout dotnet/runtime@refs/pull/74384/merge to s Log
1959487 dotnet/runtime Checkout dotnet/runtime@release/7.0-rc1 to s Log
1959541 dotnet/runtime Checkout dotnet/runtime@refs/pull/74378/merge to s Log
1959500 dotnet/runtime Checkout dotnet/runtime@refs/pull/74358/merge to s Log
1959455 dotnet/runtime Checkout dotnet/runtime@refs/pull/73055/merge to s Log
1959571 dotnet/runtime Checkout dotnet/runtime@release/7.0 to s Log
1959575 dotnet/runtime Checkout dotnet/runtime@refs/pull/74381/merge to s Log
1959224 dotnet/runtime Checkout dotnet/runtime@refs/pull/72896/merge to s Log
1959208 dotnet/runtime Checkout dotnet/runtime@refs/pull/74367/merge to s Log
1959279 dotnet/runtime Checkout dotnet/runtime@refs/pull/74371/merge to s Log
1957760 dotnet/runtime Checkout dotnet/runtime@refs/pull/74323/merge to s Log
1957759 dotnet/runtime Checkout dotnet/runtime@refs/pull/74323/merge to s Log

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
4 8 45

hoyosjs avatar Aug 22 '22 05:08 hoyosjs

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to this area: @dotnet/runtime-infrastructure See info in area-owners.md if you want to be subscribed.

Issue Details
{
  "ErrorMessage": "fatal: unable to access 'https://github.com/dotnet/runtime/': transfer closed with outstanding read data remaining",
  "BuildRetry": false
}

Report

Build Definition Step Name Console log
1957131 dotnet/runtime Checkout dotnet/runtime@refs/pull/74184/merge to s Log
1957760 dotnet/runtime Checkout dotnet/runtime@refs/pull/74323/merge to s Log
1957149 dotnet/runtime Libraries Build Linux_musl arm64 Release Log
1957759 dotnet/runtime Checkout dotnet/runtime@refs/pull/74323/merge to s Log
1957147 dotnet/runtime Libraries Build Linux arm64 Release Log

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
2 5 5
Author: hoyosjs
Assignees: -
Labels:

area-Infrastructure, untriaged, Known Build Error

Milestone: -

ghost avatar Aug 22 '22 14:08 ghost

@dotnet/dnceng FYI

hoyosjs avatar Aug 23 '22 03:08 hoyosjs

This appears to be a common issue when trying to clone many times at the same time, I think there's valuable info on this thread https://developercommunity.visualstudio.com/t/git-clone-fails-with-tf4000733-error-code-when-man/489440

dkurepa avatar Aug 23 '22 09:08 dkurepa

The messages are of the sort of fatal: could not read Username for 'https://github.com': terminal prompts disabled, fatal: unable to access 'https://github.com/dotnet/runtime/': transfer closed with outstanding read data remaining, and RPC issues. Not about This request was blocked because there are too many clones running at the same time.

hoyosjs avatar Aug 23 '22 16:08 hoyosjs

Why is this in the runtime repo -- wouldn't arcade be a better place? Is there anything specific to this repo?

danmoseley avatar Oct 06 '22 20:10 danmoseley

I think this issue is here because of the Known Build Error label and the Build Analysis check is then looking this up when this happens on PRs in this repo

premun avatar Oct 07 '22 07:10 premun

@premun the known build error system doesn't look at known build errors in the arcade repo as well? I would expect it to be quite common for a runtime PR to encounter a build error being tracked in arcade.

danmoseley avatar Oct 07 '22 13:10 danmoseley

Ah, apologies, I just found this one: https://github.com/dotnet/arcade/issues/9009

premun avatar Oct 07 '22 14:10 premun

OK, so shall we close this one as a duplicate? And any future such build errors in this repo, will be automatically associated with the arcade issue?

danmoseley avatar Oct 07 '22 14:10 danmoseley

Yeah, let's

premun avatar Oct 07 '22 14:10 premun