Closed
Bug 1634675
Opened 4 years ago
Closed 4 years ago
Remove webrtc-gtest
Categories
(Core :: WebRTC, enhancement, P2)
Core
WebRTC
Tracking
()
RESOLVED
FIXED
mozilla78
Tracking | Status | |
---|---|---|
firefox78 | --- | fixed |
People
(Reporter: dminor, Assigned: dminor)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
The webrtc.org gtests are not run in automation and have not proven to be very useful when doing local development. They aren't super useful when doing a libwebrtc update and we should be doing future libwebrtc feature development against tip and backporting, rather than developing against our local copy. They're basically just making the build take longer but not providing any value. For example of a build problem, see Bug 1630425.
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
Updated•4 years ago
|
Priority: -- → P2
Comment 3•4 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:dminor, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(dminor)
Pushed by nohlmeier@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/cad387b2d0b3
Remove webrtc-gtests r=drno,froydnj
Comment 5•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox78:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in
before you can comment on or make changes to this bug.
Description
•