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

Means to force export #74

Closed
garthk opened this issue Apr 16, 2020 · 2 comments
Closed

Means to force export #74

garthk opened this issue Apr 16, 2020 · 2 comments

Comments

@garthk
Copy link
Contributor

garthk commented Apr 16, 2020

:timer.sleep/1 in tests makes babies cry; any chance of an exported method to trigger export so we can verify the exporter worked?

@tsloughter
Copy link
Member

With elixir if you can turn the export into a message (I'm assuming this is for honeycomb so you can't just use the _pid exporter?) and do assert_receive which takes a timeout.

In opentelemetry tests we are using a macro to do the same as assert_receive and in the case of testing zipkin and otel protocol I just manually call their export functions.

Definitely could use better testing on the zipkin/otpl side as it just verifies its an "ok" :):

?assertMatch(ok, opentelemetry_zipkin:export(Tid, Resource, State)),

@garthk
Copy link
Contributor Author

garthk commented Apr 24, 2020

Yeah, a receive was how I ended up doing it. It's replacing one timeout Sean didn't like with another he shouldn't, but not to worry :)

@garthk garthk closed this as completed Apr 24, 2020
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

No branches or pull requests

2 participants