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

Issue 632184 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug

Blocking:
issue 640994



Sign in to add a comment

ExtensionWelcomeNotificationTest.* failing on win10

Project Member Reported by wfh@chromium.org, Jul 27 2016

Issue description

Version: de2f4dd379a9de9153985a6e3a5f388c6ee53437 
OS: Windows 10

https://chromium-swarm.appspot.com/user/task/3047452fbe0d9310

12 tests crashed:
    ExtensionWelcomeNotificationTest.DelayedPreferenceSyncNeverShown (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:439)
    ExtensionWelcomeNotificationTest.DelayedPreferenceSyncPreviouslyDismissed (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:406)
    ExtensionWelcomeNotificationTest.DismissWelcomeNotification (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:366)
    ExtensionWelcomeNotificationTest.FirstRunChromeNowNotification (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:269)
    ExtensionWelcomeNotificationTest.FirstRunShowRegularNotification (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:251)
    ExtensionWelcomeNotificationTest.NotificationPreviouslyExpired (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:515)
    ExtensionWelcomeNotificationTest.ShowWelcomeNotificationAgain (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:286)
    ExtensionWelcomeNotificationTest.SyncedDismissalWelcomeNotification (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:386)
    ExtensionWelcomeNotificationTest.TimeExpiredNotification (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:471)
    ExtensionWelcomeNotificationTest.WelcomeNotificationPreviouslyDismissed (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:306)
    ExtensionWelcomeNotificationTest.WelcomeNotificationPreviouslyDismissedLocal (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:326)
    ExtensionWelcomeNotificationTest.WelcomeNotificationPreviouslyDismissedSyncedAndLocal (e:\b\c\b\win\src\chrome\browser\notifications\extension_welcome_notification_unittest.cc:346)

I haven't dug into this yet to get a stack.
 

Comment 1 by wfh@chromium.org, Jul 27 2016

[6424:4144:0727/152950:14223453:FATAL:test_simple_task_runner.cc(21)] Check failed: thread_checker_.CalledOnValidThread(). 

is the error, but don't have a stack yet.

Comment 2 by wfh@chromium.org, Jul 28 2016

no symbols in task 3047452fbe0d9310, so can't get stacks.

Comment 3 by wfh@chromium.org, Aug 12 2016

Cc: steve...@chromium.org peter@chromium.org fdoray@chromium.org dim...@chromium.org mukai@chromium.org dewittj@chromium.org
this looks like it's still happening on every try job

e.g. 

https://build.chromium.org/p/tryserver.chromium.win/builders/win10_chromium_x64_rel_ng/builds/254

but it's passing because it's not a regression from the patch. Would be nice if someone looked at this. Adding a few random people.
Stack from bot:
ExtensionWelcomeNotificationTest.DelayedPreferenceSyncNeverShown (run #1):
[ RUN      ] ExtensionWelcomeNotificationTest.DelayedPreferenceSyncNeverShown
[7852:8368:0812/143923:6472203:FATAL:test_simple_task_runner.cc(21)] Check failed: thread_checker_.CalledOnValidThread().
Backtrace:
	base::debug::StackTrace::StackTrace [0x00007FF7348B63F1+33]
	logging::LogMessage::~LogMessage [0x00007FF73483102C+76]
	base::TestSimpleTaskRunner::PostDelayedTask [0x00007FF733CFB754+112]
	base::win::ObjectWatcher::DoneWaiting [0x00007FF7348A6BD4+148]
	RtlCreateTimer [0x00007FFA2AB2F25D+1165]
	TpSetWait [0x00007FFA2AB316C0+400]
	RtlFindActivationContextSectionString [0x00007FFA2AB1100D+5741]
	BaseThreadInitThunk [0x00007FFA2A850404+20]
	RtlUserThreadStart [0x00007FFA2AB45181+33]

Comment 5 by grt@chromium.org, Aug 15 2016

Cc: -fdoray@chromium.org
Owner: fdoray@chromium.org
Status: Assigned (was: Untriaged)
I suspect r407874. Francois: please take a look. Thanks!

Comment 6 by wfh@chromium.org, Aug 25 2016

Labels: -Pri-2 Pri-1
These tests are still broken - not just on the FYI builder, but on every single win10 trybot run

https://build.chromium.org/p/chromium.fyi/builders/Win%2010%20Fast%20Ring/builds/2325/steps/unit_tests

https://build.chromium.org/p/tryserver.chromium.win/builders/win10_chromium_x64_rel_ng/builds/267/steps/unit_tests%20%28with%20patch%29%20on%20Windows-10-10586

Please can this be given a higher priority.

Comment 7 by wfh@chromium.org, Aug 25 2016

Blocking: 640994

Comment 8 by fdoray@chromium.org, Aug 25 2016

Status: Started (was: Assigned)
Reverted the problematic CL https://codereview.chromium.org/2277333002/

A TaskRunner is supposed to be thread-safe https://cs.chromium.org/chromium/src/base/task_runner.h?l=42 but that property isn't respected by the TestSimpleTaskRunner used in ExtensionWelcomeNotificationTest. A DCHECK fails when ObjectWatcher tries to used that TaskRunner from multiple threads.

Comment 9 by fdoray@chromium.org, Aug 26 2016

Status: Fixed (was: Started)
ExtensionWelcomeNotificationTest.* passed on Win10 https://build.chromium.org/p/chromium.fyi/builders/Win%2010%20Fast%20Ring/builds/2341/steps/unit_tests

Comment 10 by wfh@chromium.org, Aug 26 2016

Thanks for fixing this.
Project Member

Comment 11 by bugdroid1@chromium.org, Sep 6 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/980375e38eac6b3669a25a0d5f2a8991f57a4d55

commit 980375e38eac6b3669a25a0d5f2a8991f57a4d55
Author: fdoray <fdoray@chromium.org>
Date: Tue Sep 06 17:47:07 2016

Make TestSimpleTaskRunner thread-safe.

From task_runner.h:
 "Implementations of TaskRunner should be thread-safe in that all
  methods must be safe to call on any thread."

The fact that TestSimpleTaskRunner doesn't respect this contract is
confusing. It led to a CL being reverted because it caused a DCHECK
failure inside TestSimpleTaskRunner.
https://codereview.chromium.org/2277333002/

This CL ensures that this won't happen again by making
TestSimpleTaskRunner thread-safe.

BUG= 632184 
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review-Url: https://codereview.chromium.org/2296923003
Cr-Commit-Position: refs/heads/master@{#416654}

[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/base/test/test_simple_task_runner.cc
[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/base/test/test_simple_task_runner.h
[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/cc/test/ordered_simple_task_runner.h
[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/chrome/browser/chromeos/policy/heartbeat_scheduler_unittest.cc
[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/chrome/browser/chromeos/policy/status_uploader_unittest.cc
[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/chrome/browser/chromeos/policy/system_log_uploader_unittest.cc
[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/components/policy/core/common/cloud/cloud_policy_refresh_scheduler_unittest.cc
[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/components/policy/core/common/cloud/external_policy_data_updater_unittest.cc
[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/components/policy/core/common/policy_statistics_collector_unittest.cc
[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/device/bluetooth/bluetooth_adapter_win_unittest.cc
[modify] https://crrev.com/980375e38eac6b3669a25a0d5f2a8991f57a4d55/device/bluetooth/bluetooth_task_manager_win_unittest.cc

Sign in to add a comment