Skip to content

Conversation

@fqueze
Copy link
Contributor

@fqueze fqueze commented Feb 7, 2025

gradle-profiler can generate profiles in the chrome-trace format, that we can import.

Here's an example profile using our current importer: https://share.firefox.dev/3Q4P7g0

Same profile imported with the PR applied: https://share.firefox.dev/3EplC5N

@codecov
Copy link

codecov bot commented Feb 7, 2025

Codecov Report

Attention: Patch coverage is 71.42857% with 4 lines in your changes missing coverage. Please review.

Project coverage is 85.83%. Comparing base (7f30744) to head (b992f12).
Report is 320 commits behind head on main.

Files with missing lines Patch % Lines
src/profile-logic/import/chrome.js 71.42% 4 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5360      +/-   ##
==========================================
- Coverage   85.84%   85.83%   -0.01%     
==========================================
  Files         312      312              
  Lines       29827    29835       +8     
  Branches     8213     8215       +2     
==========================================
+ Hits        25605    25610       +5     
- Misses       3627     3630       +3     
  Partials      595      595              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@fqueze fqueze force-pushed the import-gradle-profiler-chrome-trace branch from b992f12 to ffdba4a Compare July 30, 2025 13:34
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.

1 participant