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

Issue 684175 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
llozano@chromium.org
█ yunlian@chromium.org
rjkroege@chromium.org
█ reve...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

MSAN failures on the Linux ChromeOS MSan Tests bot

Project Member Reported by thomasanderson@chromium.org, Jan 24 2017 
See https://build.chromium.org/p/chromium.memory.full/builders/Linux%20ChromeOS%20MSan%20Tests/builds/4818

The CrOS MSAN bot reported exceptions for about a month due to a Precise->Trusty builder upgrade.  The tacker for this was  bug 680967 .

Now that the bot is no longer reporting exceptions, there were MSAN errors introduced during its downtime that must now be fixed.

Comment 1 by autumn@chromium.org, Feb 1 2017

Cc: llozano@chromium.org
Components: -Infra>Client>ChromeOS Infra>Client
Sounds like a chrome infra issue, changing component 

+ llozano as this may impact toolchain too

Comment 2 by llozano@chromium.org, Feb 1 2017

Cc: yunlian@chromium.org
Project Member

Comment 3 by sheriffbot@chromium.org, Feb 12 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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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

Sign in to add a comment