Like we do for mochitests, set the MOZ_DEVELOPER_REPO_DIR and
MOZ_DEVELOPER_OBJ_DIR environment variables when running talos
tests so that the content sandbox permits access to test files
that are symlinks from the .app/ directory to the repo or
object directory.
MozReview-Commit-ID: J1bRqoB8a2i
--HG--
extra : rebase_source : 18f0bafa53dcd872d9bd647fc2e5ce143f5887bd
365731510976 (bug 1380391) added index routes for decision tasks by
pushlog id. This is a good idea. The pushlog id is guaranteed to always
be incrementing (except for repos that are periodically reset, which
we don't care about). It is useful to provide strict ordering for
pushes and is simpler for machines to consume and sort than dates.
So let's index all tasks by pushlog id.
MozReview-Commit-ID: BPqx4ARza1c
--HG--
extra : rebase_source : e952c636e5fcd2a0ddb5e14a0faaccb3761298bf
It be ideal to have |mach test {findbugs,test}| and |mach lint
{lint,checkstyle}|, but the |mach test| command is very difficult to
extend in a direction orthogonal to the existing direction. The
existing |mach test| is built around in-tree manifests, tagged and
divided into suites, intended to support |mach test
path/to/arbitrary/test|. The Android findbugs task is a global static
analysis that doesn't fit into the path/manifest model. The Android
test task is based on JUnit and not easy to build manifest support
for. The |mach lint| command is intended to be extended, but the
effort to extend it is non-trivial and not worth the effort (at this
time).
Therefore, I've taken the existing, little used |mach android| command
and added subcommands for use by local developers and automation. If
nothing else, this reduces the number of "special Gradle targets" --
the equivalent of "special Make targets" -- sprinkled throughout the
tree, which can only be a good thing!
MozReview-Commit-ID: 24b1vbgykpN
--HG--
extra : rebase_source : 8843a6e3840586fe05a1434484a848d48b2a6e8b
This adds the mozconfigs, mozharness configs and taskcluster changes required
to create optimized DMD builds for linux64, win32, win64 and macosx64.
These builds will happen nightly on mozilla-central
We also add support for custom build variants on Windows (or other generic
worker environments).
MozReview-Commit-ID: HrVT9PLSWVx
--HG--
extra : rebase_source : 39ac752a312afe04187728da82a4a7f722634811
The MINIDUMP_SAVE_PATH had been set incorrectly in these jobs. Now it
is set to the taskcluster upload directory, so when a crash dump is
produced, the .dmp and .extra files are uploaded and made available
as artifacts.
This patch upgrades the GRCOV version being used and changes how it is used in 'codecoverage.py'.
MozReview-Commit-ID: 6fjUB6sV3gy
--HG--
extra : histedit_source : 419133ee55f9a37725845994e0ff16a9c59b2bad
Using /home/worker is the build directory has a 30% talos performance
loss, because test machines has a /home mount directory.
MozReview-Commit-ID: zehcGJrUQX
--HG--
extra : source : feedcde68c2a54da210f03eb287ab5c862fc982b
extra : amend_source : 96a6ad12e8fbb5dd2f7ff97f5ef183b8400475cf
`try-test-paths` is set up to map anything under testing/web-platform
to the web-platform-tests flavour. By default, the web-platform-tests flavour
refers to the testharness test type for wptrunner, so we need to account for
reftest and wdspec test types.
This change causes mozharness to omit the test-type argument to wptrunner when
try-test-paths is being used, therefore making wptrunner determine the
appropriate test type for each requested test.
MozReview-Commit-ID: 7TDAShdDM4g
--HG--
extra : rebase_source : fde6ec219f574cd1e536764c0128a6816834f533
Using /home/worker is the build directory has a 30% talos performance
loss, because test machines has a /home mount directory.
MozReview-Commit-ID: zehcGJrUQX
--HG--
extra : rebase_source : e9ce75ecf18e7d4c829e369f5fbd1df8d6449edf
This patch enables talos test suites to run on VM (taskcluster) and also enables these test suites to run with GCOV code coverage instrumentation on the linux64-ccov build.
MozReview-Commit-ID: 7p59zvra1ge
--HG--
extra : rebase_source : 990ebecb9daaee7c5030e08b0d763493103f0fe8
Support OSX Signed nightlies (in the complete.mar too)
MozReview-Commit-ID: 6iPrPhjj34g
--HG--
extra : rebase_source : 55a6bcf1910f1cae084cf32f6cf47ecf44b500aa
This patch adds grcov to linux64-ccov. Grcov is then used after code coverage collection to process the .gcno and .gcda files into a .info (LCOV-style) file. It also uses the 'linked-files-map.json' to rewrite symbolic links to the path that they point to. The .info file that is produced is called 'grcov_lcov_output_stdout' and is stored in the zip file 'code-coverage-grcov.zip'.
MozReview-Commit-ID: 5WhD289N6Fs
--HG--
extra : rebase_source : 9ed60bd96f5e9a479771357e38b0b3b16abd351e
As of bug 1373150, l10n repacks do not require a anything to compile, so
they can stop downloading most toolchains from tooltool. However some
tools are still required, such as mozmake on Windows and DMG-related
tools on cross OSX.
--HG--
extra : rebase_source : f46e851c7941491530ce65490d0cfce4f9f02e35
In automation we should combine the standard logging and
the gecko log by default to ease the investigation of test
failures. It will also provide crash/assertion output
without having to search for it in other log files.
Also the custom error list has been replaced with the
default base and harness error lists as used by other
harnesses, which prevents false assumptions by the parser
when the trace log contains returns of expected errors.
MozReview-Commit-ID: 1rQ6maOqD3V
--HG--
extra : rebase_source : 77e94ffc6b77ac0467214321ed566f58c4e46f0e
(For Landing more OSX Nightly Support from date to central)
MozReview-Commit-ID: FSbQZ1Fbdcs
--HG--
extra : rebase_source : 3651dd368f032ae9f17cba42010902f850a64700
(For Landing more OSX Nightly Support from date to central)
MozReview-Commit-ID: FSbQZ1Fbdcs
--HG--
extra : rebase_source : 3651dd368f032ae9f17cba42010902f850a64700
Allow running |mach wpt| on one click loaners in order to run
web-platform-tests tests.
This implementation is just like the one for other testsuites using
thee packaged tests rather than the checkout that we get with wpt, at
least on Linux. That's also where the tests run from so it seems
reasonable for now. Moving to the checkout in the future could remove
some of the logic here by using a fake mozbuild environment so that
the testsuite itself doesn't have to implement anything much.
MozReview-Commit-ID: CaewrdjJ2ef
--HG--
extra : rebase_source : 491b8014d48f06ff5bd41b28cc985608981fbdf4
For a while now it has been making the content process sandbox less strict.
MozReview-Commit-ID: Am6fGzViaLk
--HG--
extra : rebase_source : 0bc037f205896c866559a7ab1f7e2c042c3142db
Mike Hommey
Rail Aliiev
Haik Aftandilian
Ryan VanderMeulen
Sebastian Hengst
Gregory Szorc
Gian-Carlo Pascutto
Tom Prince
Nick Alexander
Rob Thijssen
Marco Castelluccio
Chris AtLee
Geoff Brown
Greg Mierzwinski
Bob Clary
Alex Gaynor
Wes Kocher
rforbes
Wander Lairson Costa
Maja Frydrychowicz
Carsten "Tomcat" Book
Justin Wood
James Graham
Bryce Van Dyk
Henrik Skupin
Rob Wood