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

Issue 629499 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
OOO until 4th Feb
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug
Team-Security-UX



Sign in to add a comment

NotificationPermissionContextTest.PushSecureOriginRequirement failing on DrMemory bot

Project Member Reported by grt@chromium.org, Jul 19 2016

Issue description

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%29/builds/5351/steps/memory%20test%3A%20unit/logs/stdio

[ RUN      ] NotificationPermissionContextTest.PushSecureOriginRequirement
c:\b\build\slave\drm-cr\build\src\chrome\browser\notifications\notification_permission_context_unittest.cc(191): error: Value of: context.GetPermissionStatus(origin, origin)
  Actual: 3
Expected: CONTENT_SETTING_BLOCK
Which is: 2
c:\b\build\slave\drm-cr\build\src\chrome\browser\notifications\notification_permission_context_unittest.cc(195): error: Value of: context.GetPermissionStatus(origin, origin)
  Actual: 1
Expected: CONTENT_SETTING_BLOCK
Which is: 2
[  FAILED  ] NotificationPermissionContextTest.PushSecureOriginRequirement (78 ms)
 

Comment 1 by raymes@chromium.org, Jul 20 2016

Cc: raymes@chromium.org
 Issue 629514  has been merged into this issue.

Comment 2 by raymes@chromium.org, Jul 20 2016

This is happening because SecureOriginWhiteListTest.UnsafelyTreatInsecureOriginAsSecure marks http://example.com as secure which is leaked to other tests.
Project Member

Comment 3 by bugdroid1@chromium.org, Jul 21 2016

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

commit d0dfe00f7e138a1f9221e8865fffe3b3a859c92f
Author: raymes <raymes@chromium.org>
Date: Thu Jul 21 00:58:25 2016

Fix SecureOriginWhiteListTest.UnsafelyTreatInsecureOriginAsSecure to not leak test state

SecureOriginWhiteListTest.UnsafelyTreatInsecureOriginAsSecure currently marks
2 insecure origins as secure. This state leaks to other tests such that those
origins are treated as secure in those tests. This CL cleans up the state by
resetting SchemeAndOriginWhitelist after the test.

BUG= 629499 

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

[modify] https://crrev.com/d0dfe00f7e138a1f9221e8865fffe3b3a859c92f/chrome/common/secure_origin_whitelist_unittest.cc
[modify] https://crrev.com/d0dfe00f7e138a1f9221e8865fffe3b3a859c92f/content/common/origin_util.cc

Comment 4 by raymes@chromium.org, Jul 21 2016

Status: Fixed (was: Assigned)
Cc: kinuko@chromium.org
 Issue 532243  has been merged into this issue.

Sign in to add a comment