Key: |
QB-3224
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Critical
|
Assignee: |
Robin Shen
|
Reporter: |
AlSt
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 23/Jul/18 06:09 AM
Updated: 28/Feb/19 03:05 PM
|
|
|
Component/s: |
None
|
Affects Version/s: |
8.0.10
|
Fix Version/s: |
9.0.0
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Sometimes, more or less often, git fetch command executed by quickbuild fails with the following error message/response:
> 2018-07-12 09:43:48 - Failed to run command: git fetch --all --tags -q
> Command return code: 1
> Command error output: fatal: git fetch-pack: expected ACK/NAK, got 'A ref was requested that is no longer valid. The ref may have been updated while the git-upload-pack request was received. Please try again.'
> fatal: The remote end hung up unexpectedly
> error: Could not fetch origin
This is caused by the nature of the http(s) request used by git and modifications during these, which occurs more likely with increased action on a repository.
Quickbuild should follow the advice in the response and retry the fetch command automatically to avoid failures during CHECK_BUILD_CONDITION.
Basically this would make sense for every git command. If there is a "Please try again" contained in the message it really should try the command again.
|
Description
|
Sometimes, more or less often, git fetch command executed by quickbuild fails with the following error message/response:
> 2018-07-12 09:43:48 - Failed to run command: git fetch --all --tags -q
> Command return code: 1
> Command error output: fatal: git fetch-pack: expected ACK/NAK, got 'A ref was requested that is no longer valid. The ref may have been updated while the git-upload-pack request was received. Please try again.'
> fatal: The remote end hung up unexpectedly
> error: Could not fetch origin
This is caused by the nature of the http(s) request used by git and modifications during these, which occurs more likely with increased action on a repository.
Quickbuild should follow the advice in the response and retry the fetch command automatically to avoid failures during CHECK_BUILD_CONDITION.
Basically this would make sense for every git command. If there is a "Please try again" contained in the message it really should try the command again. |
Show » |
No work has yet been logged on this issue.
|
|