From 152edb838bd0b317a62446c5161686cf7a3b3eb4 Mon Sep 17 00:00:00 2001 From: Roberto Dip Date: Fri, 1 Mar 2024 17:54:42 -0300 Subject: [PATCH] fix flaky MDM test (#17307) this one seems to be specially flaky and is blocking a couple of PRs from being merged. --- server/service/integration_mdm_test.go | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/server/service/integration_mdm_test.go b/server/service/integration_mdm_test.go index aba846f09e..e7ac0782f0 100644 --- a/server/service/integration_mdm_test.go +++ b/server/service/integration_mdm_test.go @@ -2313,8 +2313,7 @@ func (s *integrationMDMTestSuite) TestDEPProfileAssignment() { // - existing device with "added" // - new device with "added" require.Len(t, profileAssignmentReqs[ix2Devices].Devices, 2, "%#+v", profileAssignmentReqs) - require.Equal(t, devices[0].SerialNumber, profileAssignmentReqs[ix2Devices].Devices[0]) // FIXME: this test seems to be flaky - require.Equal(t, addedSerial, profileAssignmentReqs[ix2Devices].Devices[1]) + require.ElementsMatch(t, []string{devices[0].SerialNumber, addedSerial}, profileAssignmentReqs[ix2Devices].Devices) checkHostDEPAssignProfileResponses(profileAssignmentReqs[ix2Devices].Devices, profileAssignmentReqs[ix2Devices].ProfileUUID, fleet.DEPAssignProfileResponseSuccess) // - existing device with "modified" and a different team (thus different profile request)