Bug 1614855: Run valgrind builds in AWS r=froydnj a=Aryx
authorWander Lairson Costa <wander.lairson@gmail.com>
Wed, 12 Feb 2020 11:15:56 +0000
changeset 574972 1627ede858ca6c0d3308c3f164fb318952be2400
parent 574971 c0693d2fff714626b79eb8a2e0f5ed78c6e085fa
child 574973 1d1b989333f12ae74ce5c6cdfb5c52ce1cf5ef9c
push id2264
push userdluca@mozilla.com
push dateWed, 12 Feb 2020 16:25:54 +0000
treeherdermozilla-release@1627ede858ca [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersfroydnj, Aryx
bugs1614855, 1545094
milestone73.0.1
Bug 1614855: Run valgrind builds in AWS r=froydnj a=Aryx GCE instances use Ubuntu 18.04, which is known to cause issues in valgrind builds (Bug 1545094), while EC2 uses Ubuntu 14.04. Move valgrind builds back to GCE to avoid perma fail of these jobs. Differential Revision: https://phabricator.services.mozilla.com/D62552
taskcluster/ci/valgrind/kind.yml
--- a/taskcluster/ci/valgrind/kind.yml
+++ b/taskcluster/ci/valgrind/kind.yml
@@ -23,17 +23,17 @@ jobs:
         index:
             product: firefox
             job-name: linux64-valgrind-opt
         treeherder:
             platform: linux64/opt
             symbol: V
             kind: build
             tier: 1
-        worker-type: b-linux
+        worker-type: b-linux-aws
         worker:
             docker-image: {in-tree: valgrind-build}
             max-run-time: 72000
             env:
                 PERFHERDER_EXTRA_OPTIONS: valgrind
         run:
             using: mozharness
             actions: [get-secrets, build, valgrind-test]