Repository navigation
jit/performance/codequality/benchmarksgame/k-nucleotide/k-nucleotide-9/k-nucleotide-9.sh #67675
Description
Runfo Tracking Issue: jit/performance/codequality/benchmarksgame/k-nucleotide/k-nucleotide-9/k-nucleotide-9.sh
| Build | Definition | Kind | Run Name |
|---|
Build Result Summary
| Day Hit Count | Week Hit Count | Month Hit Count |
|---|---|---|
| 0 | 0 | 0 |
Activity
AndyAyersMS commentedon Apr 7, 2022
Updated area path.
agocke commentedon May 2, 2022
@SamMonoRT This looks to still be failing, can you assign it for investigation?
SamMonoRT commentedon May 2, 2022
Assigning to @naricc --- this test seems to be disabled on Android, iOS, WASM(https://github.com/dotnet/runtime/blob/main/src/tests/issues.targets), so not certain if this works in other configs. Could be a case of disabling the tests to get a Green CI for now, but we need to understand why it started failing.
@agocke - I verified my email, but don't seem to get access to the runfo tracking issue to see when the hits started. Is there a way to query for this test history, as to when it started failing, and is it failing deterministically on only certain lanes, possibly identify the first PR which hit the issue ?
SamMonoRT commentedon May 6, 2022
Failing test has been added to issues.target file to be excluded while we investigate. Removing blocking ci label and adding disabled-test instead.
jakobbotsch commentedon May 11, 2022
This failed again in https://dev.azure.com/dnceng/public/_build/results?buildId=1763118&view=results.
It looks like it should also be disabled under the "llvmfullaot" variant.
SamMonoRT commentedon May 11, 2022
cc @naricc - seems like an issues.target grouping issue to me. Shouldn't all mono runtime tests overrule the sub categorization?
SamMonoRT commentedon May 17, 2023
Don't see new recent failures, but we still need to understand why this fails for mono lanes. @jandupej to take a look whats needed to re-enable the test in CI pipelines
jandupej commentedon Jun 6, 2023
Checked the test locally repeatedly and in CI (including extra-platforms). No failures were encountered. Reenabled test in #87058. Closing.