Closed
Bug 833884
Opened 12 years ago
Closed 12 years ago
loan win64 build machine to Jiimm for possible Visual Studio 2012 Update 1 work
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ehsan.akhgari, Assigned: kmoir)
References
(Blocks 1 open bug)
Details
We need to start experimenting with whether compiling with Visual Studio 2012 Update 1 will result in a significant reduction in the linker vmem usage. As a first step, we need to have the compiler installed on a build machine.
John, can you please find an owner for this on the RelEng team? I'd really like us to get this done by the end of this week so that we can have some numbers to discuss in the next week's Engineering call.
Thanks!
| Assignee | ||
Updated•12 years ago
|
Assignee: joduinn → kmoir
Comment 1•12 years ago
|
||
kmoir, if you could set up a machine for loaning that would be great.
ehsan will find an owner and we can then grant BuildVPN access and credentials to the volunteer.
I had previously installed VS2012 by doing this:
* Download http://dev-stage01.build.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/en_visual_studio_professional_2012_x86_dvd_920779.iso (only inside of BuildVPN)
* Mount it and extract contents to C:\Tools\VS2012_PRO_MSDN_ENU
* C:\Tools\VS2012_PRO_MSDN_ENU\vs_professional.exe /quiet /restart
If a different ISO is needed we can get it and put it accessible for the machine.
We just need to loan a machine to someone from dev.
Comment 2•12 years ago
|
||
Has anyone done this experiment on their local machine?
| Reporter | ||
Comment 3•12 years ago
|
||
(In reply to comment #2)
> Has anyone done this experiment on their local machine?
Not that I know of, but it's best to do it on the build machine to know for sure what's going to happen there
Comment 4•12 years ago
|
||
(cc-ing jimm, who has been involved in earlier VS evals for Win8 work, and might have insights).
(In reply to Armen Zambrano G. [:armenzg] from comment #1)
> kmoir, if you could set up a machine for loaning that would be great.
>
> ehsan will find an owner and we can then grant BuildVPN access and
> credentials to the volunteer.
from irc, Ehsan will be doing this eval, and kmoir expects he'll have the loaner machine today. Tweaking summary to match reality.
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: armenzg
Summary: Please install Visual Studio 2012 Update 1 on a builder → loan win64 build machine to Ehsan to install & eval Visual Studio 2012 Update 1
Comment 5•12 years ago
|
||
Let's figure out this "vs 2012 update 1" thing first, and see if we can build binaries that run on xp. I think we can hold off on a dev machine until that experimentation is complete.
| Reporter | ||
Comment 6•12 years ago
|
||
I actually won't be the person doing this investigation, as I said here and on IRC.
Summary: loan win64 build machine to Ehsan to install & eval Visual Studio 2012 Update 1 → Please install Visual Studio 2012 Update 1 on a builder
Comment 7•12 years ago
|
||
(In reply to John O'Duinn [:joduinn] from comment #4)
> (cc-ing jimm, who has been involved in earlier VS evals for Win8 work, and
> might have insights).
>
> (In reply to Armen Zambrano G. [:armenzg] from comment #1)
> > kmoir, if you could set up a machine for loaning that would be great.
> >
> > ehsan will find an owner and we can then grant BuildVPN access and
> > credentials to the volunteer.
>
> from irc, Ehsan will be doing this eval, and kmoir expects he'll have the
> loaner machine today. Tweaking summary to match reality.
(In reply to :Ehsan Akhgari from comment #6)
> I actually won't be the person doing this investigation, as I said here and
> on IRC.
per irc w/ehsan, jimm in #developers:
1) jimm is doing eval of compiler in bug#833887 (XP support is just one of the concerns). Jimm does not need loaner machine for that.
2) assuming eval is good, then jimm (not ehsan) will then be doing experiment on loaner machine.
** kmoir: please reopen/redo bug#833911 to grant jimm access instead of ehsan for this work.
Summary: Please install Visual Studio 2012 Update 1 on a builder → loan win64 build machine to Jiimm for possible Visual Studio 2012 Update 1 work
| Assignee | ||
Comment 8•12 years ago
|
||
jimm: I have w64-ix-slave17 ready for you once you have done your initial eval
Comment 9•12 years ago
|
||
(In reply to Kim Moir [:kmoir] from comment #8)
> jimm: I have w64-ix-slave17 ready for you once you have done your initial
> eval
If you could please email me the access info I can get a pgo build going on this. I'd prefer to use RDP for access.
Is w64-ix-slave17 one of our current 64-bit win builders with the 8.0 sdk installed?
Comment 10•12 years ago
|
||
(jmathies@moco)
| Assignee | ||
Comment 11•12 years ago
|
||
I've sent Jim the information to connect to the slave.
Comment 12•12 years ago
|
||
> * Download
> http://dev-stage01.build.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/
> en_visual_studio_professional_2012_x86_dvd_920779.iso (only inside of
> BuildVPN)
Now @ http://dev-stage01.build.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/visual_studio/
Comment 13•12 years ago
|
||
On this slave, I'm currently getting a config error about python being too old -
$ build/pymake/make.py -f client.mk configure
make.py[0]: Entering directory 'e:\mc'
TEST-PASS | check-sync-dirs.py | e:\mc\js\src\build <= e:\mc\build
Generating e:/mc/configure using autoconf
e:\mc\client.mk:276:0$ cd e:/mc; /usr/local/bin/autoconf-2.13
TEST-PASS | check-sync-dirs.py | e:\mc\js\src\build <= e:\mc\build
Generating e:/mc/js/src/configure using autoconf
e:\mc\client.mk:276:0$ cd e:/mc/js/src; /usr/local/bin/autoconf-2.13
e:\mc\config\makefiles\autotargets.mk:59:0$ pymake.builtins mkdir -p "e:/mc/../vs11pgo-obj/"
e:\mc\client.mk:314:0$ cp e:/mc/.mozconfig e:/mc/../vs11pgo-obj/.mozconfig
cd e:/mc/../vs11pgo-obj
e:/mc/configure
Adding configure options from e:/mc/.mozconfig:
--enable-application=browser
--enable-debugger-info-modules=yes
--enable-application=browser
--enable-optimize
--disable-debug
--disable-tests
--enable-debug-symbols
creating cache ./config.cache
checking host system type... i686-pc-mingw32
checking target system type... i686-pc-mingw32
checking build system type... i686-pc-mingw32
checking for mawk... no
checking for gawk... gawk
checking for python2.7... no
checking for python... /c/mozilla-build/python/python
Creating Python environment
Python 2.7 or greater (but not Python 3) is required to build. You are running Python 2.6.
according to python -v it has python 2.6.5. Do we need to upgrade the slave? I tried updating mozilla-build but ran into file access errors.
Comment 14•12 years ago
|
||
hat tip armenz, he pointed me to the right location for python27. I need to update my shell path variables.
Comment 15•12 years ago
|
||
ok, pgo build kicked off. will report back once it's complete.
Comment 16•12 years ago
|
||
pgo build completed, reported results in bug 833881. I'm not sure what's next, we probably better wait a day to see if people want to do more testing, after which we can reset w64-ix-slave17.
| Reporter | ||
Comment 17•12 years ago
|
||
Nah, I think we're done here. Thanks!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 19•12 years ago
|
||
Make that bug 834906.
Comment 20•12 years ago
|
||
(mass move of loan bugs to new releng component, filter on CallekAug2013LoanerMove )
Component: Release Engineering: Machine Management → Release Engineering: Loan Requests
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: Loan Requests → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•