We want to run only one testcase each time the test activity is invoked.
Next:
Currently the APK is reinstalled before runnning each test case, avoiding that (and other test data setup) will speed up tests a lot.
build/android/run_browser_tests.py -vvv -f SessionHistoryTest.BasicBackForward:SessionHistoryTest.FrameBackForward
BUG=138275
Review URL: https://chromiumcodereview.appspot.com/12263024
git-svn-id: http://src.chromium.org/svn/trunk/src/build@183982 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Do not regenerate JNI files (and subsequently the .so file) if they have
not changed. This will happen if you edit a java file that has a native
counterpart, but the native signatures were not touched.
We do not enable this all the time as some build systems require that
when you modify an input, the output should also be modified. This
also will result in more command line output, so we'll keep it behind
a developer flag for now.
BUG=
Review URL: https://chromiumcodereview.appspot.com/12314025
git-svn-id: http://src.chromium.org/svn/trunk/src/build@183936 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Remove make build logic and switch all bots to use ninja.
Many bots already use ninja to build, including
Android Builder (dbg) on main waterfall.
Also fix issue introduced in r154587 where experimental
compile did not use goma.
BUG=157947
R=Yaron
Review URL: https://codereview.chromium.org/12310007
git-svn-id: http://src.chromium.org/svn/trunk/src/build@183712 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This doesn't change the conditional contents of browser_tests.isolate
on any platform. All tests formerly under OS=="linux" are now under
OS=="linux" and (chromeos==0 or chromeos==1).
BUG=158329
TEST=build _run targets, look for new variable in .isolated.state
Review URL: https://chromiumcodereview.appspot.com/12208124
git-svn-id: http://src.chromium.org/svn/trunk/src/build@183668 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
We were using package_name as a unique name for naming output files and
directories. package_name was typically the same as _target_name or a
variation of it (like dropping _apk). Using _target_name instead means
we need to specify one less thing and it is (maybe?) guaranteed to be
unique.
TBR=brettw,joi,jar,fischman,zea,sky
BUG=
Review URL: https://chromiumcodereview.appspot.com/11308030
git-svn-id: http://src.chromium.org/svn/trunk/src/build@183639 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
All of our APKs should be built with build/java_apk.gypi. Currently,
native test APKs are built very differently. This change makes them
build more like other apks, as a first step to using java_apk.gypi.
Since WebKit's gyp files use generate_native_test.py directly,
rather than including apk_test.gypi, generate_native_test.py
needs to continue to support using it for ant compilation. :(
BUG=177121
Review URL: https://chromiumcodereview.appspot.com/12310002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@183614 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
CQ automatically adds +x to any file which ends with .sh
Since envsetup.sh doesn't have a shabang line, this has
causes several tree closures. Fix this by adding a shabang
and detecting when script is not being sourced.
TBR=yfriedman
Review URL: https://codereview.chromium.org/12282018
git-svn-id: http://src.chromium.org/svn/trunk/src/build@182968 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Adding the missing UpdateTextInputState calls after each ime event and
preventing updates midway through ime event.
Added missing calls will start sending UpdateSelection updates to the
IMEs.
i.e. confirmComposition can cause multiple didChangeSelection calls but
we only care about the last one.
BUG=172845
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12093068
git-svn-id: http://src.chromium.org/svn/trunk/src/build@182534 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
To implement CertVerifyProc on Android we refer to the Java
side to query the platform trust managers. Currently the
information we get from the platform is binary - each
certificate chain is either identified as trusted or not, in
which case we assume that this is due to not-trusted root.
This patch provides better granularity distinguishing the
following cases: expired, not yet valid, incorrect (could not
be parsed), not trusted root.
This allowed to reenable two net unittests:
- CertVerifyProcTest.ExtraneousMD5RootCert
- CertVerifyProcTest.IntermediateCARequireExplicitPolicy
The following net unittest had to be disabled as it joins
the club of CertVerifyProc tests failing on bots with
incorrect time/date settings:
- CertVerifyProcTest.InvalidKeyUsage
BUG=169762
Review URL: https://chromiumcodereview.appspot.com/12212135
git-svn-id: http://src.chromium.org/svn/trunk/src/build@182280 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
It turns out that r181918, which pinned the Clang revision on Mac ASan
bots worked a little too well, pinning the version on *all* Mac bots.
This reverts the Clang roll. We will then fix update.sh to get the Mac
ASan pinning correct, and then re-land the roll.
BUG=174873, 170629
Review URL: https://codereview.chromium.org/12256002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@182173 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
As of Clang r174490 instrumented binaries do not include the __asan_* symbols,
so the postbuild strip action fails.
This is a temporary measure, we may need to do something else (e.g. use different .saves files) when the dynamic runtime is adopted on OSX.
BUG=170629,174873
Review URL: https://codereview.chromium.org/12210114
git-svn-id: http://src.chromium.org/svn/trunk/src/build@181733 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
We have substantially improved the licenses checker to avoid
false positives in finding copyrighted code in non-third_party dirs.
Also, this change makes the presence of stale entries in the
whitelist file to be a warning, not an error.
BUG=161461
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12209034
git-svn-id: http://src.chromium.org/svn/trunk/src/build@181679 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
aruslan@chromium.org
nileshagrawal@chromium.org
mostynb@opera.com
tedchoc@chromium.org
bengr@chromium.org
shashishekhar@chromium.org
craigdh@chromium.org
ilevy@chromium.org
benrg@chromium.org
cjhopman@chromium.org
miguelg@chromium.org
aberent@chromium.org
jschuh@chromium.org
phajdan.jr@chromium.org
mmenke@chromium.org
tfarina@chromium.org
siggi@chromium.org
isherman@chromium.org
szager@chromium.org
aurimas@chromium.org
bsalomon@google.com
frankf@chromium.org
bulach@chromium.org
ppi@chromium.org
hans@chromium.org
skyostil@chromium.org
thestig@chromium.org
chrisha@chromium.org
MHX348@motorola.com
apatrick@chromium.org
glider@chromium.org
mnaganov@chromium.org