Chromium Code Reviews
|
|
Chromium Code Reviews
Issue
427153003:
[MIPS] Enhance MIPS testing on its buildbot (Closed)
|
Created:
6 years, 4 months ago by petarj Modified:
6 years, 2 months ago CC:
native-client-reviews_googlegroups.com Base URL:
http://git.chromium.org/native_client/src/native_client.git@master Visibility:
Public. |
Description[MIPS] Enhance MIPS testing on its buildbot
Modify the buildbot scripts so they can be reused for MIPS as well.
Execution of the tests is not yet enabled for MIPS since some tests do
not pass.
BUG= https://code.google.com/p/nativeclient/issues/detail?id=2275
TEST= trigger the buildbot
Committed: http://src.chromium.org/viewvc/native_client?view=rev&revision=13901
Patch Set 1 #
Total comments: 5
Patch Set 2 : Fix comments. #Patch Set 3 : Rebase. #
Total comments: 12
Patch Set 4 : Update. #
Total comments: 4
Patch Set 5 : Update. #
Messages
Total messages: 27 (5 generated)
Initial version. Let me know your comments on this. Thanks. Regards, Petar
https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_pnacl.sh File buildbot/buildbot_pnacl.sh (right): https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_pnacl.sh#n... buildbot/buildbot_pnacl.sh:232: # Chech is MIPS TC already built, if not, build it. "Check" https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_pnacl.sh#n... buildbot/buildbot_pnacl.sh:432: mode-trybot-qemu() { Derek has a refactoring change out for review which moves most of this function to buildbot_pnacl.py: https://codereview.chromium.org/426763002/ Derek, should Petar wait until your change is committed? https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_selector.py File buildbot/buildbot_selector.py (left): https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_selector.p... buildbot/buildbot_selector.py:222: # MIPS toolchain buildbot. I think this should still say "toolchain" because the bot is on the toolchain page (http://build.chromium.org/p/client.nacl.toolchain/console rather than http://build.chromium.org/p/client.nacl/console).
https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_pnacl.sh File buildbot/buildbot_pnacl.sh (right): https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_pnacl.sh#n... buildbot/buildbot_pnacl.sh:232: # Chech is MIPS TC already built, if not, build it. On 2014/07/31 16:12:30, Mark Seaborn wrote: > "Check" Done. https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_selector.py File buildbot/buildbot_selector.py (left): https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_selector.p... buildbot/buildbot_selector.py:222: # MIPS toolchain buildbot. On 2014/07/31 16:12:30, Mark Seaborn wrote: > I think this should still say "toolchain" because the bot is on the toolchain > page (http://build.chromium.org/p/client.nacl.toolchain/console rather than > http://build.chromium.org/p/client.nacl/console). Done.
On 2014/08/04 00:50:37, petarj wrote: > https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_pnacl.sh > File buildbot/buildbot_pnacl.sh (right): > > https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_pnacl.sh#n... > buildbot/buildbot_pnacl.sh:232: # Chech is MIPS TC already built, if not, build > it. > On 2014/07/31 16:12:30, Mark Seaborn wrote: > > "Check" > > Done. > > https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_selector.py > File buildbot/buildbot_selector.py (left): > > https://codereview.chromium.org/427153003/diff/1/buildbot/buildbot_selector.p... > buildbot/buildbot_selector.py:222: # MIPS toolchain buildbot. > On 2014/07/31 16:12:30, Mark Seaborn wrote: > > I think this should still say "toolchain" because the bot is on the toolchain > > page (http://build.chromium.org/p/client.nacl.toolchain/console rather than > > http://build.chromium.org/p/client.nacl/console). > > Done. I'm about to land a refactoring of buildbot_pnacl.sh to remove some duplication and continue moving away from the shell scripts. The current CL ( https://codereview.chromium.org/426763002/ ) doesn't affect mode-buildbot-arm but I started another CL behind it to remove basically all the scons testing from buildbot_pnacl.sh. It might make more sense to support mips in buildbot_pnacl.py for scons tests. gyp build and uploading for the hardware bots will be later. for your gyp build, I would be ok with starting with what you have here... or you could even add some gyp support to buildbot_pnacl.py that we could use for ARM too :)
New patch uploaded. PTAL.
LGTM https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.sh File buildbot/buildbot_pnacl.sh (right): https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:190: # Build with gyp - this only exercises the trusted TC Doesn't the Gyp build also invoke pnacl-clang? If so, the comment isn't accurate and you can remove it. https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:191: gyp-mips32-build() { Nit: can you put this after the ARM version? https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:194: gypmode="Debug" Nit: indent by 2, not 4 https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:212: export CC="mipsel-linux-gnu-gcc ${extra} " Trailing space not needed? https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:216: export SYSROOT Not set. Can this be removed? https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:221: export PATH=$(pwd)/toolchain/linux_x86/mips_trusted/bin:$PATH Shouldn't this just be scoped to the Gyp/make invocations? Scons has its own way of discovering the MIPS trusted toolchain, so we don't want Scons to be falling back to this PATH setting, when you add a Scons invocation later. Perhaps like this: local env_var=PATH=$(pwd)/... ... env $env_var native_client/build/gyp_nacl ... env $env_var make ... Or better, can you set: local bin=$(pwd)/toolchain/linux_x86/mips_trusted/bin export CC="$bin/mipsel-linux-gnu-gcc ${extra}" ... so that messing with PATH isn't needed?
https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.sh File buildbot/buildbot_pnacl.sh (right): https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:190: # Build with gyp - this only exercises the trusted TC On 2014/10/10 17:16:37, Mark Seaborn wrote: > Doesn't the Gyp build also invoke pnacl-clang? If so, the comment isn't > accurate and you can remove it. Done. https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:191: gyp-mips32-build() { On 2014/10/10 17:16:37, Mark Seaborn wrote: > Nit: can you put this after the ARM version? Done. https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:194: gypmode="Debug" On 2014/10/10 17:16:36, Mark Seaborn wrote: > Nit: indent by 2, not 4 Done. (I made the change in gyp-arm-build() too) https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:212: export CC="mipsel-linux-gnu-gcc ${extra} " On 2014/10/10 17:16:36, Mark Seaborn wrote: > Trailing space not needed? Done. (I made the change in gyp-arm-build() too) https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:216: export SYSROOT On 2014/10/10 17:16:36, Mark Seaborn wrote: > Not set. Can this be removed? Done. (I made the change in gyp-arm-build() too) https://codereview.chromium.org/427153003/diff/40001/buildbot/buildbot_pnacl.... buildbot/buildbot_pnacl.sh:221: export PATH=$(pwd)/toolchain/linux_x86/mips_trusted/bin:$PATH On 2014/10/10 17:16:36, Mark Seaborn wrote: > Shouldn't this just be scoped to the Gyp/make invocations? > > Scons has its own way of discovering the MIPS trusted toolchain, so we don't > want Scons to be falling back to this PATH setting, when you add a Scons > invocation later. > > Perhaps like this: > > local env_var=PATH=$(pwd)/... > ... > env $env_var native_client/build/gyp_nacl ... > env $env_var make ... > > > Or better, can you set: > > local bin=$(pwd)/toolchain/linux_x86/mips_trusted/bin > export CC="$bin/mipsel-linux-gnu-gcc ${extra}" > ... > > so that messing with PATH isn't needed? Done.
The CQ bit was checked by petarj@mips.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/427153003/480001
The CQ bit was unchecked by commit-bot@chromium.org
Presubmit check for 427153003-480001 failed and returned exit status 1. Running presubmit commit checks ... ** Presubmit Warnings ** Found lines longer than 80 characters (first 5 shown). buildbot/buildbot_pnacl.sh, line 253, 91 chars
On 2014/10/13 13:31:39, I haz the power (commit-bot) wrote: > Presubmit check for 427153003-480001 failed and returned exit status 1. > > Running presubmit commit checks ... > > ** Presubmit Warnings ** > Found lines longer than 80 characters (first 5 shown). > buildbot/buildbot_pnacl.sh, line 253, 91 chars OK to add NOPRESUBMIT=true?
On 2014/10/13 13:36:41, petarj wrote: > OK to add NOPRESUBMIT=true? If there's a pre-existing presubmit warning in the file, yes. https://codereview.chromium.org/427153003/diff/480001/buildbot/buildbot_pnacl.sh File buildbot/buildbot_pnacl.sh (right): https://codereview.chromium.org/427153003/diff/480001/buildbot/buildbot_pnacl... buildbot/buildbot_pnacl.sh:242: local toolchain_dir=native_client/toolchain/linux_x86/mips_trusted Maybe use "$(pwd)/toolchain..."? See other comment. https://codereview.chromium.org/427153003/diff/480001/buildbot/buildbot_pnacl... buildbot/buildbot_pnacl.sh:256: local bin=$(pwd)/toolchain/linux_x86/mips_trusted/bin You could reuse $toolchain_dir from above. (Although these two differ in whether they're relative and include "native_client" in the path.)
https://codereview.chromium.org/427153003/diff/480001/buildbot/buildbot_pnacl.sh File buildbot/buildbot_pnacl.sh (right): https://codereview.chromium.org/427153003/diff/480001/buildbot/buildbot_pnacl... buildbot/buildbot_pnacl.sh:242: local toolchain_dir=native_client/toolchain/linux_x86/mips_trusted On 2014/10/13 15:34:44, Mark Seaborn wrote: > Maybe use "$(pwd)/toolchain..."? See other comment. Done. https://codereview.chromium.org/427153003/diff/480001/buildbot/buildbot_pnacl... buildbot/buildbot_pnacl.sh:256: local bin=$(pwd)/toolchain/linux_x86/mips_trusted/bin On 2014/10/13 15:34:44, Mark Seaborn wrote: > You could reuse $toolchain_dir from above. (Although these two differ in > whether they're relative and include "native_client" in the path.) Done.
The CQ bit was checked by petarj@mips.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/427153003/980001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: nacl-win64_glibc_opt on tryserver.nacl (http://build.chromium.org/p/tryserver.nacl/builders/nacl-win64_glibc_opt/buil...)
The CQ bit was checked by petarj@mips.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/427153003/980001
Message was sent while issue was closed.
Committed patchset #5 (id:980001) as 13901
Message was sent while issue was closed.
This fails on the MIPS toolchain bot, though I can't tell why. There's various errors from invoking pnacl-clang, but seemingly no output from pnacl-clang itself: FAILED: Command '['/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj/gen/sdk/linux_x86/pnacl_newlib/bin/pnacl-clang', '-c', 'nacl_exception.c', '-o', '/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj.target/nacl_exception_lib/geni/newlib-mips/nacl_exception_lib/nacl_exception_0cb6ae52.o', '-MD', '-MF', '/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj.target/nacl_exception_lib/geni/newlib-mips/nacl_exception_lib/nacl_exception_0cb6ae52.o.d', '-Wundef', '-Wstrict-prototypes', '-O2', '-g', '-Wall', '-fdiagnostics-show-option', '-Werror', '-Wno-extra-semi', '-Wno-unused-private-field', '-Wno-char-subscripts', '-Wno-unused-function', '-D__STDC_LIMIT_MACROS=1', '-D__STDC_FORMAT_MACROS=1', '-D_GNU_SOURCE=1', '-D_DEFAULT_SOURCE=1', '-D_BSD_SOURCE=1', '-D_POSIX_C_SOURCE=199506', '-D_XOPEN_SOURCE=600', '-DDYNAMIC_ANNOTATIONS_ENABLED=1', '-DDYNAMIC_ANNOTATIONS_PREFIX=NACL_', '-DNACL_BUILD_ARCH=mips', '-D_DEFAULT_SOURCE=1', '-D_BSD_SOURCE=1', '-D_POSIX_C_SOURCE=199506', '-D_XOPEN_SOURCE=600', '-D_GNU_SOURCE=1', '-D__STDC_LIMIT_MACROS=1', '-D__STDC_FORMAT_MACROS', '-DNACL_BUILD_ARCH=mips', '-DNACL_BUILD_SUBARCH=32', '-DNACL_WINDOWS=0', '-DNACL_OSX=0', '-DNACL_LINUX=0', '-DNACL_ANDROID=0', '-I/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj/gen/tc_newlib/include', '-I../../../..', '-I../../../src/third_party', '-I../../../..', '-DNDEBUG', '-std=gnu99']' returned non-zero exit status 1 make: *** [out/Release/obj/gen/tc_newlib/libmips/libnacl_exception.a] Error 1 -- http://build.chromium.org/p/client.nacl.toolchain/builders/linux-pnacl-x86_32...
Message was sent while issue was closed.
On 2014/10/13 22:09:07, Mark Seaborn wrote: > This fails on the MIPS toolchain bot, though I can't tell why. There's various > errors from invoking pnacl-clang, but seemingly no output from pnacl-clang > itself: > > FAILED: Command > '['/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj/gen/sdk/linux_x86/pnacl_newlib/bin/pnacl-clang', > '-c', 'nacl_exception.c', '-o', > '/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj.target/nacl_exception_lib/geni/newlib-mips/nacl_exception_lib/nacl_exception_0cb6ae52.o', > '-MD', '-MF', > '/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj.target/nacl_exception_lib/geni/newlib-mips/nacl_exception_lib/nacl_exception_0cb6ae52.o.d', > '-Wundef', '-Wstrict-prototypes', '-O2', '-g', '-Wall', > '-fdiagnostics-show-option', '-Werror', '-Wno-extra-semi', > '-Wno-unused-private-field', '-Wno-char-subscripts', '-Wno-unused-function', > '-D__STDC_LIMIT_MACROS=1', '-D__STDC_FORMAT_MACROS=1', '-D_GNU_SOURCE=1', > '-D_DEFAULT_SOURCE=1', '-D_BSD_SOURCE=1', '-D_POSIX_C_SOURCE=199506', > '-D_XOPEN_SOURCE=600', '-DDYNAMIC_ANNOTATIONS_ENABLED=1', > '-DDYNAMIC_ANNOTATIONS_PREFIX=NACL_', '-DNACL_BUILD_ARCH=mips', > '-D_DEFAULT_SOURCE=1', '-D_BSD_SOURCE=1', '-D_POSIX_C_SOURCE=199506', > '-D_XOPEN_SOURCE=600', '-D_GNU_SOURCE=1', '-D__STDC_LIMIT_MACROS=1', > '-D__STDC_FORMAT_MACROS', '-DNACL_BUILD_ARCH=mips', '-DNACL_BUILD_SUBARCH=32', > '-DNACL_WINDOWS=0', '-DNACL_OSX=0', '-DNACL_LINUX=0', '-DNACL_ANDROID=0', > '-I/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj/gen/tc_newlib/include', > '-I../../../..', '-I../../../src/third_party', '-I../../../..', '-DNDEBUG', > '-std=gnu99']' returned non-zero exit status 1 > make: *** [out/Release/obj/gen/tc_newlib/libmips/libnacl_exception.a] Error 1 > > -- > http://build.chromium.org/p/client.nacl.toolchain/builders/linux-pnacl-x86_32... This looks like OS bittage issue, i.e. clang is 64-bit executable and linux-pnacl-x86_32-tests-mips has 32-bit OS, correct?
On 14 October 2014 12:29, Petar Jovanovic <Petar.Jovanovic@imgtec.com> wrote: > Hi Mark, > > If this is the case, what do you suggest? > Can you file a Chrome Infrastructure ticket on https://code.google.com/p/chromium/issues/list to ask for the build slaves behind http://build.chromium.org/p/client.nacl.toolchain/builders/linux-pnacl-x86_32... to be reimaged? The 32-bit Linux bots were changed (a few months ago) to use a 64-bit kernel with a 32-bit userland. I suppose that MIPS bot was missed. Reimaging should get it to use the new default kernel. > Can nacl-precise_64-newlib-mips-pnacl be used instead? > Well, that bot appears on the main waterfall ( http://build.chromium.org/p/client.nacl/console) rather than on the toolchain waterfall ( http://build.chromium.org/p/client.nacl.toolchain/console). I don't think you should put this new MIPS config on the main waterfall because: * It builds toolchains. * It's likely to get broken every so often. That's OK for the "FYI" section on the toolchain waterfall, but not so good on the main waterfall. Cheers, Mark > ________________________________________ > From: Petar Jovanovic > Sent: Tuesday, October 14, 2014 6:54 PM > To: mseaborn@chromium.org; dschuff@chromium.org > Cc: native-client-reviews@googlegroups.com > Subject: Re: [MIPS] Enable MIPS testing on the buildbots (issue 427153003 > by petarj@mips.com) > > On 2014/10/13 22:09:07, Mark Seaborn wrote: > > This fails on the MIPS toolchain bot, though I can't tell why. There's > various > > errors from invoking pnacl-clang, but seemingly no output from > pnacl-clang > > itself: > > > FAILED: Command > > > '['/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj/gen/sdk/linux_x86/pnacl_newlib/bin/pnacl-clang', > > '-c', 'nacl_exception.c', '-o', > > > '/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj.target/nacl_exception_lib/geni/newlib-mips/nacl_exception_lib/nacl_exception_0cb6ae52.o', > > '-MD', '-MF', > > > '/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj.target/nacl_exception_lib/geni/newlib-mips/nacl_exception_lib/nacl_exception_0cb6ae52.o.d', > > '-Wundef', '-Wstrict-prototypes', '-O2', '-g', '-Wall', > > '-fdiagnostics-show-option', '-Werror', '-Wno-extra-semi', > > '-Wno-unused-private-field', '-Wno-char-subscripts', > '-Wno-unused-function', > > '-D__STDC_LIMIT_MACROS=1', '-D__STDC_FORMAT_MACROS=1', '-D_GNU_SOURCE=1', > > '-D_DEFAULT_SOURCE=1', '-D_BSD_SOURCE=1', '-D_POSIX_C_SOURCE=199506', > > '-D_XOPEN_SOURCE=600', '-DDYNAMIC_ANNOTATIONS_ENABLED=1', > > '-DDYNAMIC_ANNOTATIONS_PREFIX=NACL_', '-DNACL_BUILD_ARCH=mips', > > '-D_DEFAULT_SOURCE=1', '-D_BSD_SOURCE=1', '-D_POSIX_C_SOURCE=199506', > > '-D_XOPEN_SOURCE=600', '-D_GNU_SOURCE=1', '-D__STDC_LIMIT_MACROS=1', > > '-D__STDC_FORMAT_MACROS', '-DNACL_BUILD_ARCH=mips', > '-DNACL_BUILD_SUBARCH=32', > > '-DNACL_WINDOWS=0', '-DNACL_OSX=0', '-DNACL_LINUX=0', '-DNACL_ANDROID=0', > > > '-I/mnt/data/b/build/slave/nacl-toolchain/build/out/Release/obj/gen/tc_newlib/include', > > '-I../../../..', '-I../../../src/third_party', '-I../../../..', > '-DNDEBUG', > > '-std=gnu99']' returned non-zero exit status 1 > > make: *** [out/Release/obj/gen/tc_newlib/libmips/libnacl_exception.a] > > Error 1 > > > -- > > > http://build.chromium.org/p/client.nacl.toolchain/builders/linux-pnacl-x86_32... > > This looks like OS bittage issue, i.e. clang is 64-bit executable and > linux-pnacl-x86_32-tests-mips has 32-bit OS, correct? > > https://codereview.chromium.org/427153003/ > -- You received this message because you are subscribed to the Google Groups "Native-Client-Reviews" group. To unsubscribe from this group and stop receiving emails from it, send an email to native-client-reviews+unsubscribe@googlegroups.com. To post to this group, send email to native-client-reviews@googlegroups.com. Visit this group at http://groups.google.com/group/native-client-reviews. For more options, visit https://groups.google.com/d/optout.
Message was sent while issue was closed.
On 2014/10/15 17:59:11, Mark Seaborn wrote: > Can you file a Chrome Infrastructure ticket on > https://code.google.com/p/chromium/issues/list to ask for the build slaves > behind > http://build.chromium.org/p/client.nacl.toolchain/builders/linux-pnacl-x86_32... > to be reimaged? > Here it is: https://code.google.com/p/chromium/issues/detail?id=423822
On 15 October 2014 11:17, <petarj@mips.com> wrote: > On 2014/10/15 17:59:11, Mark Seaborn wrote: > >> Can you file a Chrome Infrastructure ticket on >> https://code.google.com/p/chromium/issues/list to ask for the build >> slaves >> behind >> > > http://build.chromium.org/p/client.nacl.toolchain/ > builders/linux-pnacl-x86_32-tests-mips/ > >> to be reimaged? >> > > > Here it is: > > https://code.google.com/p/chromium/issues/detail?id=423822 Hmm, does the issue tracker not allow you to file Infra tickets? Do you not have issue tracker permissions for bypassing the "New issue wizard" form? Cheers, Mark -- You received this message because you are subscribed to the Google Groups "Native-Client-Reviews" group. To unsubscribe from this group and stop receiving emails from it, send an email to native-client-reviews+unsubscribe@googlegroups.com. To post to this group, send email to native-client-reviews@googlegroups.com. Visit this group at http://groups.google.com/group/native-client-reviews. For more options, visit https://groups.google.com/d/optout.
Message was sent while issue was closed.
On 2014/10/15 18:21:27, Mark Seaborn wrote: > On 15 October 2014 11:17, <mailto:petarj@mips.com> wrote: > > > On 2014/10/15 17:59:11, Mark Seaborn wrote: > > > >> Can you file a Chrome Infrastructure ticket on > >> https://code.google.com/p/chromium/issues/list to ask for the build > >> slaves > >> behind > >> > > > > http://build.chromium.org/p/client.nacl.toolchain/ > > builders/linux-pnacl-x86_32-tests-mips/ > > > >> to be reimaged? > >> > > > > > > Here it is: > > > > https://code.google.com/p/chromium/issues/detail?id=423822 > > > Hmm, does the issue tracker not allow you to file Infra tickets? > No. > Do you not have issue tracker permissions for bypassing the "New issue > wizard" form? > I do not think I have. I do not see how I can bypass it. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
