chromium.fyi: Set min num of devices for swarmed x64 android tests.

chromium.fyi: Set min num of devices for swarmed x64 android tests.

The tasks aren't getting picked up because it defaults to 6 and the
swarming bots only have 1 available. (No clue why; I'll look at that later.)
This should at least get them running, albeit really slowly.

BUG=534815, 664190
Committed: https://crrev.com/7a9d577b4d27f64420d5a6a0b3e5e6c2bdcbf6b5
Cr-Commit-Position: refs/heads/master@{#436150}

[bpastene, 2016-12-03 00:39:38]

Description was changed from

==========
chromium.fyi: Set min num of devices for swarmed x64 android tests.

BUG=534815, 664190
==========

to

==========
chromium.fyi: Set min num of devices for swarmed x64 android tests.

The tasks aren't getting picked up because it defaults to 6 and the
swarming bots only have 1 available. (No clue why; I'll look at that later.)
This should at least get them running, albeit really slowly.

BUG=534815, 664190
==========

[bpastene, 2016-12-03 00:39:39]

bpastene@chromium.org changed reviewers:
+ thakis@chromium.org

[Nico, 2016-12-03 00:41:09]

lgtm if you think that's the way to go, but the Real Bug seems to be that
there's only one, and once that's fixed we need to revert this here again. So
not sure if this is worth it or not, up to you.

[bpastene, 2016-12-03 00:51:11]

On 2016/12/03 00:41:09, Nico wrote:
> lgtm if you think that's the way to go, but the Real Bug seems to be that
> there's only one, and once that's fixed we need to revert this here again. So
> not sure if this is worth it or not, up to you.

I've got my hands quite full atm, so yeah, I think this is best as a temporary
band-aid.

The weird thing is, the bots have been stuck at exactly 1 healthy device for a
steady week now (an improvement from 0!)
Maybe something's up with the usb hub. I'd like to investigate, but that might
not be for a while now.

[bpastene, 2016-12-03 00:52:47]

The CQ bit was checked by bpastene@chromium.org

[commit-bot: I haz the power, 2016-12-03 00:53:27]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-03 02:49:49]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1480726367573460, "parent_rev":
"4dee35ed66fabeb4f1797994a86ed088d35f4470", "commit_rev":
"f298f78e77b53d12ef3f9a0a35cc77850f1d6278"}

[commit-bot: I haz the power, 2016-12-03 02:50:21]

Description was changed from

==========
chromium.fyi: Set min num of devices for swarmed x64 android tests.

The tasks aren't getting picked up because it defaults to 6 and the
swarming bots only have 1 available. (No clue why; I'll look at that later.)
This should at least get them running, albeit really slowly.

BUG=534815, 664190
==========

to

==========
chromium.fyi: Set min num of devices for swarmed x64 android tests.

The tasks aren't getting picked up because it defaults to 6 and the
swarming bots only have 1 available. (No clue why; I'll look at that later.)
This should at least get them running, albeit really slowly.

BUG=534815, 664190
==========

[commit-bot: I haz the power, 2016-12-03 02:50:22]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-03 02:51:46]

Description was changed from

==========
chromium.fyi: Set min num of devices for swarmed x64 android tests.

The tasks aren't getting picked up because it defaults to 6 and the
swarming bots only have 1 available. (No clue why; I'll look at that later.)
This should at least get them running, albeit really slowly.

BUG=534815, 664190
==========

to

==========
chromium.fyi: Set min num of devices for swarmed x64 android tests.

The tasks aren't getting picked up because it defaults to 6 and the
swarming bots only have 1 available. (No clue why; I'll look at that later.)
This should at least get them running, albeit really slowly.

BUG=534815, 664190

Committed: https://crrev.com/7a9d577b4d27f64420d5a6a0b3e5e6c2bdcbf6b5
Cr-Commit-Position: refs/heads/master@{#436150}
==========

[commit-bot: I haz the power, 2016-12-03 02:51:47]

Patchset 1 (id:??) landed as
https://crrev.com/7a9d577b4d27f64420d5a6a0b3e5e6c2bdcbf6b5
Cr-Commit-Position: refs/heads/master@{#436150}

[Nico, 2016-12-05 16:39:59]

Looks like things are still unhappy after this:

https://build.chromium.org/p/chromium.fyi/builders/ClangToTAndroid%20x64/buil...

E    4.198s individual_device_set_up(238F7DFF)  Shard failed:
individual_device_set_up(238F7DFF)
Traceback (most recent call last):
  File
"/b/swarm_slave/w/irHIUUYf/build/android/pylib/local/device/local_device_environment.py",
line 55, in wrapper
    return f(dev, *args, **kwargs)
  File
"/b/swarm_slave/w/irHIUUYf/build/android/pylib/local/device/local_device_gtest_run.py",
line 303, in individual_device_set_up
    step()
  File
"/b/swarm_slave/w/irHIUUYf/build/android/pylib/local/device/local_device_gtest_run.py",
line 269, in install_apk
    self._delegate.Install(dev)
  File
"/b/swarm_slave/w/irHIUUYf/build/android/pylib/local/device/local_device_gtest_run.py",
line 124, in Install
    permissions=self._permissions)
  File
"/b/swarm_slave/w/irHIUUYf/third_party/catapult/devil/devil/android/decorators.py",
line 57, in timeout_retry_wrapper
    retry_if_func=retry_if_func)
  File
"/b/swarm_slave/w/irHIUUYf/third_party/catapult/devil/devil/utils/timeout_retry.py",
line 159, in Run
    error_log_func=error_log_func)
  File
"/b/swarm_slave/w/irHIUUYf/third_party/catapult/devil/devil/utils/reraiser_thread.py",
line 186, in JoinAll
    self._JoinAll(watcher, timeout)
  File
"/b/swarm_slave/w/irHIUUYf/third_party/catapult/devil/devil/utils/reraiser_thread.py",
line 158, in _JoinAll
    thread.ReraiseIfException()
  File
"/b/swarm_slave/w/irHIUUYf/third_party/catapult/devil/devil/utils/reraiser_thread.py",
line 81, in run
    self._ret = self._func(*self._args, **self._kwargs)
  File
"/b/swarm_slave/w/irHIUUYf/third_party/catapult/devil/devil/utils/timeout_retry.py",
line 152, in <lambda>
    child_thread = reraiser_thread.ReraiserThread(lambda: func(*args,
**kwargs),
  File
"/b/swarm_slave/w/irHIUUYf/third_party/catapult/devil/devil/android/decorators.py",
line 47, in impl
    return f(*args, **kwargs)
  File
"/b/swarm_slave/w/irHIUUYf/third_party/catapult/devil/devil/android/device_utils.py",
line 655, in Install
    reinstall=reinstall, permissions=permissions)
  File
"/b/swarm_slave/w/irHIUUYf/third_party/catapult/devil/devil/android/device_utils.py",
line 705, in _InstallInternal
    device_apk_paths = self._GetApplicationPathsInternal(package_name)
  File
"/b/swarm_slave/w/irHIUUYf/third_party/catapult/devil/devil/android/device_utils.py",
line 506, in _GetApplicationPathsInternal
    'pm path returned: %r' % '\n'.join(output), str(self))
CommandFailedError: (device: 238F7DFF) pm path returned: 'Error: Could not
access the Package Manager.  Is the system running?'
E    4.212s Main  Error occurred.
Traceback (most recent call last):
  File "/b/swarm_slave/w/irHIUUYf/build/android/test_runner.py", line 877,
in main
    return RunTestsCommand(args)
  File "/b/swarm_slave/w/irHIUUYf/build/android/test_runner.py", line 662,
in RunTestsCommand
    return RunTestsInPlatformMode(args)
  File "/b/swarm_slave/w/irHIUUYf/build/android/test_runner.py", line 819,
in RunTestsInPlatformMode
    str(iteration_count))
  File "/b/swarm_slave/w/irHIUUYf/build/android/pylib/base/environment.py",
line 33, in __exit__
    self.TearDown()
  File
"/b/swarm_slave/w/irHIUUYf/build/android/pylib/local/device/local_device_environment.py",
line 194, in TearDown
    self.parallel_devices.pMap(tear_down_device)
  File
"/b/swarm_slave/w/irHIUUYf/build/android/pylib/local/device/local_device_environment.py",
line 169, in parallel_devices
    return parallelizer.SyncParallelizer(self.devices)
  File
"/b/swarm_slave/w/irHIUUYf/build/android/pylib/local/device/local_device_environment.py",
line 160, in devices
    raise device_errors.NoDevicesError()
NoDevicesError: No devices attached.
ERROR:root:Logdog binary ./../../bin/logdog_butler unavailable. Unable to
upload logcats.

On Fri, Dec 2, 2016 at 9:51 PM, commit-bot@chromium.org via
codereview.chromium.org <reply@chromiumcodereview-hr.appspotmail.com> wrote:

> Patchset 1 (id:??) landed as
> https://crrev.com/7a9d577b4d27f64420d5a6a0b3e5e6c2bdcbf6b5
> Cr-Commit-Position: refs/heads/master@{#436150}
>
> https://codereview.chromium.org/2544223003/
>

-- 
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[bpastene, 2016-12-05 17:54:34]

Blehhh, why does this thing not want to work?

The test runner blacklists the only available device because "Error: Could not
access the Package Manager."

And yet swarming thinks the device is totally fine and continues triggering
tests onto it. So, something's wrong here....

I'll investigate when I get a chance (might not be for a while)