New issue
Advanced search Search tips

Issue 599769 link

Starred by 1 user
Status: Duplicate
Merged: issue 603357
Owner:
joedow@chromium.org
Closed: Apr 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

New Remoting test is failing on DrMemory

Project Member Reported by benwells@chromium.org, Apr 1 2016 
See https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%20full%29%20%283%29/builds/9970

Failure output:
RemoteSecurityKeyMessageReaderTest.MultipleMessages:
[3144:216:0330/224907:1854773:ERROR:remote_security_key_message_reader.cc(94)] Failed to read message: 1
e:\b\build\slave\drm-cr-64\build\src\remoting\host\security_key\remote_security_key_message_reader_unittest.cc(200): error: Value of: messages_received_.size()
Actual: 1
Expected: payloads.size()
Which is: 11

For now will disable the test on DrMemory, please investigate and re-enable.
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 1 2016 

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

commit 67d2bccd08940cf188c7b386f56854b00ded3bb9
Author: benwells <benwells@chromium.org>
Date: Fri Apr 01 05:43:45 2016

Exclude RemoteSecurityKeyMessageReaderTest.MultipleMessages on DrMemory.

TBR=jyasskin@chromium.org
BUG= 599769 

Review URL: https://codereview.chromium.org/1846143002

Cr-Commit-Position: refs/heads/master@{#384496}

[modify] https://crrev.com/67d2bccd08940cf188c7b386f56854b00ded3bb9/tools/valgrind/gtest_exclude/remoting_unittests.gtest-drmemory_win32.txt

Comment 2 by joedow@chromium.org, Apr 1 2016

Status: Assigned (was: Untriaged)

Comment 3 by joedow@chromium.org, Apr 15 2016

Components: Services>Chromoting

Comment 4 by joedow@chromium.org, Apr 18 2016

Mergedinto: 603357
Status: Duplicate (was: Assigned)
Merging this bug into a different bug tracking this failure.  Technically this issue is obsolete as I had renamed the test and this exception is no longer valid, however I still need to remove this exception when I fix the renamed unit test
►

Sign in to add a comment