|bvt-arc times out across boards|
|Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Dec 19||Back to list|
Filed by email@example.com on behalf of firstname.lastname@example.org The bvt-arc suite is timing out on quite a few boards. General symptoms: * There is a 15-60 minute gap between scheduling the tests and the first test starting. * Once the tests start, they seem to run normally. None fail. * The suite is aborted after a timeout. How far it gets before the timeout seems to be correlated with the length of the scheduling delay. Examples: - cave-release: https://luci-milo.appspot.com/buildbot/chromeos/cave-release/1775 - celes-release: https://luci-milo.appspot.com/buildbot/chromeos/celes-release/1772 - lulu-release: https://luci-milo.appspot.com/buildbot/chromeos/lulu-release/1776 - poppy-release: https://luci-milo.appspot.com/buildbot/chromeos/poppy-release/1029 - relm-release: https://luci-milo.appspot.com/buildbot/chromeos/relm-release/1775 - sentry-release: https://luci-milo.appspot.com/buildbot/chromeos/sentry-release/1773 - ultima-release: https://luci-milo.appspot.com/buildbot/chromeos/ultima-release/1777
Another one today: https://luci-milo.appspot.com/buildbot/chromeos/ultima-release/1780 Timeline: 4:46: 38 tests scheduled 5:15: First test starts running 6:21: 34th test finishes successfully 7:48: Suite is aborted because it times out. There are no log messages between 6:26 and 7:48. This sounds at least superficially similar to crbug.com/796439 .
A bunch more today: https://luci-milo.appspot.com/buildbot/chromeos/caroline-release/1325 https://luci-milo.appspot.com/buildbot/chromeos/cave-release/1785 https://luci-milo.appspot.com/buildbot/chromeos/relm-release/1785 https://luci-milo.appspot.com/buildbot/chromeos/setzer-release/1778 https://luci-milo.appspot.com/buildbot/chromeos/squawks-release/2067 https://luci-milo.appspot.com/buildbot/chromeos/terra-release/1787 https://luci-milo.appspot.com/buildbot/chromeos/wizpig-release/1791 There may be two separate bugs here, because the delay happens in two places: 1. A long delay between scheduling all the suites and starting the first test. These usually run until the timeout once they start. 2. Some of the tests run fairly soon after scheduling, and then there's a long delay with no output before the timeout.
|► Sign in to add a comment|