Closed
Bug 1479643
Opened 6 years ago
Closed 6 years ago
Remove assertion that binary path matches between recording and replaying
Categories
(Core Graveyard :: Web Replay, enhancement)
Core Graveyard
Web Replay
Tracking
(firefox63 fixed)
RESOLVED
FIXED
mozilla63
Tracking | Status | |
---|---|---|
firefox63 | --- | fixed |
People
(Reporter: bhackett1024, Assigned: bhackett1024)
References
Details
Attachments
(1 file)
850 bytes,
patch
|
mccr8
:
review+
|
Details | Diff | Splinter Review |
This assertion is bogus: we're comparing the binary path of the content process currently executing with the binary path of the content process used while recording, which we don't normally expect to match.
Attachment #8996167 -
Flags: review?(continuation)
Comment 1•6 years ago
|
||
Why won't they match? Aren't they the same executable?
Assignee | ||
Comment 2•6 years ago
|
||
(In reply to Andrew McCreight [:mccr8] (away Aug 6 - 10) from comment #1) > Why won't they match? Aren't they the same executable? Recordings should be portable between executables that are built from the same m-c revision (we don't have any checks for the revision, but will eventually). If a recording is made on one machine and then replayed on another (or in my case, another local copy of the same tree) then we'll hit this assert.
Comment 3•6 years ago
|
||
Comment on attachment 8996167 [details] [diff] [review] patch Review of attachment 8996167 [details] [diff] [review]: ----------------------------------------------------------------- Makes sense.
Attachment #8996167 -
Flags: review?(continuation) → review+
Pushed by bhackett@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/172b93b2f600 Remove assertion that binary path matches between recording and replaying, r=mccr8.
Comment 5•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/172b93b2f600
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Updated•4 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•