701144 - help do sendchanges more easily

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Armen [:armenzg]]

Before it was easy to grab a sendchange from the logs, copy it and paste it to run it again locally.

IMO we should fix the output to make it easy or write a command line tool to make it easy.

Comment 2

[John Hopkins (:jhopkins)]

More context from the duplicate bug: "I was asked to respin tests for a specific build today.  I looked at the various sendchange steps, which give all the info, but I would have loved to see the actual commandline spit out in a format I could copy/paste."

Comment 3

[Chris Cooper [:coop] (he/him)]

We could add custom log output for sendchange steps, just like we do for, e.g., tallying failure counts for unittests. Anyone want to take that on?

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

I didn't think this was too bad when I did it today, assuming you already have the log for the build job. eg, starting from 

'python' 'e:/builds/moz2_slave/m-beta-w32-dbg/tools/buildfarm/utils/retry.py' '-s' '5' '-t' '1800' '-r' '5' '--stdout-regexp' 'change sent successfully' 'buildbot' 'sendchange' '--master' 'buildbot-master10.build.mozilla.org:9301' '--username' 'sendchange-unittest' '--branch' 'mozilla-beta-win32-debug-unittest' '--revision' 'e31e3efd7e7d' '--comments' u'Bug 700591 - fix test_history_expiration.js DST timebomb.\nr=dietrich, a=LegNeato' '--property' 'buildid:20111116171950' '--property' 'pgo_build:False' '--property' u'builduid:58317e0d1750460cbd8b0b05162f6014' 'http://stage.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-beta-win32-debug/1321492790/firefox-9.0.en-US.win32.zip' 'http://stage.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-beta-win32-debug/1321492790/firefox-9.0.en-US.win32.tests.zip'

just copy from 'buildbot' through to the end of the line and paste it into terminal. 

Although now I notice that there are arguments like u'blahblah' which need the leading u squashed. IIRC builduid is used by systems like WarOnOrange to connect tests with builds.

Comment 5

[Armen [:armenzg]]

I wrote this script that does a sendchange pointing to the latest builds/tests from "latest-mozilla-central".

https://github.com/armenzg/playground/blob/master/mozilla/scripts/sendchanges.py

Patches welcome and I will be porting to braindump once I have something more flexible.

Comment 6

[Armen [:armenzg]]

The first version failed because there are no symbols on latest nightly.

I pushed a new version that deals with "tinderbox-builds". I have to cheat by hard-coding the unix timestamp for each platform.

There should be a way to take one changeset and returning the URLs of the builds for each platform for that specific changeset.

Comment 7

[Chris AtLee [:catlee]]

Does http://hg.mozilla.org/build/braindump/file/26c0cd9e1b14/buildbot-related/pulse2buildbot.py do what you want?

It will listen for production sendchanges via pulse and replay them to the master you specify.

Comment 8

[Mike Taylor [:bear]]

removing the [buildduty] whiteboard to get it out of the active buildduty work queue

Comment 9

[[e-mail] (:bhearsum)]

Mozharness jobs have copy/pastable sendchanges, which accounts for nearly all of our builds now.