-
Notifications
You must be signed in to change notification settings - Fork 353
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
Remove bash dependency from init-compiler #11359
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dotnet/roslyn-infrastructure This is deleting eng system telemetry. Why was this telemetry added in the first place? Are we ok with deleting it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it was added to satisfy validation in
eng/configure-toolset.sh
, that has an ignore list which I have updated below.Note that when we invoke
build.sh
in runtime and diagnostics repos, which call multiple scripts before reachinginit-compiler.sh
, we use plainecho
orprint
commands in all those scripts. This script only has a few error cases, which we don't encounter in the CI, so I replacedWrite-PipelineTelemetryError
withecho
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do not encounter these error cases in the CI when everything is working correctly. We may encounter these error cases in the CI on infrastructure updates or when things break for some reason. IIRC, it is why this telemetry was added in the first place - to allow eng system team to see that there is a problem in some repo after the update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When it was added, this script was only used by arcade cmake SDK. I deduplicated that code in dotnet/runtime#59018 just to avoid duplication and not for telemetry. The one invovled in the build had no stake in telemetry data. I don't think out of all the other possible errors in 20+ scripts involved in the build (which use
echo
), there is anything special about the few in this script.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I agree with @am11, the telemetry here is not super valuable, I've never actually seen it reporting a failure.
@am11 would you mind resolving the merge conflicts? I think this is good to go.