New issue
Advanced search Search tips

Issue 852895 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

remoting_unittests failing on chromium.linux/Linux Tests (dbg)(1)(32)

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jun 14 2018

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of fdoray@chromium.org

remoting_unittests failing on chromium.linux/Linux Tests (dbg)(1)(32)

Builders failed on: 
- Linux Tests (dbg)(1)(32): 
  https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20Tests%20%28dbg%29%281%29%2832%29


 

Comment 1 by fdoray@chromium.org, Jun 14 2018

Log:

Command: ./remoting_unittests --brave-new-test-launcher --test-launcher-bot-mode --cfi-diag=0 --test-launcher-summary-output=/b/s/w/iocKZJ81/output.json
./remoting_unittests: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory

Comment 2 by fdoray@chromium.org, Jun 14 2018

Components: Services>Chromoting

Comment 3 by joedow@google.com, Jun 14 2018

Here is the CL which added them to the set of tests to run on chromium.Linux:
https://chromium-review.googlesource.com/c/chromium/src/+/1099430

The specific exception that was removed in that CL was:
 'remoting_unittests': {
    'remove_from': [
      # On chromium.linux, unclear why these aren't run on 32-bit.
      'Linux Tests (dbg)(1)(32)',
    ],
  },

Comment 4 by hzl@chromium.org, Jun 14 2018

Cc: jbudorick@chromium.org
Owner: thakis@chromium.org
@thakis The test is failing on the bot. Would you please revert/fix?

Comment 5 by thakis@chromium.org, Jun 14 2018

I'll disable it again.

Comment 6 by hzl@chromium.org, Jun 14 2018

cc @jbudorick since @jbudorick reviewed.

Comment 7 by hzl@chromium.org, Jun 14 2018

Labels: -Infra-Troopers
Thanks @thakis
Project Member

Comment 9 by bugdroid1@chromium.org, Jun 14 2018

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

commit 128fd383c461a7839c4415c148675b69b5b906f4
Author: Nico Weber <thakis@chromium.org>
Date: Thu Jun 14 23:29:27 2018

Disable remoting_unittests again on Linux Tests (dbg)(1)(32).

Now we know why they didn't run there.

TBR=jbudorick

Bug:  852895 
Change-Id: I907a26d4035e4f6f3942838cc48befe00cae5c9c
Reviewed-on: https://chromium-review.googlesource.com/1101838
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567479}
[modify] https://crrev.com/128fd383c461a7839c4415c148675b69b5b906f4/testing/buildbot/chromium.linux.json
[modify] https://crrev.com/128fd383c461a7839c4415c148675b69b5b906f4/testing/buildbot/test_suite_exceptions.pyl

Labels: Pri-1
Labels: -Pri-1 Pri-2
Owner: ----
Status: Untriaged (was: Available)
Back to p2 now that the test is disabled and the bot is back to green.

Remoting triage can look at this and decide what (if anything) to do with this. How much longer is the 32-bit bot going to be around?
Labels: -Sheriff-Chromium
Removing Sheriff-Chromium label too.
Status: Fixed (was: Untriaged)
We don't ship 32-bit binaries for Linux, so I think these can stay disabled.
Cc: -fdoray@chromium.org

Sign in to add a comment