Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests for connect over TLS were bypassed due to the unix socket path being populated #107

Closed
wants to merge 39 commits into from

Conversation

carboneater
Copy link
Contributor

So I wanted to try to reproduce the CI errors regarding ClamAV sometimes returning an empty array.
I never managed to reproduce it locally.

However, I realized the TLS tests would pass, even when stunnel was stopped...
Overriding the default test values to force the right code branch uncovered two minor bugs...
And started a whole new round of fighting with GitHub Actions...

The two 30s timers in the pipeline were replaced with pauses until services are detected to be ready.
Sadly, even this did not fix the flakiness from the good files array test...

Gabriel added 30 commits December 8, 2022 16:13
Remove secondary timer, openssl/stunnel config should give us the time padding clamd needs to boot
All other messages seem either non-unique or too unique (only fired on a specific internal event)
Logs said clamav was already active...
Makefile Show resolved Hide resolved
@kylefarris
Copy link
Owner

I've added the pertinent changes from this PR to Master. Thanks for the contribution @carboneater . I'll get the dependencies updated before the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants