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

Registry code cleanup had to be reverted to fix perf tests #7893

Closed
danmoseley opened this issue Apr 17, 2017 · 7 comments
Closed

Registry code cleanup had to be reverted to fix perf tests #7893

danmoseley opened this issue Apr 17, 2017 · 7 comments
Labels
area-System.Runtime backlog-cleanup-candidate An inactive issue that has been marked for automated closure. bug help wanted [up-for-grabs] Good issue for external contributors no-recent-activity

Comments

@danmoseley
Copy link
Member

@JeremyKuhne
dotnet/coreclr#10983

Not sure whether this is necessary for 2.0 or not. Please set milestone to future if not.

@adiaaida supplied repro instructions offline, it seems not to obad so shouldn't take long to narrow down the problem in your change.

@JeremyKuhne
Copy link
Member

@adiaaida I assume this is because I stripped out reading perf keys? (Which isn't actually used in CoreLib directly.) Can you provide some details on the failure you were hitting?

@michellemcdaniel
Copy link
Contributor

The failure mode is that when we look at the etl files generated (and subsequently, the any other files that are supposed to have perf data in them), they are empty. This is what @jorive found when he was debugging: "I was debugging the xUnit Performance API, and I noticed on the BenchmarkEventSource (inherits from EventSource), when calling the IsEnabled() method, it always return false."

So basically, because of that, we don't get any of the event data when we run perf with your changes.

@JeremyKuhne
Copy link
Member

A repro would be helpful- I might have messed up my changes to EventProvider.GetDataFromController...

@gkhanna79
Copy link
Member

@danmosemsft what is the milestone for this?

@JeremyKuhne
Copy link
Member

Marked it as future- it was opportunistic.

@JeremyKuhne JeremyKuhne removed their assignment May 22, 2017
jkotas referenced this issue in jkotas/coreclr Sep 19, 2018
- Ensure that the registry keys are always disposed
- Use smaller subset of registry APIs
- Reduce diffs with CoreCLR/CoreFX
- Contributes to #11009 and #17899
jkotas referenced this issue in dotnet/coreclr Sep 19, 2018
- Ensure that the registry keys are always disposed
- Use smaller subset of registry APIs
- Reduce diffs with CoreCLR/CoreFX
- Contributes to #11009 and #17899
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@maryamariyan maryamariyan added the untriaged New issue has not been triaged by the area owner label Feb 26, 2020
@joperezr joperezr removed the untriaged New issue has not been triaged by the area owner label Jul 1, 2020
Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels Jan 1, 2025
Copy link
Contributor

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@dotnet-policy-service dotnet-policy-service bot removed this from the Future milestone Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Runtime backlog-cleanup-candidate An inactive issue that has been marked for automated closure. bug help wanted [up-for-grabs] Good issue for external contributors no-recent-activity
Projects
None yet
Development

No branches or pull requests

7 participants