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

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

24 строки
698 B
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 835930 - move b2g unittest profile handling on top of mozbase instead of automation.py, r=jgriffin
2013-03-29 00:42:49 +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 1459598 - Use profiles.json file to map test suites to the base profiles they use, r=jgraham This serves two purposes: 1) It makes web-platform-tests pref downloading/handling a little more robust. When run externally, it now downloads the entire testing/profiles directory. When loading prefs it will look for both prefs_general.js (to support older versions of Firefox) and profiles.json (for support moving forward). This way we can add/remove/rename pref files under these directories without needing to worry about breaking upstream wpt. 2) It provides developers an overview of which harnesses are using which base profiles. Instead of hunting through test harness code to find this information, they can glance at profiles.json. MozReview-Commit-ID: AMzdnD8aGA2 --HG-- extra : rebase_source : 6fa0a802680417e49fcef99f3d03de7458a8fcba
2018-05-07 16:43:12 +03:00
profile_files = [
Bug 1460914 - [xpcshell] Define preferences in testing/profiles instead of testing/xpcshell/head.js, r=ted This commit creates an empty 'base' profile because I wanted to preserve the ability to apply a pref to all test harnesses on try. Since xpcshell doesn't share many prefs with the other harnesses, it can't use the common profile. So adding a pref to 'common' will apply it everywhere except xpcshell. Adding a pref to 'base' will apply it everywhere including xpcshell. These profiles are starting to get a bit messy, but I'd like to punt re-organizing them to a follow-up bug. Depends on D9716 Differential Revision: https://phabricator.services.mozilla.com/D9717 --HG-- extra : moz-landing-system : lando
2018-10-26 20:47:18 +03:00
'base/*',
Bug 1451159 - [testing/profiles] Store profile data in actual profile look alike folders r=gbrown This moves testing/profiles/prefs_general.js to testing/profiles/common/user.js. It also adds an 'extensions' folder to the common profile. Dropping extension files here will get them installed in all test harnesses (useful for testing on try). The idea is that all test harnesses will eventually use this 'common' profile. We'll also create some new per harness profiles, e.g testing/profiles/mochitest and testing/profiles/reftest. This way there will be a single location developers can go to set preferences, both for a specific harness, and across all harnesses. MozReview-Commit-ID: 8sqBqLiypgU --HG-- rename : testing/profiles/prefs_general.js => testing/profiles/common/user.js extra : rebase_source : 72a4a4b691e93c77479c7e70647b0ca373862c51
2018-04-19 23:12:26 +03:00
'common/*',
Bug 1458571 - Use base testing/profiles in talos, r=rwood This moves all of the global prefs that were previously defined in testing/talos/talos/config.py, into a new "perf" profile under testing/profiles/perf/user.js. This perf profile will be shared with raptor, so changes to one framework will result in changes to the other. MozReview-Commit-ID: JRxZEDlPu6b --HG-- extra : rebase_source : 38f61eb6f9dd3e8dd9e0425ffe32dbdf845fcf65
2018-05-09 22:06:53 +03:00
'perf/*',
Bug 1459598 - Use profiles.json file to map test suites to the base profiles they use, r=jgraham This serves two purposes: 1) It makes web-platform-tests pref downloading/handling a little more robust. When run externally, it now downloads the entire testing/profiles directory. When loading prefs it will look for both prefs_general.js (to support older versions of Firefox) and profiles.json (for support moving forward). This way we can add/remove/rename pref files under these directories without needing to worry about breaking upstream wpt. 2) It provides developers an overview of which harnesses are using which base profiles. Instead of hunting through test harness code to find this information, they can glance at profiles.json. MozReview-Commit-ID: AMzdnD8aGA2 --HG-- extra : rebase_source : 6fa0a802680417e49fcef99f3d03de7458a8fcba
2018-05-07 16:43:12 +03:00
'profiles.json',
Bug 905404 - [pgo] Add custom profile data in testing/profiles/profileserver. r=ahal Add extra preferences for the profileserver script on-top of the ones as inheritted from unittests. --HG-- extra : rebase_source : 02d3297134e82c2425fc4c6c939cc5d0cc4a2c13 extra : histedit_source : 07f699b0ff8bec2a6eda7705a0fa13fb3b352f98
2018-09-06 09:47:46 +03:00
'profileserver/*',
Bug 1460912 - [reftest] Use base profiles in reftest r=gbrown This moves reftest-preferences.js to: testing/profiles/reftest/user.js Developers can also now add extensions to: testing/profiles/reftest/extensions MozReview-Commit-ID: IVLsT5MWtcJ --HG-- rename : layout/tools/reftest/reftest-preferences.js => testing/profiles/reftest/user.js extra : rebase_source : 1725627d439998d92545e0d4693fbb76a266945f
2018-05-07 23:10:29 +03:00
'reftest/*',
Bug 1458571 - Make talos and raptor use the 'common' base profile, r=rwood This factors out the prefs that are common across raptor, talos and mochitest/web-platform-tests. In order to do this a new "unittest" profile has been created. This means, to set a pref across everything that uses this system, edit: testing/profiles/common/user.js To set a pref across unittest frameworks (which excludes raptor and talos), edit: testing/profiles/unittest/user.js Setting a pref for perf frameworks only remains the same. Extensions follow the same rules (drop them in <profile>/extensions). MozReview-Commit-ID: 6AHlYsN0Lb8 --HG-- extra : rebase_source : aad259f06af549f3bc707fed5b1caaacf25bc28f
2018-05-10 22:31:31 +03:00
'unittest/*',
Bug 905404 - [wpt] Add custom profile data in testing/profiles/web-platform. r=jgraham Add extra preferences for web-platform-tests on-top of the ones as inheritted from unittests. --HG-- extra : rebase_source : 6a1f6828eb52120f9a2029be8220931cd2ca0f69 extra : histedit_source : 5f219cbd34039c79c624bee35f3b56700bde903e
2018-09-06 09:44:52 +03:00
'web-platform/*'
Bug 1109831 - move testing/profiles/ files to moz.build's TEST_HARNESS_FILES; r=mshal
2014-12-10 21:58:51 +03:00
]
Bug 1460912 - [reftest] Use base profiles in reftest r=gbrown This moves reftest-preferences.js to: testing/profiles/reftest/user.js Developers can also now add extensions to: testing/profiles/reftest/extensions MozReview-Commit-ID: IVLsT5MWtcJ --HG-- rename : layout/tools/reftest/reftest-preferences.js => testing/profiles/reftest/user.js extra : rebase_source : 1725627d439998d92545e0d4693fbb76a266945f
2018-05-07 23:10:29 +03:00
TEST_HARNESS_FILES.reftest.profile_data += profile_files
Bug 1459598 - Use profiles.json file to map test suites to the base profiles they use, r=jgraham This serves two purposes: 1) It makes web-platform-tests pref downloading/handling a little more robust. When run externally, it now downloads the entire testing/profiles directory. When loading prefs it will look for both prefs_general.js (to support older versions of Firefox) and profiles.json (for support moving forward). This way we can add/remove/rename pref files under these directories without needing to worry about breaking upstream wpt. 2) It provides developers an overview of which harnesses are using which base profiles. Instead of hunting through test harness code to find this information, they can glance at profiles.json. MozReview-Commit-ID: AMzdnD8aGA2 --HG-- extra : rebase_source : 6fa0a802680417e49fcef99f3d03de7458a8fcba
2018-05-07 16:43:12 +03:00
TEST_HARNESS_FILES.testing.mochitest.profile_data += profile_files
TEST_HARNESS_FILES['web-platform'].prefs += profile_files
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 1459598 - Use profiles.json file to map test suites to the base profiles they use, r=jgraham This serves two purposes: 1) It makes web-platform-tests pref downloading/handling a little more robust. When run externally, it now downloads the entire testing/profiles directory. When loading prefs it will look for both prefs_general.js (to support older versions of Firefox) and profiles.json (for support moving forward). This way we can add/remove/rename pref files under these directories without needing to worry about breaking upstream wpt. 2) It provides developers an overview of which harnesses are using which base profiles. Instead of hunting through test harness code to find this information, they can glance at profiles.json. MozReview-Commit-ID: AMzdnD8aGA2 --HG-- extra : rebase_source : 6fa0a802680417e49fcef99f3d03de7458a8fcba
2018-05-07 16:43:12 +03:00
BUG_COMPONENT = ("Testing", "General")