jit/performance/codequality/benchmarksgame/k-nucleotide/k-nucleotide-9/k-nucleotide-9.sh

[runfoapp]

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

[ghost]

Tagging subscribers to this area: @JulieLeeMSFT
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Runfo Creating Tracking Issue (data being generated)

Author:	runfoapp[bot]
Assignees:	-
Labels:	area-CodeGen-coreclr, untriaged
Milestone:	-

[AndyAyersMS]

Updated area path.

[agocke]

@SamMonoRT This looks to still be failing, can you assign it for investigation?

[SamMonoRT]

Assigning to @naricc --- this test seems to be disabled on Android, iOS, WASM(https:/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]

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]

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]

cc @naricc - seems like an issues.target grouping issue to me. Shouldn't all mono runtime tests overrule the sub categorization?

[SamMonoRT]

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]

Checked the test locally repeatedly and in CI (including extra-platforms). No failures were encountered. Reenabled test in #87058. Closing.