566040 - [Tracking bug] Create new project branch "JaegerMonkey"

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[David Mandelin [:dmandelin]]

This is basically a project branch request, except that we are already using http://hg.mozilla.org/users/danderson_mozilla.com/jaegermonkey/ as the hg repo, so we don't need that part set up.

The questionnaire:

    *  Name of hg repo for this branch (relative to hg.mozilla.com)

A: users/danderson_mozilla.com/jaegermonkey/
   (this has already been created, so no action required here)

    * Do you want builds?
A: yes
          o All o.s. or subset of linux32, linux64, osx10.5, osx10.6, win32
A: we would like: linux32, linux64, 
                  osx10.6 (32-bit build), osx10.6 (64-bit build)
                  win32, win64 when available
          o Incremental-build-on-checkin? y/N
A: yes
          o Are en-US builds enough, with no l10n? Y/n
A: no
          o Nightly builds? Y/n
                + Nightly updates? y/N 
A: no nightlies for now

    * Do you want unittests?
          o All o.s. or subset of: WinXP, Win7, 10.5, 10.6, fedora12, fedora12-64, maemo4, maemo5gtk, maemo5qt (with android and Win7x64 coming soon). 
A: we would like unit tests for the same set that we want builds for (listed above). It's important to get unit testing on 32- and 64- bit builds where available--this is a JIT, so the instruction set matters.

    * Do you need mobile builds?
          o All o.s. or subset of linux-i686, macosx-i686, maemo4, maemo5gtk, maemo5qt
          o Incremental-build-on-checkin? y/N 
A: no mobile builds for now

    * Do you want talos?
          o Do you need talos on Tiger?
          o All o.s. or subset of Talos platforms? 
A: no, don't need talos for this

    * Name of the contact person for this branch who will:
          o Be doing periodic refreshes from parent
          o Be contact person for misc setup questions
          o Decide when to land back project branch onto parent
          o Decide when to terminate the project branch 
A: Dave Mandelin, [e-mail]

    * Timeline:
          o Approx expected life span of project branch - if known? 
A: at least through end of 2010

    * Additional requests:
          o Need any changes to toolchain used in parent branch?
A: no
          o Need any changes to the compile/link/repack steps used in parent branch?
A: no
          o Do you expect to create any releases from this project branch?
                + NOTE: Currently we do not have nightly/alpha/beta/release updates on these project branches. 
A: not for now, but we might in a few months
          o Any other info that might be helpful to us?

Comment 1

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

Missed this; tweaking summary to make it show up with the other new project branch requests.

Comment 2

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

