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

chore: do not skip test #528

Conversation

mdelapenya
Copy link
Collaborator

What does this PR do?

It removes the skip condition in the Test_LogConsumerGetsCalled test function.

Why is it important?

As described in #331, we skipped it because there was flakiness with Go 1.14 and Go 1.15

Since we are supporting only the latest two minor versions of Go in the CI (see #492 and #493), we expect the flakiness disappears.

Related issues

@mdelapenya mdelapenya requested a review from a team as a code owner September 16, 2022 08:18
@mdelapenya mdelapenya added the test flakiness Report a flaky test that happens on the CI label Sep 16, 2022
@mdelapenya mdelapenya self-assigned this Sep 16, 2022
@codecov
Copy link

codecov bot commented Sep 16, 2022

Codecov Report

Merging #528 (af5bd11) into main (1486bcc) will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #528      +/-   ##
==========================================
+ Coverage   68.71%   68.76%   +0.04%     
==========================================
  Files          22       22              
  Lines        2148     2148              
==========================================
+ Hits         1476     1477       +1     
  Misses        532      532              
+ Partials      140      139       -1     
Impacted Files Coverage Δ
docker.go 70.82% <0.00%> (+0.10%) ⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@mdelapenya
Copy link
Collaborator Author

In the case the flakiness appears again, we can investigate it more thoroughly

@mdelapenya mdelapenya merged commit 53dbf4d into testcontainers:main Sep 26, 2022
@mdelapenya mdelapenya deleted the do-not-skip-Test_LogConsumerGetsCalled branch October 3, 2022 05:38
mdelapenya referenced this pull request in mdelapenya/testcontainers-go Dec 21, 2022
* main:
  Add system requirements parent docs page for podman and colima (#562)
  Support for cap-add/cap-drop (#555)
  fix container NetworkMode usage (#560)
  chore: use hashed versions of test-summary action (#556)
  chore: use container.State() function in tests (#543)
  Log docker server info (#548)
  docs: add docs regarding Colima usage (#547)
  chore: add emoji to breaking changes in release drafter (#542)
  chore: add CONTRIBUTING file (#539)
  issue #537 Rename the wait/multi.go file to wait/all.go (#541)
  docs: add a basic layout for wait strategies in docs (#536)
  docs: improve consistency and fix typos (#534)
  chore: do not skip test (#528)
  chore: include test flakiness in the release drafter (#535)
  chore: retire old versions of Go (#530)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test flakiness Report a flaky test that happens on the CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"Test_LogConsumerGetsCalled" is failing with certain flakiness
2 participants