test: Improve 'republish in consume block' test reliability

baelter · baelter · commit 100804ebd05a · 2025-11-27T23:24:22.000+01:00
- Add ack() for the final message (deliveryTag 10000) before canceling
  consumer to ensure proper cleanup
- Increase test timeout from default 5s to 60s to accommodate processing
  10,000 messages with concurrent publishes

This test was timing out due to:
1. Missing ack on final message before cancel
2. Insufficient timeout for high-volume message processing

The test validates that the buffer pool can handle concurrent publishes
within a consume callback without race conditions.
diff --git a/test/test.ts b/test/test.ts
@@ -823,13 +823,14 @@ test("can republish in consume block without race condition", async () => {
     if (msg.deliveryTag < 10000) {
       await Promise.all([q.publish(msg.body), q.publish(msg.body), msg.ack()])
     } else if (msg.deliveryTag === 10000) {
+      await msg.ack()
       await consumer.cancel()
     }
   })
   await expect(consumer.wait()).resolves.toBeUndefined()
   await expect(conn.close()).resolves.toBeUndefined()
   console.log(conn.bufferPool.length)
-})
+}, 60_000)
 
 test("raises when channelMax is reached", async () => {
   const amqp = getNewClient()