(In reply to comment #2)
> This is basically a project branch request, except that we are already using
> http://hg.mozilla.org/users/danderson_mozilla.com/jaegermonkey/ as the hg repo,
> so we don't need that part set up.
> The questionnaire:
>     *  Name of hg repo for this branch (relative to hg.mozilla.com)
> A: users/danderson_mozilla.com/jaegermonkey/
>    (this has already been created, so no action required here)
Even though the user repo exists, any objections to us setting up hg.mozilla.org/projects/jaegermonkey and moving your work to that?

Hosting this way will keep this project branch in sync with how we do all the other project branches. Its also quick to setup, so not a problem to do.


>           o Are en-US builds enough, with no l10n? Y/n
> A: no
You are asking for l10n builds. Double checking is that correct?

Comment 3

[David Anderson [:dvander] - inactive, e-mail if emergency]

(In reply to comment #2)

> Even though the user repo exists, any objections to us setting up

No objections, but instead please clone from here:

 http://hg.mozilla.org/users/danderson_mozilla.com/moo

This is the new JM repo. The old one will be deleted soon.

> You are asking for l10n builds. Double checking is that correct?

We don't need L10n builds.

Thanks!

Comment 4

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

(In reply to comment #3)
> (In reply to comment #2)
> 
> > Even though the user repo exists, any objections to us setting up
> No objections, but instead please clone from here:
>  http://hg.mozilla.org/users/danderson_mozilla.com/moo
> This is the new JM repo. The old one will be deleted soon.
ok. We'll be sure to coord with you after we clone, to make sure nothing gets lost after the clone. Watch this space.


> > You are asking for l10n builds. Double checking is that correct?
> We don't need L10n builds.
> Thanks!
Phew - thanks!

Comment 5

[David Mandelin [:dmandelin]]

What's the status on buildbots? We have browsers that build and more-or-less work, so we'd love to get automated testing soon.

Comment 6

[Lukas Blakk [:lsblakk] use ?needinfo]

Am about to put up "disposable" automation branches in bug 551528 - would cloning the jaegermonkey repo to one of those serve your purposes?  What is the life expectancy of this project branch?

Comment 7

[Robert Sayre]

that's workable in the short term, but this branch will be around until at least 2011. dmandelin filed this bug over a month ago, and we need to get automated builds very soon.

Comment 8

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: adds jaegermonkey branch to staging/production configs

Comment 9

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: adds jaegermonkey branch to graphs/sql/data.sql

Comment 10

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: insert statements for graphserver addition of jaegermonkey branch

Comment 11

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: add jaegermonkey mozconfigs

Comment 12

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

(In reply to comment #7)
> that's workable in the short term, but this branch will be around until at
> least 2011. dmandelin filed this bug over a month ago, and we need to get
> automated builds very soon.

This should be live Monday.

Comment 13

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

Thanks, John and Lukas!

Comment 14

[alice nodelman [:alice] [:anode]]

Applied to graphs-stage
mysql> insert into branches values (NULL,"Jaegermonkey");
Query OK, 1 row affected (0.01 sec)

mysql> insert into machines values (NULL,6,0,NULL,"Linux_jaegermonkey",1,unix_timestamp());
Query OK, 1 row affected (0.03 sec)

mysql> insert into machines values (NULL,6,0,NULL,"Linux_jaegermonkey_leak_test",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)

mysql> insert into machines values (NULL,7,0,NULL,"OS_X_10.5.2_jaegermonkey",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)

mysql> insert into machines values (NULL,7,0,NULL,"OS_X_10.5.2_jaegermonkey_leak_test",1,unix_timestamp());
Query OK, 1 row affected (0.01 sec)

mysql> insert into machines values (NULL,8,0,NULL,"WINNT_5.2_jaegermonkey",1,unix_timestamp());
Query OK, 1 row affected (0.02 sec)

mysql> insert into machines values (NULL,8,0,NULL,"WINNT_5.2_jaegermonkey_leak_test",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)

mysql> insert into machines values (NULL,19,0,NULL,"WINNT_6.1_jaegermonkey",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)

mysql> insert into machines values (NULL,19,0,NULL,"WINNT_6.1_jaegermonkey_leak_test",1,unix_timestamp());
Query OK, 1 row affected (0.01 sec)

mysql> insert into machines values (NULL,17,0,NULL,"OS_X_10.6.2_jaegermonkey",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)

mysql> insert into machines values (NULL,17,0,NULL,"OS_X_10.6.2_jaegermonkey_leak_test",1,unix_timestamp());
 (NULL,18,0,NULL,"Linux_x86-64_jaegermonkey",1,unix_timestamp());
insert into machines values (NULL,18,0,NULL,"Linux_x86-64_jaegermonkey_leak_test",1,unix_timestamp());
Query OK, 1 row affected (0.04 sec)

mysql> insert into machines values (NULL,18,0,NULL,"Linux_x86-64_jaegermonkey",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)

mysql> insert into machines values (NULL,18,0,NULL,"Linux_x86-64_jaegermonkey_leak_test",1,unix_timestamp());
Query OK, 1 row affected (0.01 sec)

Comment 15

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 452027 [details] [diff] [review]
add jaegermonkey mozconfigs 

http://hg.mozilla.org/build/buildbot-configs/rev/d28f111ca806

Comment 16

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 452025 [details] [diff] [review]
adds jaegermonkey branch to graphs/sql/data.sql 

http://hg.mozilla.org/graphs/rev/b8ae2a37b8d1

Comment 17

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: add jaegermonkey branch to talos-r3/talos-staging-pool

turning off all talos tests since they do not need talos at this time, we'll just have the default unittests that are being run on talos masters now.

Comment 18

[Aki Sasaki (not active)]

Comment on attachment 452024 [details] [diff] [review]
adds jaegermonkey branch to staging/production configs 

>+BRANCHES['jaegermonkey']['enable_nightly'] = False
>+BRANCHES['jaegermonkey']['create_snippet'] = False
>+# Disable XULRunner / SDK builds
>+BRANCHES['jaegermonkey']['enable_xulrunner'] = False
>+# Disable Nightly builds
>+BRANCHES['jaegermonkey']['enable_nightly'] = False

You seem to have enable_nightly here twice, which might trip someone up.
r=me if you remove one (probably the second, so the order remains the same as addonsmgr?)

Comment 19

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 452024 [details] [diff] [review]
adds jaegermonkey branch to staging/production configs 

http://hg.mozilla.org/build/buildbot-configs/rev/948c28e4eaff

Comment 20

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 452762 [details] [diff] [review]
add jaegermonkey branch to talos-r3/talos-staging-pool

http://hg.mozilla.org/build/buildbot-configs/rev/e9fefda70ba8

Comment 21

[Lukas Blakk [:lsblakk] use ?needinfo]

Turned this on in production - reconfig'd pm01/03 as well as both talos masters.  Will check in the morning to make sure all is well.

Comment 22

[Robert Sayre]

I don't see anything on the tinderbox page yet... what needs to happen?

Comment 23

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

That depends. Do you want a set of builds before pushing any changes, or are you content to push something new ?

Comment 24

[Lukas Blakk [:lsblakk] use ?needinfo]

(In reply to comment #22)
> I don't see anything on the tinderbox page yet... what needs to happen?

You can start pushing changes now to trigger some builds.  The first round of builds will burn because of no pre-existing logs for them to compare against. Please go ahead and do this and ping me if you have any issues after the first round.