Jim Mathies [:jimm] Reporter
	Description • 15 years ago

I'm currently trying to track down leaks caused by a patch for the 1.9.1 branch (bug 470487) that only show up on try server. Curious if it's possible to get access to a test image similar to try's "WINNT 5.2 try hg unit test" for testing purposes to try and track this down.

	Phong Tran [:phong]
	Comment 1 • 15 years ago

I'm moving this over to releng.

	John Ford [:jhford] CET/CEST Berlin Time
	Comment 2 • 15 years ago

is this reproducible on all slaves or a subset?

	Jim Mathies [:jimm] Reporter
	Comment 3 • 15 years ago

(In reply to comment #2)
> is this reproducible on all slaves or a subset?

WINNT 5.2 try hg unit test AFAICT. It's windows only.

	John Ford [:jhford] CET/CEST Berlin Time
	Comment 4 • 15 years ago

WINNT 5.2 try hg unit test is actually a type of job that can be completed by any one of a number of machines in our pool.  You should see something like "COMPUTERNAME=TRY-W32-SLAVE18" in the environment printout preceding the different build steps.  Have you done this more than once on try?

	Jim Mathies [:jimm] Reporter
	Comment 5 • 15 years ago

(In reply to comment #4)
> WINNT 5.2 try hg unit test is actually a type of job that can be completed by
> any one of a number of machines in our pool.  You should see something like
> "COMPUTERNAME=TRY-W32-SLAVE18" in the environment printout preceding the
> different build steps. 

COMPUTERNAME=TRY-W32-SLAVE04

> Have you done this more than once on try?

Yes, multiple times, the leaks always show up.

	Jim Mathies [:jimm] Reporter
	Comment 6 • 15 years ago

(In reply to comment #5)
> (In reply to comment #4)
> > WINNT 5.2 try hg unit test is actually a type of job that can be completed by
> > any one of a number of machines in our pool.  You should see something like
> > "COMPUTERNAME=TRY-W32-SLAVE18" in the environment printout preceding the
> > different build steps. 
> 
> COMPUTERNAME=TRY-W32-SLAVE04
> 
> > Have you done this more than once on try?
> 
> Yes, multiple times, the leaks always show up.

Ran it today to be sure - 

COMPUTERNAME=TRY-W32-SLAVE06

same leaks.

	Nick Thomas [:nthomas] (UTC+12) Assignee
	Comment 7 • 15 years ago

We'll lend you try-w32-slave06 for a short while. Please file a bug against mozilla.org::Server Operations if you don't already have access to the MPT VPN.

	Nick Thomas [:nthomas] (UTC+12) Assignee
	Comment 8 • 15 years ago

Renamed buildbot.tac, created a snapshot, scrubbed, and emailed auth to jimm. Rebooting the box may reset the auth and lock you out, but you shouldn't need to do that anyway.

Leaving this open to restore when Jim is done (please let us know!).  Note to self - restoring is revert snapshot, rename buildbot.tac.bak.

	Nick Thomas [:nthomas] (UTC+12) Assignee
	Comment 9 • 15 years ago

(In reply to comment #8)
> Leaving this open to restore when Jim is done (please let us know!).  Note to
> self - restoring is revert snapshot, rename buildbot.tac.bak.

And re-enable notifications on the buildbot check in nagios.

	Jim Mathies [:jimm] Reporter
	Comment 10 • 15 years ago

Ok, all finished! You can take it back.

	Nick Thomas [:nthomas] (UTC+12) Assignee
	Comment 11 • 15 years ago

Thanks Jim. Snapshot reverted & deleted, and connected back to the try master.

What did we learn from this ? Was full access required to solve the problem ? Would an objdir or objdir/dist have been sufficient ?

	Jim Mathies [:jimm] Reporter
	Comment 12 • 15 years ago

(In reply to comment #11)
> Thanks Jim. Snapshot reverted & deleted, and connected back to the try master.
> 
> What did we learn from this ? Was full access required to solve the problem ?
> Would an objdir or objdir/dist have been sufficient ?

I used it to track down a bunch of tests that caused a leak. The assumption was it was something specific to our build machines. It ended up related to something quirky in the JVM we have installed. I suppose if I had a few other folks try and reproduce, we probably would have found it on some other machine. Having access to the try slave though made the process simple since I was the guy working on the original patch.