Closed Bug 1828434 Opened 1 year ago Closed 7 months ago

Remote Protocol markers missing from profiles generated by Raptor

Categories

(Testing :: Raptor, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: davehunt, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxp])

The markers introduced by bug 1818080 are not appearing in the profiles generated by Raptor.

Example recent page load regression bug with linked profiles that are missing the markers: https://bugzilla.mozilla.org/show_bug.cgi?id=1827282

Example profile showing the markers: https://profiler.firefox.com/public/fvm2zn3ekxwqsthn0t8ah4rvh6kwgwdfgrh89mg/marker-chart/?globalTrackOrder=0w2&markerSearch=Remote-Protocol&thread=0&v=8

This issue can be reproduced locally using the following command, which will run one page load and open the profile: ./mach raptor -t welcome --gecko-profile --page-cycles 1

Severity: -- → S3
Priority: -- → P2
Whiteboard: [fxp]

(In reply to Dave Hunt [:davehunt] [he/him] ⌚GMT from comment #0)

This issue can be reproduced locally using the following command, which will run one page load and open the profile: ./mach raptor -t welcome --gecko-profile --page-cycles 1

I actually cannot see it locally when running the test on MacOS. The profile markers from Marionette are present. So I wonder what's different to your setup and especially the one that is used in CI.

Here my profile: https://share.firefox.dev/3GRdVUq

I tried to print the Marionette logs to the console but this doesn't work when setting the preference remote.log.level=Trace. Maybe the pref isn't correctly set via Raptor?

Blocks: dev-pain

I also tried to reproduce this issue and I can't see those markers locally either, so +1 on Henrik's findings. Considering that we can see the "Marionette: Command" markers that are added in the same patch but not the others, I think it's very unlikely that only a subset of markers are missing.

I also tried to dump to terminal to see if these marker's codes are reached, but I can't see any of the dump messages I wrote, which supports the hypothesis that these markers don't have any problem. Probably we don't really have BiDi related code running at that point.

I would suggest that we close this bug.

Dave, can you please re-check?

Flags: needinfo?(dave.hunt)

I don't see any "Remote-Protocol" markers with my original test:

./mach raptor -t welcome --gecko-profile --page-cycles 1

However, I do see them when I run a page load test:

./mach raptor -t google-docs --gecko-profile --page-cycles 1
Flags: needinfo?(dave.hunt)

I do perfectly see it for the welcome test: https://share.firefox.dev/3QGN1nt

Dave, did you maybe forgot to select the parent process? The markers are not present for web content processes.

Flags: needinfo?(dave.hunt)

Yep, I see it now. Thanks! Is the issue still present in our CI runs or should we close this as WORKSFORME?

Flags: needinfo?(dave.hunt)

When I open a profile as generated for the Amazon (profiled) job on mozilla-central I can see the markers correctly. So I think that we can close this bug.

Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.