kfdtest: Disable tests that cause unwanted behavior

disable KFDLocalMemoryTest.Fragmentation and
KFDEventTest.MeasureInterruptConsumption as
part of the  KFD test suite improvement feature

Signed-off-by: Apurv Mishra <Apurv.Mishra@amd.com>
This commit is contained in:
Apurv Mishra
2025-05-08 14:45:17 -04:00
کامیت شده توسط Mishra, Apurv
والد d54124383f
کامیت f853dda9ba
3فایلهای تغییر یافته به همراه3 افزوده شده و 9 حذف شده
@@ -34,10 +34,6 @@ FILTER[core]=\
# FILTER[pm] need human intervention, so put it here. Developers can run them
# manually through "-p pm" option.
#
# Fragmentation test fails intermittently on different systems (see KFD-344). It
# stresses memory management in unusual ways by having lots of memory allocated but
# not mapped, which is not relevant to compute applications over ROCr.
#
# CU Masking Linear are not working correctly due to how the HW distributes work over CUs.
# They are available for testing but are not currently expected to pass on CI/VI/AI.
#
@@ -48,9 +44,7 @@ FILTER[core]=\
# The CheckZeroInitializationVram test is no longer expected to pass as KFD no longer
# clears memory at allocation time.
PERMANENT_BLACKLIST_ALL_ASICS=\
"-KFDEventTest.MeasureInterruptConsumption:"\
"${FILTER[pm]}:"\
"KFDLocalMemoryTest.Fragmentation:"\
"-${FILTER[pm]}:"\
"KFDQMTest.BasicCuMaskingLinear:"\
"KFDQMTest.BasicCuMaskingEven:"\
"RDMATest.GPUDirect:"\
@@ -334,7 +334,7 @@ exit:
}
};
TEST_F(KFDEventTest, MeasureInterruptConsumption) {
TEST_F(KFDEventTest, DISABLED_MeasureInterruptConsumption) {
TEST_START(TESTPROFILE_RUNALL);
QueueAndSignalBenchmark latencyBench(128);
QueueAndSignalBenchmark sustainedBench(4095);
@@ -435,7 +435,7 @@ static void Fragmentation(KFDTEST_PARAMETERS* pTestParamters){
EXPECT_SUCCESS_GPU(queue.Destroy(), gpuNode);
}
TEST_F(KFDLocalMemoryTest, Fragmentation) {
TEST_F(KFDLocalMemoryTest, DISABLED_Fragmentation) {
TEST_REQUIRE_ENV_CAPABILITIES(ENVCAPS_64BITLINUX);
TEST_START(TESTPROFILE_RUNALL);