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

Issue 799852 link

Starred by 0 users
Status: Assigned
Owner:
█ yini...@chromium.org
Last visit > 30 days ago
Cc:
grt@chromium.org
█ sandeepkumars@chromium.org
█ penny...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

[Missing Tests] : Blogpost comments : getting a BSOD Blue screen, with Bad pool header when trying to access Chrome from a app-v application

Project Member Reported by sandeepkumars@chromium.org, Jan 8 2018 
Automated tests for the below commit have been missing.Would it be possible to add test coverage to avoid regressions in future?

CL: 
===
https://chromium.googlesource.com/chromium/src.git/+/f2d73e5016e9f212dded87e65ed1ae0d0da4e723

Ref Bug: 
========
https://bugs.chromium.org/p/chromium/issues/detail?id=794695

Thank You!

Comment 1 by grt@chromium.org, Jan 8 2018

Cc: penny...@chromium.org
Labels: Stability-ThirdParty
Status: Started (was: Assigned)
The code has unit tests. The problem was that the code was triggering a bug in third-party software that injected into Chrome. We can't really write a regression test for this that'll run in the normal waterfall. I'm checking to see if it's possible to run automated tests on a machine with App-V installed. This seems useful, but not at all simple.

Comment 2 by grt@chromium.org, Jan 10 2018

Cc: grt@chromium.org
Labels: -Pri-1 -M-63 -M-64 Pri-2
Owner: yini...@chromium.org
Status: Assigned (was: Started)
It turns out that this type of integration test is already on the radar of the appropriate team. Assigning to yiningc@. Thanks!

Comment 3 by nyerramilli@chromium.org, Feb 2 2018

Components: Tests>Missing
►

Sign in to add a comment