Bug 58662 - sheriffbot rollout has failed the last two times I tried
Summary: sheriffbot rollout has failed the last two times I tried
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-15 07:08 PDT by Adam Roben (:aroben)
Modified: 2011-04-15 18:21 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Roben (:aroben) 2011-04-15 07:08:30 PDT
The last two times I've tried to use sheriffbot to roll out a patch, it has failed. Here are the IRC logs:

Apr 14 10:37:16 <aroben>	sheriffbot: rollout 83849 http/tests/inspector-enabled/database-open.html failing on multiple bots
Apr 14 10:37:29 <sheriffbot>	Preparing rollout for r83849...
Apr 14 10:37:30 <sheriffbot>	aroben: Failed to create rollout patch:
Apr 14 10:37:30 <sheriffbot>	Failed to run "['./Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '--bot-id=ec2-sherrif-bot', '..." exit_code: 1


Apr 15 09:03:35 <aroben>	sheriffbot: rollout 83954 fast/dom/Window/timer-null-script-execution-context.html crashing on multiple bots
Apr 15 09:03:44 <sheriffbot>	Preparing rollout for r83954...
Apr 15 09:03:44 <sheriffbot>	aroben: Failed to create rollout patch:
Apr 15 09:03:44 <sheriffbot>	Failed to run "['./Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '--bot-id=ec2-sherrif-bot', '..." exit_code: 1
Comment 1 Eric Seidel (no email) 2011-04-15 07:09:38 PDT
Thanks.  We should be able to pull up the logs from those attempts pretty easily.  We could/should even make sherrifbot just post his logs to queues.webkit.org.
Comment 2 Eric Seidel (no email) 2011-04-15 18:11:56 PDT
Adam is investigating.  Seems the sheriff got himself stuck.
Comment 3 Adam Barth 2011-04-15 18:21:33 PDT
I've restarted him.  We'll see if the problem recurs.  In the future, you can try sending him the command:

sheriffbot: restart

To see if that fixes the problem.