Closed Bug 1843347 Opened 1 year ago Closed 3 months ago

[meta] Reduce reliance on mozprocess ProcessHandler

Categories

(Testing :: Mozbase, task)

Default
task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gbrown, Assigned: gbrown)

References

Details

(Keywords: meta)

mozprocess is a complex module with many open bugs, but little active development. At the same time, many of the use cases for which mozprocess was developed can be easily and reliably addressed with modern subprocess. mozprocess is used extensively in mozilla-central, and is implicated in several longstanding intermittent failures.

Let's try to use mozprocess less -- convert mozprocess.ProcessHandler clients to subprocess directly, or to a simple subprocess shim accessed via a new mozprocess interface.

Depends on: 1408479
Depends on: 1839262
Depends on: 1843380
See Also: → 1845125
Depends on: 1846617
Depends on: 1846618
Summary: [meta] Reduce reliance on mozprocess → [meta] Reduce reliance on mozprocess ProcessHandler
Depends on: 1846619
Depends on: 1847841
See Also: → 1848637
Depends on: 1847164
Depends on: 1849892
Depends on: 1849982
Depends on: 1850789
Depends on: 1850832
Depends on: 1851715
Depends on: 1851717
See Also: → 1635776
Depends on: 1857647
Depends on: 1858451
Depends on: 1860170
Depends on: 1860671

I made a lot of progress in reducing use of mozprocess' ProcessHandler, but did not completely remove it. Some complicated uses of ProcessHandler remain, and I don't have a specific plan for addressing those cases. mozprocess' ability to stream process output without requiring the caller to wait is a useful and compelling feature; its child process management may also be superior to that of subprocess.

I leave it to others to decide whether ProcessHandler should be fully deprecated...or fixed?

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