test: skipped

Author: aryamohanan

packages/collector/test/tracing/protocols/http/client/test.js

@@ -1037,7 +1037,6 @@ function registerConnectionRefusalTest(appUsesHttps) {
                 span => expect(span.n).to.equal('node.http.client'),
                 span => expect(span.k).to.equal(constants.EXIT),
                 span => expect(span.ec).to.equal(1),
-                // Native fetch wraps connection errors with "fetch failed" message
                 span => expect(span.data.http.error).to.contains('Request cannot be constructed')
               ]);
             })

packages/collector/test/tracing/protocols/http/proxy/test.js

@@ -199,7 +199,7 @@ const mochaSuiteFn = supportedVersion(process.versions.node) ? describe : descri
               agentControls.getSpans().then(spans => {
                 // Note: With native fetch, a client span is created even for malformed URLs
                 // because fetch returns a rejected promise rather than throwing synchronously.
-                // This differs from node-fetch v2 behavior where no span was created.
+                // This differs from node-fetch behavior where no span was created.
                 // We expect 2 spans: 1 server span + 1 client span (with error)
                 expect(spans).to.have.lengthOf(2);
 

packages/opentelemetry-sampler/test/app.js

@@ -80,7 +80,6 @@ app.post('/otel-post', (_req, res) => {
   delay(500)
     .then(() => fetch('https://www.example.com'))
     .then(async response => {
-      // Consume response body for proper span completion with native fetch
       await response.text();
     })
     .then(() => {