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

Eliminate "Sending invitation" output spam in test_signup #7563

Closed
gnprice opened this issue Nov 29, 2017 · 3 comments
Closed

Eliminate "Sending invitation" output spam in test_signup #7563

gnprice opened this issue Nov 29, 2017 · 3 comments

Comments

@gnprice
Copy link
Member

gnprice commented Nov 29, 2017

We're getting close to eliminating output spam in our tests! One of the remaining cases is in tools/test-backend zerver.tests.test_signup, a bunch of lines like this:

2017-11-29 01:22:45.669 INFO [] Sending invitation for realm zulip to alice@zulip.com

We should work out where those are coming from and clean them up.

@zulipbot
Copy link
Member

Hello @zulip/server-testing members, this issue was labeled with the area: testing-coverage label, so you may want to check it out!

@gnprice
Copy link
Member Author

gnprice commented Nov 29, 2017

(See #1587 for locking this kind of problem down entirely in the future.)

@hackerkid
Copy link
Member

@zulipbot claim

hackerkid added a commit to hackerkid/zulip that referenced this issue Nov 30, 2017
hackerkid added a commit to hackerkid/zulip that referenced this issue Dec 5, 2017
hackerkid added a commit to hackerkid/zulip that referenced this issue Dec 20, 2017
showell pushed a commit to showell/zulip that referenced this issue Dec 21, 2017
showell pushed a commit to showell/zulip that referenced this issue Dec 21, 2017
utkarsh23 pushed a commit to utkarsh23/zulip that referenced this issue Dec 22, 2017
showell pushed a commit to showell/zulip that referenced this issue Dec 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants