328110 - [client] should set up WAY_TOO_MUCH_GC testing for tinderbox

Status: REOPENED

(Testing :: General, enhancement, P5)

Description

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

We should set up testing of builds with WAY_TOO_MUCH_GC so that it can be run as a tinderbox test.  We should test:
 * the JS testsuite
 * the JS testsuite after loading the tests through XDR (freeze and thaw)
 * starting up the browser on a clean profile
 * starting up the browser with existing fastload files
 * loading AJAX-y Web pages.

The first two would require a tinderbox client script to build the JS shell rather than Firefox.

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

 * running common installer JavaScript operations

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Moving bugs that were filed in Webtools/Tinderbox before there was a separate component for bugs in tinderbox/buildbot client to a more appropriate component.

Comment 3

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

(In reply to comment #3)
> We should set up testing of builds with WAY_TOO_MUCH_GC so that it can be run
> as a tinderbox test.  We should test:
>  * the JS testsuite
>  * the JS testsuite after loading the tests through XDR (freeze and thaw)
>  * starting up the browser on a clean profile
>  * starting up the browser with existing fastload files
>  * loading AJAX-y Web pages.
> 
> The first two would require a tinderbox client script to build the JS shell
> rather than Firefox.


This bug seems to be asking for a few unrelated items. I'd like to clarify, and if that is the case, then split out as separate bugs. 

Is this bug asking to:
- start producing JS shell builds?
- run the existing JS testsuite on the new JSshell builds. What env setup is needed for this?
- run some modified/new JS testsuite. Is this suite written yet?

...and then, unrelated, on firefox builds:
- write and run a new AXAJ talos suite

Two items were unclear, so questions:
1) we already run TS tests starting browser on a clean new profile. Is that sufficient, or did you mean something else?

2) what do you mean with fastload files testsuite?

Comment 4

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

Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.

Comment 5

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

(In reply to comment #3)
> (In reply to comment #3)
> > We should set up testing of builds with WAY_TOO_MUCH_GC so that it can be run
> > as a tinderbox test.  We should test:
> >  * the JS testsuite
> >  * the JS testsuite after loading the tests through XDR (freeze and thaw)
> >  * starting up the browser on a clean profile
> >  * starting up the browser with existing fastload files
> >  * loading AJAX-y Web pages.
> > 
> > The first two would require a tinderbox client script to build the JS shell
> > rather than Firefox.
> 
> 
> This bug seems to be asking for a few unrelated items. I'd like to clarify, and
> if that is the case, then split out as separate bugs. 
> 
> Is this bug asking to:
> - start producing JS shell builds?
> - run the existing JS testsuite on the new JSshell builds. What env setup is
> needed for this?
> - run some modified/new JS testsuite. Is this suite written yet?
> 
> ...and then, unrelated, on firefox builds:
> - write and run a new AXAJ talos suite
> 
> Two items were unclear, so questions:
> 1) we already run TS tests starting browser on a clean new profile. Is that
> sufficient, or did you mean something else?
> 
> 2) what do you mean with fastload files testsuite?

dbaron: if this is still needed, please reopen with info.

Comment 6

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

(In reply to comment #0)
> We should set up testing of builds with WAY_TOO_MUCH_GC so that it can be run
> as a tinderbox test.  We should test:
>  * the JS testsuite

This is now the jsreftest suite, and no longer requires the JS shell.

>  * the JS testsuite after loading the tests through XDR (freeze and thaw)

But this might require the JS shell.

>  * starting up the browser on a clean profile
>  * starting up the browser with existing fastload files
>  * loading AJAX-y Web pages.


Reopening and moving to new test harnesses.