|SUCCESS| test/pcapng: add some leeway to timestamp test

[dpdklab at iol.unh.edu]

Test-Label: ai-code-review
Test-Status: SUCCESS
https://dpdk.org/patch/166465

_AI Code Review_

=== Patch Review: series.patch (via Claude) ===
Review date: 2026-07-02

# DPDK Patch Review

## Patch: test/pcapng: add some leeway to timestamp test

### Summary
This patch modifies the timestamp validation test to allow up to 1 second of leeway after capture stops to account for timing variations on busy or emulated systems.

---

## CORRECTNESS REVIEW

**No correctness bugs identified.**

The change increases the validation window by adding `NS_PER_S` (1 second in nanoseconds) to the current timestamp. This is a test-only change that makes the test more tolerant of timing variations.

---

## STYLE AND PROCESS REVIEW

### Info

**Consider documenting the rationale in code**

The commit message explains why the 1-second leeway is needed (busy/emulated CPUs), but this context is not captured in the code itself. Consider adding a comment explaining why the window is extended:

```c
/* Allow up to 1 second leeway for timestamp validation on
 * busy or emulated systems where packet capture timing may vary.
 */
ctx.end_ns = current_timestamp() + NS_PER_S;
```

This would help future maintainers understand why the test allows timestamps beyond the actual stop time.

---

## RELEASE NOTES

**No release notes required.** This is a test-only change (robustness improvement for existing test) and does not affect public API or require user-visible documentation.

---

## OVERALL ASSESSMENT

The patch is **acceptable**. It addresses a legitimate test flakiness issue with a reasonable solution (1-second tolerance window). The only suggestion is adding an inline comment for maintainability.