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

Optprof download diagnosability #3974

Merged

Conversation

rainersigwald
Copy link
Member

The MSBuild build broke as a result of the Microsoft organization moving to microsoft, which caused references to repo/branchname in OptProf artifact paths to change case, which resulted in empty query results on OptProf data (because it was published to, say, OptimizationData/Microsoft/msbuild/vs16.3 instead of OptimizationData/microsoft/msbuild/vs16.3, so the latter was empty).

I think it would have taken us less time to figure out what was going on if things were logged this way rather than the existing way. I had to dig into binlogs each time to figure out what was being queried.

In cases where the prefix is computed incorrectly, an official build failure
is hard to diagnose because the console messages and warnings did not contain
the queried path. Move the messages to an earlier point.
Create distinct errors for "no drops were found at all" and "no valid drops found".
@JohnTortugo
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@JohnTortugo
Copy link
Contributor

@rainersigwald - should this be merged?

@tmat
Copy link
Member

tmat commented Jan 31, 2020

BTW, the IBC data acquisition produces a log:

image

This log contains details of what was downloaded from where and how.

@rainersigwald
Copy link
Member Author

@JohnTortugo I'd say yes. I don't have permissions in this repo . . .

@jonfortescue
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jonfortescue
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jonfortescue
Copy link
Member

@rainersigwald checks are passing, I'm merging.

@jonfortescue jonfortescue merged commit d799f35 into dotnet:master Feb 27, 2020
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.

6 participants