Inconsistent Results with partially wrong API

[mpldr]

Describe the bug

We have a partially working API. Currently 13/71 endpoints are working as intended (we have verified this manually). However, goss does not always report this correctly. Sometimes it just randomly has some Client.Timeout exceeded while awaiting headers while the server is chilling at 2% load. Most times it reports 13/71 as it should be but sometimes it's also any other number. The highest we've seen so far was 53. The server seems not to receive the requests (at least it does not log them)

How To Reproduce

• Create a mid-size API with SQLite backend
• write a goss test for every endpoint
• run them with as much parallelism as possible

Expected Behavior

• The reported number should match the number of tests that are correct to fail
• and should not change

Actual Behavior

• The number fluctuates

Environment:

• Version of goss: v0.3.16
• OS/Distribution version (if applicable): Archlinux, reproducible with WSL2 and Ubuntu

Since this is a company project I am unfortunately not allowed to share binary or sourcecode. I can however provide the goss file if that helps.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mpldr]

Bump

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.