Skip to content

Backport parts of EventPipe PR 43711 not currently in C library.#46214

Merged
lateralusX merged 1 commit into
dotnet:masterfrom
lateralusX:lateralusX/backport-43711-eventpipe-c-lib
Jan 7, 2021
Merged

Backport parts of EventPipe PR 43711 not currently in C library.#46214
lateralusX merged 1 commit into
dotnet:masterfrom
lateralusX:lateralusX/backport-43711-eventpipe-c-lib

Conversation

@lateralusX

Copy link
Copy Markdown
Member

Backport of missing parts from #43711 , parts of this was already fixed in EventPipe C library when initially detected and reported as and issue in C++ library.

@lateralusX

Copy link
Copy Markdown
Member Author

/CC @josalem

@danmoseley

Copy link
Copy Markdown
Member

Our systems assume issues and PR's have exactly one area-XX label. If this applies to both, does area-System.Diagnostics.Tracing work well enough?

@josalem

josalem commented Dec 20, 2020

Copy link
Copy Markdown
Contributor

I don't think area-System.Diagnostics.Tracing matches for this. Now that we're combining the EventPipe implementation for mono and coreclr maybe we should add an area-tracing that isn't specific to mono or coreclr?

@danmoseley

Copy link
Copy Markdown
Member

I'm fine with that, your call. If you do make one you'll need to go back and relabel older issues as appropriate so that we can retrain the bot and it can apply it.

@josalem

josalem commented Jan 6, 2021

Copy link
Copy Markdown
Contributor

For now, I'm going to consolidate these changes under area-tracing-coreclr and we can add a new label later.

@lateralusX lateralusX merged commit 6b606df into dotnet:master Jan 7, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Feb 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants