Skip to content

Remove unused samples.thread column#6151

Merged
mstange merged 1 commit into
firefox-devtools:mainfrom
mstange:push-xxpomkrrlpwz
Jul 13, 2026
Merged

Remove unused samples.thread column#6151
mstange merged 1 commit into
firefox-devtools:mainfrom
mstange:push-xxpomkrrlpwz

Conversation

@mstange

@mstange mstange commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Main | Deploy preview

This was added by the merging/diffing code and propagated in various places, but never actually read. There is a possibility that we may want to make use of this field in the future, but it's been many years and it hasn't happened, so let's just remove it for now. We can always add it back once we need it.

I noticed it because it ends up in the "compact" speedometer profiles from CI via profiler-edit --merge-non-overlapping-threads-by-name.

@mstange mstange requested a review from canova July 7, 2026 18:48
@codecov

codecov Bot commented Jul 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.49%. Comparing base (fe04f38) to head (31bd60e).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6151   +/-   ##
=======================================
  Coverage   83.49%   83.49%           
=======================================
  Files         344      344           
  Lines       36882    36870   -12     
  Branches    10241    10335   +94     
=======================================
- Hits        30793    30783   -10     
+ Misses       5661     5660    -1     
+ Partials      428      427    -1     

☔ View full report in Codecov by Harness.
📢 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.

@canova canova left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Ah weird. Yeah, I think we wanted to show which samples came from which thread at some point. But better to remove it.

Comment thread src/types/profile-derived.ts Outdated
Comment on lines +152 to +154
// Legacy: older profiles produced by merging may have a per-sample
// origin-thread column. Not written by current code, but tolerated on
// input so pre-existing profiles still parse.

@canova canova Jul 10, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we still need to keep these types here? Isn't it better to remove them so we can make sure that they are not used by mistake later?

Also this part of the comment doesn't make sense: "... but tolerated on input so pre-existing profiles still parse". We don't usually care if a table has extra columns.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Oh yes that comment indeed makes no sense.

I was torn on whether to remove the fields from the types. I thought that maybe in the future we might want to have an upgrader that takes that information from old profiles which had it... nevermind, typing it out I realize that this is not going to happen. It's rare for somebody to use the comparison view and even rarer that they would upload the comparison profile. I'll clean this up.

Comment thread src/types/profile.ts Outdated
// Legacy: older profiles produced by merging may have a per-sample
// origin-thread column. Not written by current code, but tolerated on
// input so pre-existing profiles still parse.
threadId?: Tid[];

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Same for this one.

@mstange mstange force-pushed the push-xxpomkrrlpwz branch from 7bc758e to e889c59 Compare July 10, 2026 21:22
@mstange mstange requested a review from canova July 10, 2026 21:23
This was added by the merging/diffing code and propagated in various
places, but never actually read. There is a possibility that we may
want to make use of this field in the future, but it's been many years
and it hasn't happened, so let's just remove it for now. We can always
add it back once we need it.
@mstange mstange force-pushed the push-xxpomkrrlpwz branch from e889c59 to 31bd60e Compare July 13, 2026 16:32
@mstange mstange enabled auto-merge July 13, 2026 16:32
@mstange mstange merged commit fbe5642 into firefox-devtools:main Jul 13, 2026
19 of 21 checks passed
mstange added a commit that referenced this pull request Jul 13, 2026
<!-- profiler-preview-links:start -->
[Main](https://main--perf-html.netlify.app/) | [Deploy
preview](https://deploy-preview-6174--perf-html.netlify.app/)
<!-- profiler-preview-links:end -->

The auto-rebase of #6151 over #6168 caused a typecheck failure and
auto-merge merged anyway. I've now added the "typecheck (ubuntu-latest)"
task to the required passing tasks in the branch protection rules so
this shouldn't happen again.
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.

2 participants