fix: flaky metric test

Author: alkatrivedi

test/metrics/metrics.ts

@@ -293,7 +293,7 @@ describe('Test metrics with mock server', () => {
           attributes,
         );
         // Since we only have one attempt, the attempt latency should be fairly close to the operation latency
-        assertApprox(MIN_LATENCY, attemptLatency, 30);
+        assertApprox(operationLatency, attemptLatency, 30);
 
         const gfeLatency = getAggregatedValue(gfeLatenciesData, attributes);
         assert.strictEqual(gfeLatency, 123);
@@ -303,7 +303,7 @@ describe('Test metrics with mock server', () => {
       });
 
       // check that the latency matches up with the measured elapsed time within 10ms
-      assertApprox(elapsedTime, totalOperationLatency, 10);
+      assertApprox(elapsedTime, totalOperationLatency, 50);
 
       // Make sure no GFE/AFE connectivity errors ar emitted since we got GFE latencies
       const gfeMissingData = hasMetricData(
@@ -710,7 +710,7 @@ describe('Test metrics with mock server', () => {
           attributes,
         );
         // Since we only have one attempt, the attempt latency should be fairly close to the operation latency
-        assertApprox(MIN_LATENCY, attemptLatency, 30);
+        assertApprox(operationLatency, attemptLatency, 30);
 
         const gfeLatency = getAggregatedValue(gfeLatenciesData, attributes);
         assert.strictEqual(gfeLatency, 123);