Closed Bug 1139487 Opened 9 years ago Closed 9 years ago

Remove mozprocess.pid, mozprocess.wpk

Categories

(Testing :: Mozbase, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(firefox44 fixed)

RESOLVED FIXED
mozilla44
Tracking Status
firefox44 --- fixed

People

(Reporter: wlach, Assigned: parkouss)

References

Details

Attachments

(4 files)

These functions are known to be broken (see bug 1138759). For code in mozilla-central, we can just use psutil which is included there (nothing there uses mozprocess.pid right now though). The only other consumer of this code is talos. I'd just copy the relevant code into talos directly. If/when we move talos into mozilla-central, we can migrate it to use psutil as well.
This removes these functions from mozprocess.
Assignee: nobody → wlachance
Attachment #8573565 - Flags: review?(ahalberstadt)
obv this needs a try run, doing one
Attachment #8573566 - Flags: review?(jmaher)
Try run for mozbase unit tests and talos: https://treeherder.mozilla.org/#/jobs?repo=try&revision=e91dfac29c85
Attachment #8573565 - Flags: review?(ahalberstadt)
Attachment #8573566 - Flags: review?(jmaher)
Unfortunately this approach doesn't work with Windows talos, as it requires compiling some parts of psutil which aren't supported in that environment. I assume this problem has somehow been solved for our other tests (probably by precompiling psutil and putting it in tests.zip), if we ever moved talos in-tree (bug 787200) we would be ok pushing this code. As it is, solving this in alternate ways probably isn't worth the effort. Let's just leave things as they are for now and maybe revisit in the future.
Not working on this at the moment.
Assignee: wlachance → nobody
See Also: → 787200
ok, psutil is working now, this might be worth revisiting.
Bug 1139487 - Remove mozprocess.pid usage from talos. r=jmaher
Attachment #8670445 - Flags: review?(jmaher)
Bug 1139487 - Remove mozprocess.pid, mozprocess.wpk. r=jmaher
Attachment #8670446 - Flags: review?(jmaher)
So, let's see how that goes - I ran a push try on the first patch only,

https://treeherder.mozilla.org/#/jobs?repo=try&revision=cb30fddb5d69

We should ensure that numbers are still consistent.

I tried with dxr to find all mozprocess.pid, mozprocess.wpk usage - seems to me like talos was alone. But maybe a full push to try would be good here to be sure ?
Assignee: nobody → j.parkouss
Status: NEW → ASSIGNED
Comment on attachment 8670446 [details]
MozReview Request: Bug 1139487 - Remove mozprocess.pid, mozprocess.wpk. r=jmaher

https://reviewboard.mozilla.org/r/21367/#review19253

this is nice!
Attachment #8670446 - Flags: review?(jmaher) → review+
Attachment #8670445 - Flags: review?(jmaher) → review+
Comment on attachment 8670445 [details]
MozReview Request: Bug 1139487 - Remove mozprocess.pid usage from talos. r=jmaher

https://reviewboard.mozilla.org/r/21365/#review19255

this is more of a rubber stamp, this change confuses me, not the change, just the code it is in!
So, we should be good, looking at talos results there are no obvious changes:

https://treeherder.mozilla.org/perf.html#/compare?originalProject=mozilla-inbound&originalRevision=d01dd42e654b&newProject=try&newRevision=cb30fddb5d69

So I should still run a try on the two patches just to be sure unit tests are good for each platform.
https://hg.mozilla.org/mozilla-central/rev/9d52d889c77b
https://hg.mozilla.org/mozilla-central/rev/c57207f4c801
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla44
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: