The Dr Memory toolchain is no longer supported by Chromium and
their bots have been removed. WebRTC will now rely on the LLVM
santizers for catching such errors.
BUG=webrtc:6553
NOTRY=True
R=ehmaldonado@webrtc.org
Review URL: https://codereview.webrtc.org/2434563003 .
Cr-Commit-Position: refs/heads/master@{#14703}
A recent build error on Android revealed that we're always doing
static builds for the Android Debug builders. This changes one
to be building shared library instead (is_component_build=true),
which should prevent such breakages in the future.
BUG=webrtc:6360
NOTRY=True
Review-Url: https://codereview.webrtc.org/2342033002
Cr-Commit-Position: refs/heads/master@{#14226}
This will unblock planned work on libsrtp and reduce the exposed GYP surface.
BUG=webrtc:5949
NOTRY=True
Review-Url: https://codereview.webrtc.org/2314473002
Cr-Commit-Position: refs/heads/master@{#14152}
These were used in the transition from GN->GYP.
NOTRY=True
BUG=webrtc:5949
Review-Url: https://codereview.webrtc.org/2310973003
Cr-Commit-Position: refs/heads/master@{#14087}
We need this for the bots to be functional in client.webrtc.fyi.
Right now they're not really working since runhooks no longer runs GYP
(nor GN), and the MB step is not yet enabled in this waterfall.
BUG=webrtc:6287
NOTRY=True
Review-Url: https://codereview.webrtc.org/2312733002
Cr-Commit-Position: refs/heads/master@{#14070}
Also, make explicit that the GYP build has limited support.
BUG=webrtc:6281
NOTRY=True
Review-Url: https://codereview.webrtc.org/2298143002
Cr-Commit-Position: refs/heads/master@{#13984}
Change the previous GN configs to build GYP instead
(since we'll keep GYP around for a while) but exclude tests
and examples for that config, since we'll only support the production
code for GYP.
Add new configs for upcoming rename of those bots to GYP instead
of GN.
BUG=webrtc:5949
NOTRY=True
TBR=ehmaldonado@webrtc.org
Review-Url: https://codereview.webrtc.org/2291443002
Cr-Commit-Position: refs/heads/master@{#13980}
Change the previous GN configs to build GYP instead
(since we'll keep GYP around for a while) but exclude tests
and examples for that config, since we'll only support the production
code for GYP.
Add new configs for upcoming rename of those bots to GYP instead
of GN.
BUG=webrtc:5949
NOTRY=True
Review-Url: https://codereview.webrtc.org/2277253002
Cr-Commit-Position: refs/heads/master@{#13946}
Change the previous GN configs to build GYP instead
(since we'll keep GYP around for a while) but exclude tests
and examples for that config, since we'll only support the production
code for GYP.
Add new configs for upcoming rename of those bots to GYP instead
of GN.
The Linux32 Debug/Release bots were removed a while back, so
their configs are removed as well.
BUG=webrtc:5949
NOTRY=True
Review-Url: https://codereview.webrtc.org/2277633005
Cr-Commit-Position: refs/heads/master@{#13935}
Change the previous GN configs to build GYP instead
(since we'll keep GYP around for a while) but exclude tests
and examples for that config, since we'll only support the production
code for GYP.
Add new configs for upcoming rename of those bots to GYP instead
of GN.
BUG=webrtc:5949
NOTRY=True
Review-Url: https://codereview.webrtc.org/2274713003
Cr-Commit-Position: refs/heads/master@{#13900}
When rolling Chromium into WebRTC, these fail to compile since chromium
no longer supports GYP.
BUG=webrtc:6252
NOTRY=True
Review-Url: https://codereview.webrtc.org/2275973003
Cr-Commit-Position: refs/heads/master@{#13892}
Change the previous GN configs to build GYP instead
(since we'll keep GYP around for a while) but exclude tests for
that config from now on, since we're facing errors with GYP.
Add new configs for upcoming rename of those bots to GYP instead
of GN.
BUG=webrtc:5949
NOTRY=True
Review-Url: https://codereview.webrtc.org/2264283003
Cr-Commit-Position: refs/heads/master@{#13875}
Turns out that if mb_type is missing in the JSON, GYP is run the
traditional way instead of having the MB configuration decide.
This turns on MB for those builders.
See https://codereview.chromium.org/2194703002 for how Chromium
switched from GYP->GN.
The JSON environment for GYP and GN is only used during runhooks
step since there are scripts that key on some of these environment variables.
The actual build that is compiled is defined by the MB config, which
is now updated to have component=static_library everywhere for iOS.
With this CL, all configs gets a full GYP+GN environment.
When flipping bots over to GN, the following line will need to be added
in addition to changing mb_type:
"additional_compile_targets": [ "all" ],
Goma was also enabled for all builders to reduce compile time.
BUG=589510
NOTRY=True
Review-Url: https://codereview.webrtc.org/2239643002
Cr-Commit-Position: refs/heads/master@{#13775}
I mistyped the name of the bot as 'linux_ubsan_clang_vptr'.
The real name is 'linux_ubsan_vptr'.
Also erase the libfuzzer bot, since it's alreading using GN.
BUG=589510
NOTRY=True
Review-Url: https://codereview.webrtc.org/2227043002
Cr-Commit-Position: refs/heads/master@{#13695}
The iOS GN bots are the only ones using MB, which seems to enable
Goma by default. Since Goma has started supporting autostart, disable
it for now until a goma start step is added to the bots.
BUG=chromium:617541
TBR=phoglund@webrtc.org
Review URL: https://codereview.webrtc.org/2045583002 .
Cr-Commit-Position: refs/heads/master@{#13049}
