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

logging re-triggered on subsequent tests #6

Closed
willscott opened this issue Mar 14, 2018 · 1 comment
Closed

logging re-triggered on subsequent tests #6

willscott opened this issue Mar 14, 2018 · 1 comment

Comments

@willscott
Copy link
Contributor

After adding the Dash test in the performance group, I notice that logging seems to get re-added with each subsequent test.

When running ooni run performance, one sees expected output during Dash run, but then when NDT runs all log lines are duplicated, e.g.

   • Submitting test results; please be patient...
   • Submitting test results; please be patient...
   • Results successfully submitted
   • Results successfully submitted
   • OnProgress: 0.950000 - ending the test
   • OnProgress: 0.950000 - ending the test
   • Closing report; please be patient...
   • Closing report; please be patient...
   • Report successfully closed
   • Report successfully closed
   • OnProgress: 1.000000 - test complete
   • OnProgress: 1.000000 - test complete
@hellais
Copy link
Member

hellais commented Mar 19, 2018

Good call. The root cause of this was that the handler map was a global instead of being per nettest. To overcome this I refactored it to be instead part of the Nettest and created a NewNettest constructor. See: measurement-kit/go-measurement-kit@e6bf66a.

If you pull from the current master and run:

dep ensure -update github.com/measurement-kit/go-measurement-kit

You should find it fixed.

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