Skip to content

Conversation

@michellemcdaniel
Copy link
Contributor

For sourcelink validation, this change introduces retries.

For symbols validation, this change expands retry scenarios to any failure, not just 503s, as sometimes, dotnet-symbol fails with no real indication why, and we want to retry on all scenarios. Also updates the logging, and separates out the files being downloaded via dotnet-symbol to separate directories based on msdl/symweb, so we don't think we have those files on both when they only exist on one, as our method for confirming if they were downloaded just checked to see if certain paths exist.

Test run on runtime in validate-dotnet: https://dev.azure.com/dnceng/internal/_build/results?buildId=1131182&view=results

To double check:

For sourcelink validation, this change introduces retries.

For symbols validation, this change expands retry scenarios to any failure, not just 503s, as sometimes, dotnet-symbol fails with no real indication why, and we want to retry on all scenarios. Also updates the logging, and separates out the files being downloaded via dotnet-symbol to separate directories based on msdl/symweb, so we don't think we have those files on both when they only exist on one, as our method for confirming if they were downloaded just checked to see if certain paths exist.
@michellemcdaniel
Copy link
Contributor Author

@MattGal Can you take another look?

Copy link
Member

@MattGal MattGal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like it'd work, left a few more comments.

# Maximum number of jobs to run in parallel
$MaxParallelJobs = 16

$MaxRetry = 5
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: This variable could be plural since it represents a count of things.

$NumFailedLinks++
else {
break
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not touched in this PR, but looking down (~162?) there's a catch-all catch; could that log the exception it hits?

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

Successfully merging this pull request may close these issues.

2 participants