* run-ui-test-nightly
* Run ui tests on nightly build
* set correct number of shard according to tests running
* fix typo
* removing testing file
Co-authored-by: isabel rios <isabelrios@MBP-de-isabel-2.home>
Let's make mozilla-releng/staging-fenix the official staging repository.
By supporting it in the automation, we no longer need to maintain a
staging patchset to test things properly.
This PR builds on [AC##9024][1], and implements setting the Nimbus endpoints from [a secret set at build time][2].
For production use, this requires a secret named `nimbus_url` to be put into CI.
Note: Nimbus is currently behind a feature flag.
If developers wish to use a Nimbus server for local development, you can set the url by adding an entry into local.properties, e.g.:
```
nimbus.remote-settings.url=https://settings.stage.moz4ws.net
```
Without setting server, Nimbus will be able to function, except no experimental definitions will be fetched, and features under experiment will be configured as if not enrolled in the experiment.
[1]: https://github.com/mozilla-mobile/android-components/pull/9024
[2]: https://groups.google.com/a/mozilla.com/g/android-components-team/c/lAGVKQy8aiA/m/rY3uGAwhBAAJ
* Enable webrender for all tests and run a subset without webrender.
* Run tests on PR.
* Change task labels for webrender-enabled tests.
* Move transform logic to after the main transform.
* Reformat group symbol.
* Check if extra field is empty.
* Try a different method for treeherder info.
* Fix up assignment issue.
* Reformat symbol field instead of groupSymbol.
* Add new task group to config.
* Change the platform name for webrender tasks.
* Undo testing changes.
* Undo platform naming changes.
`assemble` doesn't assemble the tests so we need to run `test`.
`testClasses` isn't good enough because, according to `--profile`, it
doesn't include dependencies for `testRuntimeClasspath`.
Currently, push-apk fails to verify its chain of trust if github tagging
is done before it runs. Until this is fixed, we need to make sure
tagging is blocked on pushing.
* Add new per-commit android-test build.
* Rename to nightly-simulation.
* Add treeherder group to the config file.
* Remove taskcluster index path and browsertime test.
* Add nightly-simulation to taskcluster indexes.
Initially we didn't want to do that since we do not need to cache dependencies from our own
maven repository. But Android Components can introduce other third-party transitive
dependencies from other repositories (like Android X) and those need to be cached.
* Use nightly Fenix variant.
* Run the tests in PR.
* Update visual-metrics scripts to include the similarity metrics.
* Use python3.5 in visual-metrics docker.
* Install wget in the docker.
* Use python3.6 hashes instead of python3.5.
* Undo run-visual-metrics.py python changes.
* Upgrade python setuptools version to 46.1.3.
* Add setuptools to transitive dependency list.
* Undo PR test changes.
* Remove setuptools install line and use requirements.txt instead.
* Undo PR test changes.
* Fix geckodriver artifact suffix.
* Test a browsertime task.
* Revert browsertime test.
* Add google-search-restaurants to pageload tests in browsertime.
* Temporarily change the activity to pass tests.
* Change Raptor Fenix activity name.
* Remove test trigger for browsertime test.
fix: flank_snapshot requires direct shard value
-1 shards -> 50 shards
fix: adjust flank-x86.yml shard value
try old results generator in flank-x86.yml
fix: legacy-junit-report -> legacy-junit-result
revert to modern reporting
* Add visual-metrics docker type.
* Add required browsertime toolchain fetches.
* Add browsertime tests for technical and visual metrics.
* Run browsertime tests in a cron task.
* Run visual metrics on all browsertime tests.
* Use spaces instead of tabs, and resolve visual-metric nits.
* Enable browsertime on pull request for testing.
* Restrict PR tests to amazon on browsertime.
* First attempt using multi_dep.
* Add a primary dependency to browsertime.
* Try by not popping.
* Debug prints.
* Make one grouping per browsertime task.
* Try without the multi_dep transform.
* Delete dependent-tasks in visual-metrics transformer.
* Update setuptools installed and copy run-on-tasks-for.
* Use get when getting run-on-tasks-for.
* Add new pinned requirements.
* Try it.
* Set run-on-tasks-for properly.
* Remove print statement.
* Remove single_dep loader, and print statements.
* Remove run-on-tasks-for testing setting.
* Restart testing, and set user to root in visual-metrics Docker.
* Remove testing settings.
* Remove fetch-content from Docker.
* Change attributes grouping method.
* Run all tests as a check.
* Undo testing changes, and fix a bad test name.
There were a couple of errors in the original pull request for this bug:
- The raptor tasks had duplicated dependencies.
- The filename of the minidump_stackwalk artifact was incorrect.
The mozilla-central ffmpeg toolchain (used in Bug 1613479/#8780) has an
artifact that does not start with `public/build/` (it starts with just
`public/`). To easily support that, we want to set the `toolchain-artfiact`
attribute for that task.
We switched `index_search` to be a job-type in
[taskgraph](932b4cf48c)
which pass through `attributes` from the task definition (and is also more
future proof for adding fenix-specific toolchain tasks). This updates taskgraph
and the consumers of the current toolchain.
