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

Issue 656847 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Jan 2018
Cc:
█ pho...@chromium.org
█ shuqianz@chromium.org
dgarr...@chromium.org
jen...@chromium.org
d...@chromium.org
afakhry@chromium.org
steve...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Linux ChromiumOS Tests trybot seems to run differently from the tree buildbot.

Project Member Reported by avayvod@chromium.org, Oct 18 2016 
My CL passed trybots and commit queue but was later reverted due to tests failing on the Linux ChromiumOS Tests bot.

The CL: https://codereview.chromium.org/2416253002
The passing trybot: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_rel_ng/builds/296797
The failure on the main waterfall: https://uberchromegw.corp.google.com/i/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%28dbg%29%281%29/builds/19067

My guess is that the dbg tests hit some OOM issue while the release version doesn't. I wonder if something could be done here to improve the situation.

Comment 1 by avayvod@chromium.org, Oct 18 2016 

I can reproduce the failure locally with "ulimit -S 65536" but with any number higher the tests pass.
Do we run the tests with a limit of 64Mb?
I also wonder if we allocate too much memory in this case - the failing test simply creates 10 empty <embed> objects on one page.

Comment 2 by avayvod@chromium.org, Oct 19 2016

Cc: pho...@chromium.org dgarr...@chromium.org

Comment 3 by mmoss@chromium.org, Oct 19 2016

Components: -Infra Infra>Client>ChromeOS Infra>Platform>Buildbot>TryServer

Comment 4 by dshi@chromium.org, Oct 25 2016 

dgarrett, do you know anything about this bug?

Comment 5 by dgarr...@chromium.org, Oct 25 2016

Owner: x...@chromium.org
This is a Chrome issue, not ChromeOS. Passing to the current gardener.

Comment 6 by x...@chromium.org, Oct 25 2016

Cc: afakhry@chromium.org steve...@chromium.org
stevenjb@, do you know the reason? It seems the mismatched configuration on trybot and the waterfall builder has caused several issues including this one.

Comment 7 by steve...@chromium.org, Oct 25 2016

Cc: d...@chromium.org
It doesn't look like we run the equivalent of Linux ChromiumOS Tests (dbg) in the try servers. I expect due to resource constraints. +dnj@ to confirm.

Comment 8 by d...@chromium.org, Oct 26 2016 

The list of trybots that are part of CQ is here: https://chromium.googlesource.com/chromium/src/+/refs/heads/master/infra/config/cq.cfg

There is a dbg bot on the tryserver, but it is not part of CQ. So confirmed...

Comment 9 by estaab@chromium.org, Feb 1 2017

Components: -Infra>Client>ChromeOS -Infra>Platform>Buildbot>TryServer Infra>Client>Chrome
Status: Assigned (was: Untriaged)

Comment 10 by x...@chromium.org, Feb 15 2017

Owner: ----
I'm not a good owner for this.

Comment 11 by dgarr...@chromium.org, Feb 15 2017

Owner: x...@chromium.org
Please find someone who is instead of letting it just get lost.

Comment 12 by x...@chromium.org, Feb 15 2017

Cc: jen...@chromium.org
Owner: shuqianz@chromium.org
Pass to this week's infra deputy.

Comment 13 by steve...@chromium.org, Feb 15 2017

Cc: shuqianz@chromium.org
Labels: Hotlist-CrOS-Gardener
Owner: ----
Status: Untriaged (was: Assigned)
Unassigning and marking untriaged so that chrome infra can triage and decide to WontFix or increase CQ coverage. The gardeners do not have enough information to make that call.

FWIW, I suspect that edge cases like this are going to happen and while it's a pain when it occurs, we can probably live with it.

Comment 14 by shenghua...@chromium.org, Jan 29 2018

Status: Archived (was: Untriaged)
This old issue has no activity for a long time. I'm archiving it unless it can be caught with more information.
►

Sign in to add a comment