These tests don't need to be skipped.

testVariationArgs and testTelemetryUsesChromeClockDomain should be
handled by https://chromium-review.googlesource.com/c/1284756

Bug: 895977
Test: chromeos-amd64-generic-rel
Change-Id: I2627df526bfa56d5ae6e32d4954cb08c8f8c8378
Reviewed-on: https://chromium-review.googlesource.com/c/1289949Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#601030}

testing/buildbot/chromium.chromiumos.json

@@ -366,9 +366,7 @@
           "--browser=cros-chrome",
           "--remote=127.0.0.1",
           "--remote-ssh-port=9222",
-          "--xvfb",
-          "--skip=core.perf_benchmark_unittest.PerfBenchmarkTest.testVariationArgs",
-          "--skip=measurements.clock_domain_test.ClockDomainTest.testTelemetryUsesChromeClockDomain"
+          "--xvfb"
         ],
         "isolate_name": "telemetry_perf_unittests",
         "name": "telemetry_perf_unittests",

testing/buildbot/test_suites.pyl

@@ -463,9 +463,7 @@
           # By default, CrOS VMs' ssh servers listen on local port 9222.
           '--remote=127.0.0.1',
           '--remote-ssh-port=9222',
-          '--xvfb',
-          '--skip=core.perf_benchmark_unittest.PerfBenchmarkTest.testVariationArgs',
-          '--skip=measurements.clock_domain_test.ClockDomainTest.testTelemetryUsesChromeClockDomain',
+          '--xvfb'
         ],
         'swarming': {
           'hard_timeout': 1200,