Skip to content

Conversation

@martosaur
Copy link
Contributor

One thing I forgot about 1.17, is that it doesn't have group for ExUnit. That's why https://github.com/PostHog/posthog-elixir/actions/runs/18150569276/job/51660693393?pr=56 this is flaky

Copy link
Member

@rafaeelaudibert rafaeelaudibert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could also enable async on v1.18+ here, wdyt? Approving to see if tests pass

@rafaeelaudibert rafaeelaudibert merged commit 9744ad2 into PostHog:v2.0.0-branch Oct 1, 2025
@martosaur
Copy link
Contributor Author

sorry I didn't get your question 😅 For as long as we have 1.17 tests on CI we'll have to keep those two modules sync, since they both compete for global PostHog name. Or do you suggest we add some conditional check and mark them async is we're running on 1.18 and sync otherwise?

@martosaur martosaur deleted the am-flaky-1.17-test branch October 1, 2025 04:15
@rafaeelaudibert
Copy link
Member

@martosaur I basically meant: async: Version.match?(System.version(), ">= 1.18.0")

@martosaur
Copy link
Contributor Author

ah yes great call. PR #62

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