apk-based test runner work for android

build/android/buildbot_functions.sh

 #!/bin/bash
 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 #
 # Bash functions used by buildbot annotator scripts for the android
 # build of chromium.  Executing this script should not perform actions
 # other than setting variables and defining of functions.
 
 # Number of jobs on the compile line; e.g.  make -j"${JOBS}"
@@ skipping 171 matching lines @@
 
   bb_stop_goma_internal
 }
 
 # Compile step
 function bb_compile {
   echo "@@@BUILD_STEP Compile@@@"
   bb_goma_make
 }
 
+# Re-gyp and compile with unit test bundles configured as shlibs for
+# the native test runner.  Experimental for now.  Once the native test
+# loader is on by default, this entire function becomes obsolete.
+function bb_native_test_compile_run_tests {
+  echo "@@@BUILD_STEP Re-gyp for the native test runner@@@"
+  GYP_DEFINES="$GYP_DEFINES gtest_target_type=shared_library" android_gyp
+
+  echo "@@@BUILD_STEP Native test runner compile@@@"
+  bb_goma_make
+
+  # Make sure running the template prints an expected failure.
+  echo "@@@BUILD_STEP Native test runner template test@@@"
+  tempfile=/tmp/tempfile-$$.txt
+  build/android/run_tests.py --xvfb --verbose \
+    -s out/Release/replaceme_apk/ChromeNativeTests-debug.apk \

[Yaron, 2012/04/12 01:29:53]

replaceme_apk? I dont' see where this instance of replaceme is replaced

[John Grabowski, 2012/04/13 01:11:37]

It isn't.  This test is for compiling the template itself.

+    | sed 's/@@@STEP_FAILURE@@@//g' | tee $tempfile
+  happy_failure=$(cat $tempfile | grep NATIVE_LOADER_FAILED | wc -l)

[Yaron, 2012/04/12 01:29:53]

is a failure really ever happy?

[bulach, 2012/04/12 15:51:42]

nit: a grep -c makes wc unecessary... but honestly, this logic is spread across
way too many layers... just move all this logic into the run_tests.py itself, I
guess all decisions on what a failure is should be self contained there..

[John Grabowski, 2012/04/13 01:11:37]

Yes.  If compiling the template yells about "no shared library", that implies we
could build and run it successfully.

[John Grabowski, 2012/04/13 01:11:37]

Not sure I agree.  We are building the template.  
Once it is stable this will likely get removed.

[bulach, 2012/04/13 09:42:51]

well, even if it's temporary, I'd rather have the logic in the existing place
rather than spreaded in multiple levels of scripts (more below..)

+  if [[ $happy_failure -eq 0 ]] ; then
+    echo "@@@STEP_FAILURE@@@"
+  else
+    echo "The previous NATIVE_LOADER_FAILED implies success for the runner."
+  fi
+}
+
 # Experimental compile step; does not turn the tree red if it fails.
 function bb_compile_experimental {
   # Linking DumpRenderTree appears to hang forever?
   EXPERIMENTAL_TARGETS="android_experimental"
   for target in ${EXPERIMENTAL_TARGETS} ; do
     echo "@@@BUILD_STEP Experimental Compile $target @@@"
     set +e
     bb_goma_make -k "${target}"
     if [ $? -ne 0 ] ; then
       echo "@@@STEP_WARNINGS@@@"
     fi
     set -e
   done
 }
 
 # Run tests on an emulator.
 function bb_run_tests_emulator {
   echo "@@@BUILD_STEP Run Tests on an Emulator@@@"
   build/android/run_tests.py -e --xvfb --verbose
 }
 
 # Run tests on an actual device.  (Better have one plugged in!)
 function bb_run_tests {
   echo "@@@BUILD_STEP Run Tests on actual hardware@@@"
   build/android/run_tests.py --xvfb --verbose
 }