mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/testing/mozbase/moz.build

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

70 строки
1.8 KiB
Plaintext
Исходник Обычный вид История

Bug 1286877 - do not set c-basic-offset for python-mode; r=gps This removes the unnecessary setting of c-basic-offset from all python-mode files. This was automatically generated using perl -pi -e 's/; *c-basic-offset: *[0-9]+//' ... on the affected files. The bulk of these files are moz.build files but there a few others as well. MozReview-Commit-ID: 2pPf3DEiZqx --HG-- extra : rebase_source : 0a7dcac80b924174a2c429b093791148ea6ac204
2016-07-14 19:16:42 +03:00
# -*- Mode: python; indent-tabs-mode: nil; tab-width: 40 -*-
Bug 784841 - Part 18η: Convert /testing; r=ted
2013-02-26 01:05:39 +04:00
# vim: set filetype=python:
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
Bug 1317970 - Use manifestparser manifests for python unit tests, r=chmanchester This deprecates PYTHON_UNIT_TESTS and replaces it with PYTHON_UNITTEST_MANIFESTS. In the build system, this means python unittests will be treated the same as all other test suites that use manifestparser. New manifests called 'python.ini' have been created for all test directories containing python unittests. MozReview-Commit-ID: IBHG7Thif2D --HG-- extra : rebase_source : 11a92a2bc544d067946bbd774975140147458caa
2016-11-16 17:59:22 +03:00
PYTHON_UNITTEST_MANIFESTS += [
"manifestparser/tests/manifest.ini",
"mozcrash/tests/manifest.ini",
Bug 1412012 - [mozdebug] Add a basic test for get_default_debugger_name, r=jmaher MozReview-Commit-ID: CwkXKJWd55M --HG-- extra : rebase_source : e933232fff154d933953f238da14318d7ed2d0fe
2017-10-26 17:14:33 +03:00
"mozdebug/tests/manifest.ini",
Bug 1488590 - Add tests to mozdevice::adb.py r=ahal Created tests/ subdirectory under mozdevice. Added conftest.py and populated with wrappers for the methods under test. Added test_socket_connections.py with basic tests for new methods and some coverage of legacy/deprecated methods. Differential Revision: https://phabricator.services.mozilla.com/D5165 --HG-- extra : moz-landing-system : lando
2018-09-18 22:35:40 +03:00
"mozdevice/tests/manifest.ini",
Bug 1317970 - Use manifestparser manifests for python unit tests, r=chmanchester This deprecates PYTHON_UNIT_TESTS and replaces it with PYTHON_UNITTEST_MANIFESTS. In the build system, this means python unittests will be treated the same as all other test suites that use manifestparser. New manifests called 'python.ini' have been created for all test directories containing python unittests. MozReview-Commit-ID: IBHG7Thif2D --HG-- extra : rebase_source : 11a92a2bc544d067946bbd774975140147458caa
2016-11-16 17:59:22 +03:00
"mozfile/tests/manifest.ini",
Bug 1628073 - Move gecko profiler testing files to mozgeckoprofiler; r=sparky,perftest-reviewers,gbrown I need to add symbolication support for the mochitest Gecko Profiler command line option. These profiles also need to be symbolicated. Unfortunately, there is not a common place where I could use these files. Talos and Raptor each had their own copy of the snappy symbolication server. This commit consolidates these packages into a re-usable mozbase package that can be used in mochitests, and eventually in other places like xpcshell tests. I stubbed out a test file, but it doesn't do anything quite yet. This commit makes it so that the tests still work in Raptor and Talos, but doesn't add any features. It also doesn't try too hard to make the files look like a mozbase package. Differential Revision: https://phabricator.services.mozilla.com/D74289
2020-05-22 16:18:44 +03:00
"mozgeckoprofiler/tests/manifest.ini",
Bug 1317970 - Use manifestparser manifests for python unit tests, r=chmanchester This deprecates PYTHON_UNIT_TESTS and replaces it with PYTHON_UNITTEST_MANIFESTS. In the build system, this means python unittests will be treated the same as all other test suites that use manifestparser. New manifests called 'python.ini' have been created for all test directories containing python unittests. MozReview-Commit-ID: IBHG7Thif2D --HG-- extra : rebase_source : 11a92a2bc544d067946bbd774975140147458caa
2016-11-16 17:59:22 +03:00
"mozhttpd/tests/manifest.ini",
"mozinfo/tests/manifest.ini",
"mozinstall/tests/manifest.ini",
Bug 1507550 - Scrub out junk from rust signatures when processing LSAN data, r=mccr8 Rust signatures aren't properly demangled, and contain some trailing data that seems to depend on the compiler version. This defeats the attempt to allow LSAN errors when importing tests, and we end up adding multiple variants of the same symbol to the allow list. To avoid this, simply preprocess the symbols not to contain the trailing junk when reading LSAN output, whilst we await better demangling. Differential Revision: https://phabricator.services.mozilla.com/D12303
2018-11-19 18:29:46 +03:00
"mozleak/tests/manifest.ini",
Bug 1317970 - Use manifestparser manifests for python unit tests, r=chmanchester This deprecates PYTHON_UNIT_TESTS and replaces it with PYTHON_UNITTEST_MANIFESTS. In the build system, this means python unittests will be treated the same as all other test suites that use manifestparser. New manifests called 'python.ini' have been created for all test directories containing python unittests. MozReview-Commit-ID: IBHG7Thif2D --HG-- extra : rebase_source : 11a92a2bc544d067946bbd774975140147458caa
2016-11-16 17:59:22 +03:00
"mozlog/tests/manifest.ini",
"moznetwork/tests/manifest.ini",
Bug 1567954 - Part 1: Initialize Mozpower module and implement PowerBase class. r=perftest-reviewers,ahal,rwood This patch initializes the Mozpower module and implements the PowerBase class. This class is used as a base for subclasses that implement power measurement tooling for various OS and CPU combinations. Differential Revision: https://phabricator.services.mozilla.com/D39191 --HG-- extra : moz-landing-system : lando
2019-08-01 23:36:00 +03:00
"mozpower/tests/manifest.ini",
Bug 1317970 - Use manifestparser manifests for python unit tests, r=chmanchester This deprecates PYTHON_UNIT_TESTS and replaces it with PYTHON_UNITTEST_MANIFESTS. In the build system, this means python unittests will be treated the same as all other test suites that use manifestparser. New manifests called 'python.ini' have been created for all test directories containing python unittests. MozReview-Commit-ID: IBHG7Thif2D --HG-- extra : rebase_source : 11a92a2bc544d067946bbd774975140147458caa
2016-11-16 17:59:22 +03:00
"mozprocess/tests/manifest.ini",
"mozprofile/tests/manifest.ini",
Bug 1528992 - extract raptor mitmproxy integration - r=rwood,Bebe,gbrown This patch moves testing/raptor/raptor/playback into its own testing package in testing/mozbase/mozproxy so we can use the proxy in other places than Raptor. Differential Revision: https://phabricator.services.mozilla.com/D21200 --HG-- rename : testing/raptor/raptor/playback/__init__.py => testing/mozbase/mozproxy/mozproxy/__init__.py rename : testing/raptor/raptor/playback/base.py => testing/mozbase/mozproxy/mozproxy/backends/base.py rename : testing/raptor/raptor/playback/mitmproxy.py => testing/mozbase/mozproxy/mozproxy/backends/mitm.py rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-linux64.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-linux64.manifest rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-osx.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-osx.manifest rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-win.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-win.manifest rename : testing/raptor/raptor/playback/mitmproxy_requirements.txt => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy_requirements.txt extra : moz-landing-system : lando
2019-03-06 20:13:21 +03:00
"mozproxy/tests/manifest.ini",
Bug 1317970 - Use manifestparser manifests for python unit tests, r=chmanchester This deprecates PYTHON_UNIT_TESTS and replaces it with PYTHON_UNITTEST_MANIFESTS. In the build system, this means python unittests will be treated the same as all other test suites that use manifestparser. New manifests called 'python.ini' have been created for all test directories containing python unittests. MozReview-Commit-ID: IBHG7Thif2D --HG-- extra : rebase_source : 11a92a2bc544d067946bbd774975140147458caa
2016-11-16 17:59:22 +03:00
"mozrunner/tests/manifest.ini",
[mozsystemmonitor] Add test manifest to testing/mozbase/moz.build (bug 1471916) r=davehunt Currently, tests in mozsystemmonitor are skipped because the manifest is missing from mozbase/moz.build. This has now been added. For the moment, this patch also skips the test if run against Python 3. This is not ideal - a better fix may be setting the unittest.skipIf condition to skip if the there is simply a failure when run with Python 3. Differential Revision: https://phabricator.services.mozilla.com/D22426 --HG-- extra : moz-landing-system : lando
2019-03-25 16:49:38 +03:00
"mozsystemmonitor/tests/manifest.ini",
Bug 1317970 - Use manifestparser manifests for python unit tests, r=chmanchester This deprecates PYTHON_UNIT_TESTS and replaces it with PYTHON_UNITTEST_MANIFESTS. In the build system, this means python unittests will be treated the same as all other test suites that use manifestparser. New manifests called 'python.ini' have been created for all test directories containing python unittests. MozReview-Commit-ID: IBHG7Thif2D --HG-- extra : rebase_source : 11a92a2bc544d067946bbd774975140147458caa
2016-11-16 17:59:22 +03:00
"moztest/tests/manifest.ini",
"mozversion/tests/manifest.ini",
Bug 1044657 - Move PYTHON_UNIT_TESTS to moz.build; r=mshal As a first step, this moves PYTHON_UNIT_TESTS to moz.build as a passthru variable. In the future, we could hook it up to |mach test|. The __init__.py files may not need to be in the list, but I don't want to change the list here.
2014-07-28 19:51:12 +04:00
]
Bug 976733 - part 3 - convert testing/mozbase/ to use TEST_HARNESS_FILES; r=gps
2014-08-29 19:03:11 +04:00
python_modules = [
"manifestparser",
"mozcrash",
"mozdebug",
"mozdevice",
"mozfile",
Bug 1628073 - Move gecko profiler testing files to mozgeckoprofiler; r=sparky,perftest-reviewers,gbrown I need to add symbolication support for the mochitest Gecko Profiler command line option. These profiles also need to be symbolicated. Unfortunately, there is not a common place where I could use these files. Talos and Raptor each had their own copy of the snappy symbolication server. This commit consolidates these packages into a re-usable mozbase package that can be used in mochitests, and eventually in other places like xpcshell tests. I stubbed out a test file, but it doesn't do anything quite yet. This commit makes it so that the tests still work in Raptor and Talos, but doesn't add any features. It also doesn't try too hard to make the files look like a mozbase package. Differential Revision: https://phabricator.services.mozilla.com/D74289
2020-05-22 16:18:44 +03:00
"mozgeckoprofiler",
Backed out changeset 200da85932e9 (bug 1230862) for valgrind perma failures
2016-02-10 13:04:50 +03:00
"mozhttpd",
Bug 976733 - part 3 - convert testing/mozbase/ to use TEST_HARNESS_FILES; r=gps
2014-08-29 19:03:11 +04:00
"mozinfo",
"mozinstall",
Bug 1091274 - Move leak log functions out of automationutils and into mozbase. r=jgriffin
2015-07-03 08:04:22 +03:00
"mozleak",
Bug 976733 - part 3 - convert testing/mozbase/ to use TEST_HARNESS_FILES; r=gps
2014-08-29 19:03:11 +04:00
"mozlog",
"moznetwork",
Bug 1567954 - Part 1: Initialize Mozpower module and implement PowerBase class. r=perftest-reviewers,ahal,rwood This patch initializes the Mozpower module and implements the PowerBase class. This class is used as a base for subclasses that implement power measurement tooling for various OS and CPU combinations. Differential Revision: https://phabricator.services.mozilla.com/D39191 --HG-- extra : moz-landing-system : lando
2019-08-01 23:36:00 +03:00
"mozpower",
Bug 976733 - part 3 - convert testing/mozbase/ to use TEST_HARNESS_FILES; r=gps
2014-08-29 19:03:11 +04:00
"mozprocess",
"mozprofile",
Bug 1528992 - extract raptor mitmproxy integration - r=rwood,Bebe,gbrown This patch moves testing/raptor/raptor/playback into its own testing package in testing/mozbase/mozproxy so we can use the proxy in other places than Raptor. Differential Revision: https://phabricator.services.mozilla.com/D21200 --HG-- rename : testing/raptor/raptor/playback/__init__.py => testing/mozbase/mozproxy/mozproxy/__init__.py rename : testing/raptor/raptor/playback/base.py => testing/mozbase/mozproxy/mozproxy/backends/base.py rename : testing/raptor/raptor/playback/mitmproxy.py => testing/mozbase/mozproxy/mozproxy/backends/mitm.py rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-linux64.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-linux64.manifest rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-osx.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-osx.manifest rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-win.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-win.manifest rename : testing/raptor/raptor/playback/mitmproxy_requirements.txt => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy_requirements.txt extra : moz-landing-system : lando
2019-03-06 20:13:21 +03:00
"mozproxy",
Bug 976733 - part 3 - convert testing/mozbase/ to use TEST_HARNESS_FILES; r=gps
2014-08-29 19:03:11 +04:00
"mozrunner",
Bug 1091285 - move dumpScreen in a new mozscreenshot package. r=jgriffin This also completely remove build/automationutils.py. --HG-- extra : commitid : 50v6EAQNEHV extra : rebase_source : 4ac1347d73498f068979514c6afb16ac50ab4033
2015-07-29 18:50:16 +03:00
"mozscreenshot",
Bug 976733 - part 3 - convert testing/mozbase/ to use TEST_HARNESS_FILES; r=gps
2014-08-29 19:03:11 +04:00
"mozsystemmonitor",
"moztest",
"mozversion",
]
TEST_HARNESS_FILES.mozbase += [m + "/**" for m in python_modules]
TEST_HARNESS_FILES.mozbase += [
"setup_development.py",
]
Bug 1326465 - add BUG_COMPONENTS to testing/. r=gbrown,ted ensuring moz.build files have BUG_COMPONENTS for all files in the testing/ subdirectory is a win. There are a lot of older files and some files used in many harnesses. If the files are primarily used for mochitest, they are associated with the testing::mochitest component, otherwise I chose the testing::general component. There is an exception web-platform-tests, these have many test files that need to be matched to proper components. MozReview-Commit-ID: IIv9W2kEqeN
2016-12-31 00:16:56 +03:00
Bug 1413575: Add mozbase docs to sphinx tree. r=ahal MozReview-Commit-ID: 2RI2j3CpOhn --HG-- extra : rebase_source : e61e7e0d3f2200520034d2cc57eaf93e6eed8fdd
2017-11-20 20:12:06 +03:00
SPHINX_TREES["/mozbase"] = "docs"
Bug 1403519 - only build docs when necessary r=gps This marks **/docs/** as exclusively docs, and code that is autodoc'd as inclusively docs. That means that a change that purely modifies documentation files will *only* run `docs` tasks, while a change that modifies autodoc'd source code will *additionaly* run `docs` tasks. The tasks do not run by default. MozReview-Commit-ID: G9tOK0AwtrI --HG-- extra : rebase_source : 8dd971e5c9b0eb5f47895664a4ea49442f303ecb extra : source : 0881de9b2b5e36ec37cc866f1d4af109da57a919
2017-10-02 21:22:56 +03:00
with Files("docs/**"):
SCHEDULES.exclusive = ["docs"]
Bug 1326465 - add BUG_COMPONENTS to testing/. r=gbrown,ted ensuring moz.build files have BUG_COMPONENTS for all files in the testing/ subdirectory is a win. There are a lot of older files and some files used in many harnesses. If the files are primarily used for mochitest, they are associated with the testing::mochitest component, otherwise I chose the testing::general component. There is an exception web-platform-tests, these have many test files that need to be matched to proper components. MozReview-Commit-ID: IIv9W2kEqeN
2016-12-31 00:16:56 +03:00
with Files("**"):
Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher This is needed before we can upgrade to flake8 3.3.0, as that version starts flagging these errors. These files were modified by running: autopep8 --select E305 --in-place -r <dir> on the affected directories. I did it one dir at a time and verified the result after each. MozReview-Commit-ID: FmlsfiKIbtr --HG-- extra : rebase_source : 9df32258cadff5d27a0e72113c57f782756c0b18
2017-06-15 19:10:59 +03:00
BUG_COMPONENT = ("Testing", "Mozbase")
Bug 1433974 - Update BUG_COMPONENT for some of the new Testing components, r=jmaher MozReview-Commit-ID: 7jQnnAhOzEr --HG-- extra : rebase_source : af1c9dca779c6089b5cc062eea81ef9945133d48
2018-01-29 20:57:54 +03:00
with Files("rust/**"):
BUG_COMPONENT = ("Testing", "Mozbase Rust")