These tests cause test timeouts on TaskCluster with Rust Beta.
We don't know yet why, they run fine on CircleCI/Rust Stable.
We ignore them for the time being, but explicitly run them on CI.
This is a partial revert of 796716c
Rust's libstd is built against a lower NDK.
Newer NDKs have replaced libgcc with libunwind. This breaks the built
now (see https://github.com/rust-lang/rust/pull/85806).
Additionally some tooling changed so now the rust-android-gradle plugin breaks.
For now we drop back to the old NDK until we invest time to do a proper
upgrade.
This effectively enables safe-mode everywhere, forcing migration from
LDMB to safe-mode in clients.
Note:
The iOS build was one of the last ones that really used LMDB mode.
Standalone Android builds also uses LMDB mode.
Other Android builds are shipped through GeckoView, where safe-mode was already
enabled.
This crate should be used as a build dependency in Rust consumers.
In their `build.rs` they can call the builder to auto-generate code from
`metrics.yaml` and `pings.yaml` definitions:
glean_build::Builder::default()
.metrics("metrics.yaml")
.pings("pings.yaml")
.generate()
.expect("Error generating Glean Rust bindings");
This requires a working Python3 & pip installation.
Windows untested.
Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1713573 and https://bugzilla.mozilla.org/show_bug.cgi?id=1772566
Recent Rust/Cargo changed detection of available cores,
which is probably the cause of earlier CPU/memory exhaustion kills.
By manually limiting it to 6 jobs we stay within the limits, while
keeping about the same runtime.
Upstream bug: https://github.com/rust-lang/rust/issues/97549
Only 2 dependencies left:
* Testing only: OHHTTPStubs for network mocking
* GzipSwift: for TestUtils to decode gzip'ed payloads
Both are available as Swift packages, so we can consume them that way.
* Support Python 3.10
This also uses the "next gen" Python Docker images from CircleCI.
Also removes some `persist_to_workspace` that is no longer needed.
* Fix YAML syntax
* Don't use sudo
* Use legacy Docker images for Windows tests
* Use next gen images for Windows
* Use wine-stable
* Remove comment