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

test_stop_trigger: fix remote_interruptCommand no attribute error #1678

Merged
merged 2 commits into from
May 22, 2015

Conversation

yetanotherion
Copy link
Contributor

The current execution of buildbot.test.integration.test_stop_trigger.TriggeringMaster.testTriggerRunsForever
fail randomly, due to different scenarios being executed. They differentiate on whether:

  • the remotecommand is not created: it succeeds,
  • the remotecommand is created: it fails with a exceptions.AttributeError: BotBase instance has no attribute 'remote_interruptCommand'

This PR aims at fixing the error.

@yetanotherion yetanotherion force-pushed the master branch 3 times, most recently from fc36e16 to 7c9a059 Compare May 22, 2015 07:15
@yetanotherion yetanotherion changed the title [WIP] test_stop_trigger: reproduce remote_interruptCommand no attribute error test_stop_trigger: fix remote_interruptCommand no attribute error May 22, 2015
@yetanotherion
Copy link
Contributor Author

the unit tests pass in my environment
@djmitche @tardyp what do you think about the fix ?

Ion Alberdi added 2 commits May 22, 2015 10:07
This commit adds a test to reproduce the remote_interruptCommand
no attribute error.
The rpc method can be directed to two type of objects:
- slave.buildslave.base.BotBase, or
- SlaveBuilder, that is contained on the previous object
  inside a dictionary {buildername: SlaveBuilder}.

Currently, the remote interruptCommand rpc is directed
to the slave.buildslave.base.Botbase. However this
object does not have any interruptCommand method,
only the SlaveBuilder has it.

Moreover, the current prototype of the method remoteInterruptCommand
- (commandId, why)
does not permit to find the associated SlaveBuidler to which
the rpc should be directed to.

This commit implements:
- a change of the prototype to the remoteInterruptCommand method
  to add the builderName, i.e (builderName, commandId, why)
- a redirection of the interruptCommand rpc, to the SlaveBuilder.
@tardyp
Copy link
Member

tardyp commented May 22, 2015

cool fix! 👍

sa2ajj pushed a commit that referenced this pull request May 22, 2015
test_stop_trigger: fix remote_interruptCommand no attribute error
@sa2ajj sa2ajj merged commit 992e766 into buildbot:master May 22, 2015
@sa2ajj
Copy link
Contributor

sa2ajj commented May 22, 2015

Yay!

@djmitche
Copy link
Member

@yetanotherion, the change to remoteInterruptCommand needs to be documented in master/docs/developer/cls-protocols.rst

@yetanotherion
Copy link
Contributor Author

@djmitche
Copy link
Member

great, thanks!

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.

None yet

4 participants