553401 - set up buildbot for weave client tests

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[Mike Connor [:mconnor]]

this is either piggybacking on the server stuff, or it's a releng thing, but I'll let zandr make that call.

Initially need Linux/Mac/Windows, but probably need to think through how much coverage we need.  Will depend on how long the addons will live as addons before moving to core.  This is just functional unit test boxes, we don't need talos or graphserver, just running tests + a waterfall + email notification of failures.

Comment 1

[Zandr Milewski [:zandr]]

I'm going to say this is a RelEng thing, but I'm happy to play balun between client dev and RelEng to make this happen. 

It doesn't make sense to build out slaves for three platforms in our sandbox when all that structure exists in RelEng.

mconnor says `make test` works (though there's a bug against 1.9.2/trunk)

Assigning to RelEng, but lets talk about how to make it work.

Comment 2

[[e-mail] (:bhearsum)]

assigning to john for prioritization

Comment 3

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

mconnor:

1) do these tests run on our standard ref images? Or do we need toolchain modifications?

2) How long does this unittest suite take to run?

3) "mconnor says `make test` works (though there's a bug against 1.9.2/trunk)"
Whats the bug# for the 1.9.2/trunk work?

Possible q2 goal shared with labs?

Comment 4

[Mike Connor [:mconnor]]

(In reply to comment #3)
> mconnor:
> 
> 1) do these tests run on our standard ref images? Or do we need toolchain
> modifications?

Should run fine, though rebuilding crypto requires an SDK installed.  We don't want to rebuild crypto (binary bits are going away near to mid term).  Mostly just make + zip as reqs, so shouldn't be a big deal.

I run this from /Volumes/DATA/trees/test:

#!/bin/bash
export TOPSRCDIR=/Volumes/DATA/trees/test/src
export NATIVE_TOPSRCDIR=/Volumes/DATA/trees/test/src
export XULRUNNER_BIN=/Applications/Firefox3.5.app/Contents/MacOS/firefox-bin
hg clone https://hg.mozilla.org/labs/weave src
cd src
make test
cd ..
rm -rf src

> 2) How long does this unittest suite take to run?

The script above takes about two minutes on my Air (pull/build/run tests/wipe all traces), but in some ideal future we'll get that up to 10-15 minutes with expanded test coverage. ;)

> 3) "mconnor says `make test` works (though there's a bug against 1.9.2/trunk)"
> Whats the bug# for the 1.9.2/trunk work?

bug 531718

> Possible q2 goal shared with labs?

Definitely need in Q2, sooner rather than later, not sure whether it's shared with Services or just that we'll fix bugs in the testsuite ourselves.

Comment 6

[Aki Sasaki (not active)]

Has this become part of the standard set of firefox unit tests?

Comment 7

[Mike Connor [:mconnor]]

Yes.  This is no longer needed.  Marking as WONTFIX.