Uh oh!
There was an error while loading. Please reload this page.
Make lttng-ust an optional dependency. - #113876
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
jkotas
commented
Mar 25, 2025
cc @dotnet/dotnet-diag |
tommcdon
commented
Mar 25, 2025
noahfalk
left a comment
There was a problem hiding this comment.
The principal that the build allows disabling lttng looked fine to me. I'll defer to @ViktorHofer and @jkoritzinsky on the specific --with-system-libs mechanism for signaling that.
I'm interested in renaming the feature flag to something like FeatureLttng, but thats probably better kept separate so that the change in the build isn't obscured by renaming.
tmds
commented
Mar 27, 2025
We discussed and concluded that using |
tmds
commented
Apr 1, 2025
tmds
commented
Apr 8, 2025
noahfalk
commented
Apr 8, 2025
I re-ran some tests because the build analysis reported that it had lost contact with one of the agents. I don't want to merge the code until build analysis is green. |
noahfalk
commented
Apr 10, 2025
tmds
commented
Apr 10, 2025
Looking at https://github.com/dotnet/runtime/pulls, I doubt we'll see a full pass. I'll take a look at the CI results when this run is complete. |
noahfalk
commented
Apr 10, 2025
Not every leg has to pass, just the 'Build Analysis' one. Build analysis does some work to try triaging known failures so its typical that GH will show a red X on the PR even though Build Analysis determines the PR is OK. As an example: #114459 |
tmds
commented
Apr 10, 2025
Build Analysis passed! |
noahfalk
commented
Apr 10, 2025
Done! :) |
Closes#107406.
@jkotas ptal.
cc @dotnet/distro-maintainers