New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 709241 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

test failures on build125-b1 on chromium.perf Mac Air 10.11 Perf

Project Member Reported by martiniss@chromium.org, Apr 6 2017

Issue description

Several tests are failing on this bot, starting today. 
image_decoding.image_decoding_measurement
media.mse_cases
page_cycler_v2.intl_hi_ru

All three of these test failures look like this: https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/profiler-file-id_0-2017-04-06_05-28-0575569.png

It looks like somehow chrome failed to start. The log seems too spammy for me to extract any useful data from it.

cc-ing vhang, just because it could be a bot misconfiguration maybe?

Swarming task links:
https://chromium-swarm.appspot.com/task?id=355bbd6bdf917710&refresh=10&show_raw=1
https://chromium-swarm.appspot.com/task?id=355bbcd89db66d10&refresh=10&show_raw=1
https://chromium-swarm.appspot.com/task?id=355bbc9cd06a0110&refresh=10&show_raw=1
 
Cc: kbr@chromium.org erikc...@chromium.org
Erik, Ken: any idea what may be going on here from the Mac system log?

Comment 2 by kbr@chromium.org, Apr 6 2017

Not sure. There are errors coming from GoogleSoftwareUpdate, which seems suspicious but I don't think should block Chrome from launching.

We've seen intermittent failures to start Chrome for at least a few months in the Telemetry-based tests running on the GPU bots. In order to make progress we added retries of the browser launch to that other test harness. This is a poor solution and it would be better to get to the bottom this. However, without a minidump and stack trace it's impossible to guess what's happening.

Log excerpt:

Apr  6 04:12:45 build125-b1 ksadmin[616]: KSKeyedPersistentStore store directory does not exist. [com.google.UpdateEngine.CommonErrorDomain:501 - '/Library/Google/GoogleSoftwareUpdate/TicketStore' - 'KSKeyedPersistentStore.m:372']
Apr  6 04:12:45 build125-b1 ksadmin[616]: KSPersistentTicketStore failed to load tickets. (productID: com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain:1051 - '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore'] (KSKeyedPersistentStore store directory does not exist. - '/Library/Google/GoogleSoftwareUpdate/TicketStore' [com.google.UpdateEngine.CommonErrorDomain:501])
Apr  6 04:12:45 build125-b1 ksadmin[616]: ksadmin cannot access the ticket store:<KSUpdateError:0x100213f00
		domain="com.google.UpdateEngine.CoreErrorDomain"
		code=1051
		userInfo={
			function = "-[KSProductKeyedStore(ProtectedMethods) errorForStoreError:productID:message:timeoutMessage:]";
			date = 2017-04-06 11:12:45 +0000;
			productids = {(
				"com.google.Chrome"
			)};
			filename = "KSProductKeyedStore.m";
			line = 91;
			NSFilePath = "/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore";
			NSUnderlyingError = <KSError:0x100704800
				domain="com.google.UpdateEngine.CommonErrorDomain"
				code=501
				userInfo={
					date = 2017-04-06 11:12:45 +0000;
					line = 372;
					filename = "KSKeyedPersistentStore.m";
					function = "-[KSKeyedPersistentStore(PrivateMethods) validateStorePath]";
					NSFilePath = "/Library/Google/GoogleSoftwareUpdate/TicketStore";
					NSLocalizedDescription = "KSKeyedPersistentStore store directory does not exist.";
				}
			>;
			NSLocalizedDescription = "KSPersistentTicketStore failed to load tickets.";
		}
	>
Apr  6 04:12:45 build125-b1 ksadmin[617]: Using ticket store: <KSPersistentTicketStore:0x100606290 store=<KSKeyedPersistentStore:0x100607430
		path="/Users/chrome-bot/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore"
		lockFile=<KSLockFile:0x1003109e0
			path="/Users/chrome-bot/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore.lock"
			locked=NO
		>
	>>.

Looks like 4 failures in the last 1000 tasks on this bot.   Maybe a flake?
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 11 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by kbr@chromium.org, Apr 11 2018

Cc: perezju@chromium.org eyaich@chromium.org
Owner: nednguyen@chromium.org
Status: Assigned (was: Untriaged)
Assigning to Ned to close this out.

Comment 6 by kbr@chromium.org, Apr 11 2018

Labels: -Hotlist-Recharge-Cold

Sign in to add a comment