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

Skip ddtrace profiling extension #1137

Merged
merged 2 commits into from
Nov 16, 2022
Merged

Skip ddtrace profiling extension #1137

merged 2 commits into from
Nov 16, 2022

Conversation

nkzou
Copy link
Contributor

@nkzou nkzou commented Nov 16, 2022

CI is failing due to the install of ddtrace failing. The install failure happens when building the extension, so this PR is for temporarily skipping the extension while apm-ruby investigates the root cause of the install failure.

@nkzou nkzou requested a review from a team as a code owner November 16, 2022 16:41
@nkzou nkzou merged commit e19e3ab into master Nov 16, 2022
@nkzou nkzou deleted the kevinzou/skip_ddtrace_ext branch November 16, 2022 16:50
github-actions bot pushed a commit that referenced this pull request Nov 16, 2022
* Skip ddtrace profiling extension e19e3ab
ivoanjo added a commit that referenced this pull request Nov 17, 2022
ivoanjo added a commit to DataDog/dd-trace-rb that referenced this pull request Nov 17, 2022
**What does this PR do?**:

In #2358 we changed how the profiling native extension is built in CI
by adding the `-Werror` compiler option to turn warnings into errors.

We did this automatically by checking if the `CI` environment variable
was set to `true`.

Unfortunately, this broke at least one user, see
<DataDog/datadog-api-client-ruby#1137>.
The warning that was triggered in that case was actually not
relevant, see my investigation in
<#2377>.

The `CI=true` was never meant to trigger outside of our CI, but
clearly it's too generic of a name for us to rely on that.

To fix this, I've gone ahead and changed the configuration so that
`-Werror` only gets added when `DD_PROFILING_CI=true`. I also
changed our docker and CircleCI configurations to set this by
default.

**Motivation**:

This issue affected one Datadog internal customer --
<DataDog/datadog-api-client-ruby#1137>.

This should never happen -- we don't want any issues when
compiling the profiling bits to affect ddtrace installation.

**Additional Notes**:

(Nothing)

**How to test the change?**:

Validate that `-Werror` only gets added when
`DD_PROFILING_CI=true`.

To trigger a warning for testing, try removing
`DDTRACE_UNUSED` from function argument declarations, and you
should see that the compiler starts failing due to that.

---

Fixes #2377
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants