Media/WebRTC/Up-streaming Changes: Difference between revisions

Fix title
(Added RTC_CHECK)
(Fix title)
Line 14: Line 14:
* While [https://www.chromium.org/developers/testing/running-tests/ these instructions] are for running Chromium tests, the same process applies for libwebrtc. There is no facility to help you run all the tests, you need to run all the test binaries that are produced. There are no facilities for helping you identify which tests you should be running. Inserting an RTC_CHECK(false), can be useful for verifying that one is testing using the correct binary.
* While [https://www.chromium.org/developers/testing/running-tests/ these instructions] are for running Chromium tests, the same process applies for libwebrtc. There is no facility to help you run all the tests, you need to run all the test binaries that are produced. There are no facilities for helping you identify which tests you should be running. Inserting an RTC_CHECK(false), can be useful for verifying that one is testing using the correct binary.
==Submitting Code==
==Submitting Code==
==Opening An up-stream Bug===
==Opening An up-stream Bug==
* libwebrtc uses [http://webrtc-review.googlesource.com/ this Gerrit instance] to track bugs.
* libwebrtc uses [http://webrtc-review.googlesource.com/ this Gerrit instance] to track bugs.
===Submitting An up-stream Patch===
===Submitting An up-stream Patch===
===Requesting A Reviewer===
===Requesting A Reviewer===
===Asking For CI Runs===
===Asking For CI Runs===
==Tracking Progress==
==Tracking Progress==
There is a [https://docs.google.com/spreadsheets/d/1C9lg12ZQrctDU89zHB_bsni9pYTD7Ojos_7tq64Bjqs/edit#gid=0 spreadsheet] to track the progress of our in progress up-stream patches.
There is a [https://docs.google.com/spreadsheets/d/1C9lg12ZQrctDU89zHB_bsni9pYTD7Ojos_7tq64Bjqs/edit#gid=0 spreadsheet] to track the progress of our in progress up-stream patches.
139

edits