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

Remove CORE_BPF available message on Power machines #1390

Merged
merged 2 commits into from
Oct 25, 2023

Conversation

Molter73
Copy link
Collaborator

@Molter73 Molter73 commented Oct 25, 2023

Description

When running on Power machines, we are wrongly printing a message stating that CORE_BPF is available on the platform, but we don't support it in code, so we shouldn't be printing the message. Additionally, setting CORE_BPF as the collection method should hard fail since it is unsupported.

Checklist

  • Investigated and inspected CI test results

Testing Performed

Will try to test this on a power VM, but the change is small enough that should be good enough to be merged as is IMO.

When running on Power machines, we are wrongly printing a message
stating that CORE_BPF is available on the platform, but we don't support
it in code, so we shouldn't be printing the message. Additionally,
setting CORE_BPF as the collection method should hard fail since it is
unsupported.
@Molter73 Molter73 requested a review from a team as a code owner October 25, 2023 09:05
ovalenti
ovalenti previously approved these changes Oct 25, 2023
Copy link
Contributor

@ovalenti ovalenti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me !

A pity that we have to get into such exception, but this definitely makes it clearer for the user.

@ovalenti ovalenti dismissed their stale review October 25, 2023 09:13

Afterthough, we probably should use a build-time check instead

@Molter73
Copy link
Collaborator Author

Afterthough, we probably should use a build-time check instead

This would be fine, but compile time checks are usually not as nice to read. If this was in a hot path or compilation absolutely depended on the change I'd 100% use a build-time check, but since this is not the case, I think an explicit runtime check is better.

@github-actions
Copy link

Kernel Method Without Collector Time (secs) With Collector Time (secs) Baseline median (secs) Collector median (secs) PValue

@Molter73
Copy link
Collaborator Author

Merging now since the integration tests will not be affected by this change and I'd like to start cutting our release.

@Molter73 Molter73 merged commit 286dbc9 into master Oct 25, 2023
36 checks passed
@Molter73 Molter73 deleted the mauro/prevent-core-on-power branch October 25, 2023 11:09
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.

3 participants