Skip to content

RUM-15307: Report failure through ProfilerCallback#3305

Merged
ambushwork merged 1 commit into
feature/continuous-profilingfrom
yl/profiling/add-on-failure-callback
Mar 31, 2026
Merged

RUM-15307: Report failure through ProfilerCallback#3305
ambushwork merged 1 commit into
feature/continuous-profilingfrom
yl/profiling/add-on-failure-callback

Conversation

@ambushwork

Copy link
Copy Markdown
Member

What does this PR do?

  • Add onFaliure() into ProfilerCallback so that any failure of app launch profiling is reported to ContinuousProfilingScheduler, in order to notify it the app launch profiling has completed.

Motivation

RUM-15307

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Make sure you discussed the feature or bugfix with the maintaining team in an Issue
  • Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

@ambushwork
ambushwork force-pushed the yl/profiling/add-on-failure-callback branch from 8f2dec5 to f779a95 Compare March 30, 2026 14:52
@codecov-commenter

codecov-commenter commented Mar 30, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 86.36364% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 71.50%. Comparing base (ce821f2) to head (f779a95).
⚠️ Report is 2 commits behind head on feature/continuous-profiling.

Files with missing lines Patch % Lines
...dog/android/profiling/internal/ProfilingFeature.kt 66.67% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@                       Coverage Diff                        @@
##           feature/continuous-profiling    #3305      +/-   ##
================================================================
- Coverage                         71.52%   71.50%   -0.02%     
================================================================
  Files                               947      947              
  Lines                             34967    34976       +9     
  Branches                           5924     5927       +3     
================================================================
  Hits                              25009    25009              
- Misses                             8283     8298      +15     
+ Partials                           1675     1669       -6     
Files with missing lines Coverage Δ
...id/profiling/internal/perfetto/PerfettoProfiler.kt 92.20% <100.00%> (+1.02%) ⬆️
...dog/android/profiling/internal/ProfilingFeature.kt 71.62% <66.67%> (-1.24%) ⬇️

... and 38 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ambushwork
ambushwork marked this pull request as ready for review March 30, 2026 14:54
@ambushwork
ambushwork requested review from a team as code owners March 30, 2026 14:54

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f779a95920

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@datadog-prod-us1-3

This comment has been minimized.

0xnm
0xnm previously approved these changes Mar 31, 2026
@ambushwork
ambushwork force-pushed the yl/profiling/add-on-failure-callback branch from f779a95 to 2b44b3b Compare March 31, 2026 07:27
@ambushwork
ambushwork merged commit 1c7d590 into feature/continuous-profiling Mar 31, 2026
26 checks passed
@ambushwork
ambushwork deleted the yl/profiling/add-on-failure-callback branch March 31, 2026 09:23
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