runtime: Many Android JIT tests failing in CI
Configuration: Mono Android x64 Release @ Ubuntu.1804.Amd64.Android.Open
@akoeplinger @steveisok is this known?
Runfo Tracking Issue: Many Android JIT tests failing in CI
| Build | Definition | Kind | Run Name | Console | Core Dump | Test Results | Run Client |
|---|---|---|---|---|---|---|---|
| 956620 | runtime | PR 47182 | net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open | console.log | runclient.py | ||
| 945073 | runtime | PR 46810 | net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open | console.log | runclient.py | ||
| 944893 | runtime | PR 46810 | net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open | console.log | runclient.py |
Build Result Summary
| Day Hit Count | Week Hit Count | Month Hit Count |
|---|---|---|
| 0 | 0 | 0 |
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 26 (25 by maintainers)
Commits related to this issue
- Copy OpenSSL binaries (#44577) This PR could resolve some failures mentioned in https://github.com/dotnet/runtime/issues/44306 — committed to dotnet/runtime by fanyang-mono 4 years ago
- Ingest dotnet/runtime master (#385) * Remove dead code in MarshalNative (#44506) * Update buildtriage.md (#44538) * Remove internal NuGet.config that is not needed anymore (#44507) * Convert... — committed to dotnet/runtimelab by layomia 4 years ago
- Copy OpenSSL binaries (#44577) This PR could resolve some failures mentioned in https://github.com/dotnet/runtime/issues/44306 — committed to Rattenkrieg/runtime by fanyang-mono 4 years ago
Definitely seeing a bit more instability today. Moving to the staging pipeline will help.
AzDO REST APIs or Kusto. You will likely need to write a custom query to filter on just the android runtime tests.
Yeah. I should have that done by today 😄
Alex put up a PR to bump the simulator RAM size to 3GB.
https://dev.azure.com/dnceng/internal/_git/dotnet-helix-machines/pullrequest/11307?_a=files
I’m trying to sort through the recent data first and that may help what a good follow up action will be.
@ViktorHofer all of the failures from https://github.com/dotnet/runtime/pull/43740 are known, we’re iterating on replacing OpenSSL on Android there.