Sometimes there is conflict when several tests restart adb server at the same time.
Originally, restarting adb server is to fix the issue of connection lost with adb server when emulator booting, as this case already handled in AndroidCommand::WaitForSystemBootCompleted(), so it can be removed now.
Also fix a typo.
BUG=
TEST=./build/android/run_tests.py -e -n 5
Review URL: https://chromiumcodereview.appspot.com/10781032
git-svn-id: http://src.chromium.org/svn/trunk/src/build@148242 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Overtime, there has been a few changes in the way we run:
- individual test suite versus all suites.
- single device versus sharded.
- debug info.
This patch simplifies the many different code paths and ensures
we'll have less breakages (and a more consistent way to add features).
BUG=
TEST=existing android tests (single device, multiple devices, emulator).
Review URL: https://chromiumcodereview.appspot.com/10777017
git-svn-id: http://src.chromium.org/svn/trunk/src/build@146985 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
use_emulator option is taken as integer somewhere but is taken as
boolean in other places.
Clean this option to be boolean and add another option --emulator_count to set
the count of emulators.
BUG=137458
TEST=./build/android/run_tests.py -e -n 1 -s base_unittests
Review URL: https://chromiumcodereview.appspot.com/10790006
git-svn-id: http://src.chromium.org/svn/trunk/src/build@146801 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
- We had a few options with default=True, which made them not really
optional. Instead, use an option with action='store_true' which is False by
default.
- Uses buildbot_report.py rather than duplicate the functionality.
- Removes default params from SingleTestRunner to make it more explicit.
BUG=
TEST=existing android tests.
Review URL: https://chromiumcodereview.appspot.com/10689159
git-svn-id: http://src.chromium.org/svn/trunk/src/build@146318 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
These files have diverged overtime. We need to get them in sync in
preparation for the instrumentation tests.
The patches downstream have been entangled, so this is a bit big and
contains a series of otherwise unrelated patches.
However, it's probably safer to do this way (as it's guaranteed to be similar to
downstream), than trying to split it in multiple patches.
BUG=
TEST=try -b android_test
Review URL: https://chromiumcodereview.appspot.com/10689132
git-svn-id: http://src.chromium.org/svn/trunk/src/build@145872 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
- Top-level scripts are kept under build/android.
- Utility libraries have been moved to build/android/pylib.
- Fixes all imports and headers.
This is in preparation for landing the "instrumentation" (java-based) tests,
which will reuse several of these components.
BUG=
TEST=existing android tests
Review URL: https://chromiumcodereview.appspot.com/10693110
git-svn-id: http://src.chromium.org/svn/trunk/src/build@145653 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This will make the android_test bot red when apk tests fail.
The ANDROID_APK_TEST_TARGET flag is required while we transition from executable to APK tests.
- Executable tests need the DIR_CACHE override as the default path comes from the java side.
BUG=125059
Review URL: https://chromiumcodereview.appspot.com/10332230
git-svn-id: http://src.chromium.org/svn/trunk/src/build@138407 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The 'Test Finished' step was introduced in r130823 to absorb the
non-zero exit status which we'd get if any of the test suites in
the batch would fail.
Since the run_tests.py script will print a STEP_FAILURE annotation
for every suite the exit status is redundant and therefore should
be removed.
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10382100
git-svn-id: http://src.chromium.org/svn/trunk/src/build@136302 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
OFF by default; enable with a gyp var. E.g.
GYP_DEFINES="$GYP_DEFINES gtest_target_type=shared_library" android_gyp
Some useful commands:
adb uninstall org.chromium.native_test
adb install -r out/Release/base_unittests_apk/ChromeNativeTests-debug.apk
adb shell am start -n org.chromium.native_test/org.chromium.native_test.ChromeNativeTestActivity
For the moment, all apks can be built simultaneously but use the same
activity name. Thus you cannot have more than one installed at the
same time.
BUG=None
TEST=
Review URL: http://codereview.chromium.org/10051021
git-svn-id: http://src.chromium.org/svn/trunk/src/build@133053 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Before this change, if some test failed before the last test succeeded,
because of the return value, the buildbot will show that the last test also
failed. Add a summary build step to avoid that.
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/9989001
git-svn-id: http://src.chromium.org/svn/trunk/src/build@130823 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Kill all emulators before starting a test to be more robust on error.
Print error if a file fails to copy to the device.
Speed up emulator launch by 40%.
Increase emulator partition size to fix 'out of space on device' errors.
Log emulator launch time to help profile bot costs.
Run tests in verbose mode to assist with bot debugging.
BUG=None
TEST=
Review URL: http://codereview.chromium.org/8769020
git-svn-id: http://src.chromium.org/svn/trunk/src/build@112552 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
nileshagrawal@chromium.org
james.wei@intel.com
bulach@chromium.org
yongsheng.zhu@intel.com
mkosiba@chromium.org
jrg@chromium.org
yfriedman@chromium.org
wangxianzhu@chromium.org
rsleevi@chromium.org
satish@chromium.org
jrg@google.com
maruel@chromium.org
michaelbai@google.com