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

Issue metadata

Status: New
Owner: ----
Cc:
Components:
OS-

Blocked on:
issue chromium:679577



Sign in to add a comment
link

Issue 4388: Bots are unhealthy after recent infra updates.

Reported by dschuff@chromium.org, Jan 11 2017 Project Member

Issue description

The bots have several issues since early January (?)*

1. Bots are being upgraded from Precise to Trusty, and renamed from e.g. 'precise64-foo' to 'linux64-foo'. This has been completed for the buildbots but not the trybots yet.

2. Goma is being used in cases where it shouldn't be (e.g. win32 and arm)

3. Vista64 slave is offline. I'm guessing it has gone away entirely, as vista is no longer a supported Chromium target.

4. Triggering is broken for the arm hardware bots. For the main waterfall it appears that they never run, and for the trybots they appear to be run at the start (rather than being triggered).

*Some of these issues may be older than that but the logs don't seem to be still around.
 

Comment 1 by dschuff@chromium.org, Jan 11 2017

Project Member
Cc: stich...@chromium.org bbudge@chromium.org binji@chromium.org sbc@chromium.org
+cc other nacl people

Comment 2 by dschuff@chromium.org, Jan 11 2017

Project Member
Description: Show this description

Comment 3 by dschuff@chromium.org, Jan 11 2017

Project Member

Comment 4 by bugdroid1@chromium.org, Jan 11 2017

Project Member
The following revision refers to this bug:
  https://chromium.googlesource.com/native_client/src/native_client.git/+/94bbb858ca3830bcd56fb732cc6050608787f07e

commit 94bbb858ca3830bcd56fb732cc6050608787f07e
Author: Derek Schuff <dschuff@chromium.org>
Date: Wed Jan 11 06:08:13 2017

Set bot names back to precise for trybots

Infra is updating bots from Precise to Trusty and renaming them from 'precise' to 'linux'. The buildbots are finished but not the trybots. Rev 9f8fdd668b305511b605ee229533639c29a5222b updated the buildbot names but also some of the trybot names, so hack them back to 'precise' for now.

R=bradnelson@google.com, bradnelson
BUG= https://bugs.chromium.org/p/nativeclient/issues/detail?id=4388

Review-Url: https://codereview.chromium.org/2624913002 .

[modify] https://crrev.com/94bbb858ca3830bcd56fb732cc6050608787f07e/buildbot/buildbot_selector.py

Comment 5 by dschuff@chromium.org, Jan 11 2017

Project Member
6. The linux64-validator-opt bot is down. The slave is up, but doesn't have the buildbot slave software running on it.

Comment 6 by dschuff@chromium.org, Jan 17 2017

Project Member
Blockedon: chromium:679577
The Goma issues (2) seem to be fixed with the fix of https://bugs.chromium.org/p/chromium/issues/detail?id=679577

The newlib arm toolchain trybot  (e.g.)
https://build.chromium.org/p/tryserver.nacl/builders/nacl-toolchain-precise64-newlib-arm/builds/1618 seems to have some issue with the buildbot annotation. I don't know if that's a cascade from some other failure, but I don't see any other failure on that run.

Comment 7 by yyanagisawa@chromium.org, Jan 18 2017

I think it caused by compile failure.

https://build.chromium.org/p/tryserver.nacl/builders/nacl-toolchain-precise64-newlib-arm/builds/1618/steps/glibc_arm%20%28build%29/logs/stdio

% arm-nacl-gcc localtime.c -c -std=gnu11 -fgnu89-inline  -O2 -Wall -Werror -Wundef -Wwrite-strings -fmerge-all-constants -frounding-math -g -Wstrict-prototypes -Wold-style-definition     -ftls-model=initial-exec      -I../include -I/b/build/slave/nacl-toolchain-precise64-newlib-arm/build/native_client/toolchain_build/out/glibc_arm_work/time  -I/b/build/slave/nacl-toolchain-precise64-newlib-arm/build/native_client/toolchain_build/out/glibc_arm_work  -I../sysdeps/arm/armv7/multiarch  -I../sysdeps/arm/armv7  -I../sysdeps/arm/armv6t2  -I../sysdeps/arm/armv6  -I../sysdeps/arm/nacl/include -I../sysdeps/arm/nacl  -I../sysdeps/arm/nptl  -I../sysdeps/init_array  -I../sysdeps/arm/include -I../sysdeps/arm  -I../sysdeps/wordsize-32  -I../sysdeps/ieee754/flt-32  -I../sysdeps/ieee754/dbl-64  -I../sysdeps/nacl  -I../sysdeps/nptl  -I../sysdeps/pthread  -I../sysdeps/posix  -I../sysdeps/gnu  -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. -I../libio -I. -nostdinc -isystem /b/build/slave/nacl-toolchain-precise64-newlib-arm/build/native_client/toolchain_build/out/glibc_arm_work/all_deps/bin/../lib/gcc/arm-nacl/4.9.2/include -isystem /b/build/slave/nacl-toolchain-precise64-newlib-arm/build/native_client/toolchain_build/out/glibc_arm_work/all_deps/bin/../lib/gcc/arm-nacl/4.9.2/include-fixed -isystem /b/build/slave/nacl-toolchain-precise64-newlib-arm/build/native_client/..  -D_LIBC_REENTRANT -include /b/build/slave/nacl-toolchain-precise64-newlib-arm/build/native_client/toolchain_build/out/glibc_arm_work/libc-modules.h -DMODULE_NAME=libc -include ../include/libc-symbols.h       -o /b/build/slave/nacl-toolchain-precise64-newlib-arm/build/native_client/toolchain_build/out/glibc_arm_work/time/localtime.o -MD -MP -MF /b/build/slave/nacl-toolchain-precise64-newlib-arm/build/native_client/toolchain_build/out/glibc_arm_work/time/localtime.o.dt -MT /b/build/slave/nacl-toolchain-precise64-newlib-arm/build/native_client/toolchain_build/out/glibc_arm_work/time/localtime.o
In file included from ../sysdeps/nacl/clock.c:20:0:
../sysdeps/nacl/clock.c: In function ‘clock’:
../sysdeps/nacl/clock.c:28:45: error: passing argument 1 of ‘__nacl_irt_basic.clock’ from incompatible pointer type [-Werror]
   return NACL_CALL (__nacl_irt_basic.clock (&result), result);
                                             ^
../sysdeps/nacl/nacl-interfaces.h:114:18: note: in definition of macro ‘NACL_CALL’
   ({ int _err = (err); _err ? __nacl_fail (_err) : (val); })
                  ^
../sysdeps/nacl/clock.c:28:45: note: expected ‘nacl_irt_clock_t *’ but argument is of type ‘nacl_abi_clock_t *’
   return NACL_CALL (__nacl_irt_basic.clock (&result), result);
                                             ^
../sysdeps/nacl/nacl-interfaces.h:114:18: note: in definition of macro ‘NACL_CALL’
   ({ int _err = (err); _err ? __nacl_fail (_err) : (val); })
                  ^
cc1: all warnings being treated as errors

Sign in to add a comment