-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Fire test_start and test_stop events on worker nodes #1777
Fire test_start and test_stop events on worker nodes #1777
Conversation
Looks great! However, this is a breaking change (for people relying on test_start not being triggered on master), so I will not merge it just now (in case we need to make another 1.x release). My guess is that we'll release 2.0 in a month or so, so I'll merge this in a couple of weeks at the latest. |
Are planned version 2.0 changes documented anywhere? I have some more changes I'd like to implement and wanted to make sure I didn't double up on work |
Not really. Just the open PR about user spawning |
@nathan-beam Can I bother you to resolve the conflicts? |
@nathan-beam I'd love to have this as part of 2.0 (as it is a breaking change), but I can't be arsed to resolve the conflicts :) |
@cyberw should be g2g now |
nvm |
Ok now it's good to go |
Thx |
PR to fix #1776
Added
test_start
andtest_stop
events to the baseRunner
class'start()
andstop()
method, respectivelyAdded/updated relevant tests and documentation.