Open GoogleCodeExporter opened 8 years ago
See also build bot failures
buildbot failure in Libyuv on Android Release
The Buildbot has detected a new failure on builder Android Release while
building libyuv.
Full details are available at:
http://build.chromium.org/p/client.libyuv/builders/Android%20Release/builds/716
Buildbot URL: http://build.chromium.org/p/client.libyuv/
Buildslave for this Build: vm322-m3
Build Reason: scheduler
Build Source Stamp: [branch master] 2560df9513e66080524a5b8dcea92b8ec657a8eb
Blamelist: fbarchard@google.com
BUILD FAILED: failed steps failed gclient runhooks
sincerely,
-The Buildbot
Original comment by fbarch...@google.com
on 5 Jan 2016 at 11:17
I had a look at the bot and it was failing due to some file system permission
issues that was possible to resolve by wiping a
/mnt/data/b/build/slave/android/build/src/chromium/src/third_party/android_tools
on disk. So both commit bots in
https://build.chromium.org/p/client.libyuv/waterfall are now green.
However, I'm also able to reproduce the error in my local checkout, so I wonder
what the difference can be. The bots also gets auto-updated depot tools, and it
doesn't look related to depot tools to me, rather something with GYP.
Original comment by kjellan...@google.com
on 10 Jan 2016 at 8:02
OK I've figured it out: at
https://code.google.com/p/chromium/codesearch#chromium/src/build/android/gyp/jav
a_cpp_enum.py&l=233 the script uses the absolute path to lookup the name of the
script (in a very odd and probably bad way). If 'build' is not a part of the
path, it simply fails.
The works in Chromium and WebRTC since the GYP scripts (build/gyp_chromium and
webrtc/build/gyp_webrtc) are located in such paths. For libyuv, the gyp_libyuv
is put straight into the root of the checkout, thus not containing 'build'.
The reason it passes on the libyuv buildbots is just pure luck, since their
checkouts are located in a dir like: /b/build/slave/linux64/build/libyuv.
I'll see if I can make a bugfix for the java_cpp_enum.py script so this error
goes away.
Another option would be to try to find a way to not invoke that GYP stuff, but
it's hard since libyuv_tests.gyp includes testing/android/native_test.gyp,
which is where this comes from.
Workaround: Make a directory 'build' and move your libyuv workspace into it :)
Original comment by kjellan...@google.com
on 10 Jan 2016 at 8:27
CL up: https://codereview.chromium.org/1571243003/
Original comment by kjellan...@google.com
on 11 Jan 2016 at 4:30
Original issue reported on code.google.com by
fbarch...@google.com
on 22 Dec 2015 at 1:02