Install xperf tools on win7 talos slaves

RESOLVED FIXED

Status

Release Engineering
General
P3
normal
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: sdwilsh, Assigned: armenzg)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [deployment][talos] waiting on talos-r3-w7-ref reboot)

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
We need to install the xperf tools (part of the windows SDK) on all windows 7 slaves for bug 609111.

(sorry if I put this bug in the wrong component; not sure which one is correct)
Summary: Install xperf tools on talos slaves → Install xperf tools on win7 talos slaves
(Assignee)

Comment 1

7 years ago
This is the right component.
We won't be able to take this before end of Q1 though.
Priority: -- → P4
Whiteboard: [deployment][talos]
What can I do to help get this done?  Is there anything releng needs?
(Assignee)

Comment 3

7 years ago
Are these the instructions to get this installed?
https://developer.mozilla.org/En/Profiling_with_Xperf
Is this for win7 only, correct?

Getting this done relies on having someone (probably me) to have time to deploy it manually through VNC/RDP one by one in all ~50 win7 slaves (probably 2-3 hours). Before that we would have to deploy it on staging and making sure that it runs as expected and yields the information you need.

jmaher is this a Q1 goal running late? or a very awesome goodness that we should have had since day 1?

Would you have time at the all hands to go together over it and maybe get it done on staging in an hour or so? :)
this is something that would be really nice to get done in Q1, but it is a bit too late for that now.  Next week I would like to resolve the remaining two issues outlined above in person; an hour or two should be plenty.
(Assignee)

Updated

7 years ago
Assignee: nobody → armenzg
Priority: P4 → P3
(Assignee)

Updated

7 years ago
Priority: P3 → P2
(Assignee)

Comment 5

7 years ago
jmaher how are you doing on your side about this?

I have had my eyes set on fixing a bunch of stuff before the May 17th refresh.
I hope to tackle the week after that date.

Setting priority to P3 meaning that I would like to tackle this in the next 2 weeks.
Priority: P2 → P3
the next 2 weeks is great.  My patches for talos proper are just about ready, then we need to sort out the buildbot config changes.
(Assignee)

Comment 7

7 years ago
Now that sdwilsh is gone who is driving this in his place?
Priority: P3 → P4
(Reporter)

Comment 8

7 years ago
(In reply to comment #7)
> Now that sdwilsh is gone who is driving this in his place?
Me still (and I'm not quite gone yet).
(Assignee)

Comment 9

7 years ago
triagefollowup: I am slowing the process by trying to get to it when more higher priority keeps on falling on me. Could you please find someone who could deploy this manually to the Win7 slaves?

jmaher what was again the path to deploy this? C:\perftools?
Assignee: armenzg → nobody
Priority: P4 → --
Whiteboard: [deployment][talos] → [deployment][talos][triagefollowup]
yes, c:\perftools would be great.  As long as the path doesn't have a ' ' in it, that will keep the scripts and other tools easier to work with.

We are waiting for the new test talos master vm to run staging runs before checking in the code to turn this on.
(Assignee)

Comment 11

7 years ago
Thanks jmaher.
Would you like us to hold on deploying it until this get tested in your systems?
if you can get these tools deployed it would be one less dependency.  The good news is the patches are at a r+ state, so we are getting closer to making this a reality.

Updated

7 years ago
Assignee: nobody → coop
Priority: -- → P3
Whiteboard: [deployment][talos][triagefollowup] → [deployment][talos]
Can we revisit this and get this wrapped up?  I finally was able to test my patches in staging and and ready to land.
(Assignee)

Comment 14

7 years ago
coop will be on holidays next week and I will be on buildduty.
If the week is not bad I will be doing few slaves every morning.

> Getting this done relies on having someone (probably me) to have time to
> deploy it manually through VNC/RDP one by one in all ~50 win7 slaves
> (probably 2-3 hours). Before that we would have to deploy it on staging and
> making sure that it runs as expected and yields the information you need.
(Assignee)

Updated

7 years ago
Assignee: coop → armenzg
Priority: P3 → P2
(Assignee)

Comment 15

7 years ago
Returning to coop as I will be away next week and bug 629759 is being more pressing.
Assignee: armenzg → coop
Going to follow same plan as Armen: update a few slaves everyday until we're done.
Status: NEW → ASSIGNED
what is the status of this?  I know we have a lot of slaves, but a few/day and by now we should be pretty close to rolled out?
(Assignee)

Comment 18

7 years ago
Not sure where coop got to (he's gone for holidays).
I will deal with this in the next few days.
Assignee: coop → armenzg
update?
(Assignee)

Comment 20

7 years ago
The rest of my day will be dedicated to this besides small tasks.
I will update at my EOD.
Priority: P2 → P1
(Assignee)

Comment 21

7 years ago
I have been able to generate the wpt_x86.msi and place it on:
http://dev-stage01.build.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/wpt_x86.msi

I am trying to figure out what the correct command lines are to deploy it.
(Assignee)

Comment 22

7 years ago
Created attachment 553532 [details]
bat file to install Windows Performance Toolkit

It seems that the following command does the job but a UAC message comes up:
msiexec /passive /i “C:\Users\cltbld\Desktop\wpt_x86.msi” /log wpt_x86.log WPFPERFDIR=C:\perftools

jmaher does it look good to you?
Attachment #553532 - Flags: review?(jmaher)
Comment on attachment 553532 [details]
bat file to install Windows Performance Toolkit

this looks like the correct .msi and WFPPERFDIR!

Thanks!
Attachment #553532 - Flags: review?(jmaher) → review+
(Assignee)

Comment 24

7 years ago
I deployed this to half the win7 slaves. I will do the other half tomorrow.

Something to notice is that I will have to do the following slaves once they are rebooted by IT:
talos-r3-w7-011
talos-r3-w7-019
talos-r3-w7-036

I also have to deploy this to talos-r3-w7-ref and ask IT to take a snapshot.

This is the commands I have been following:
> wget --no-check-certificate -Owpt.bat https://bugzilla.mozilla.org/attachment.cgi?id=553532
> wpt.bat
> click "Yes" on UAC prompt
(Assignee)

Updated

7 years ago
Depends on: 678883
(Assignee)

Comment 25

7 years ago
I did few more slaves in the morning but the network is bad again.

Tonight IT will have a downtime for the network state so tomorrow should be easier.
(Assignee)

Updated

7 years ago
Depends on: 680445
(Assignee)

Comment 26

7 years ago
I have done all slaves but the ones mentioned in comment 24.

IT will kick the ref image in bug 680445 and the remaining slaves in bug 678883.

Once they are up I will deployed unto them.

Documentation updated as well:
https://wiki.mozilla.org/index.php?title=ReferencePlatforms/Test/Win7#Xperf
(Assignee)

Updated

7 years ago
Priority: P1 → P3
I suspect we cannot talk to 10.2.76.100 from the talos slave.

can we try:
wget 'http://10.2.76.100'
wget 'http://brasstacks.mozilla.com'

I suspect the first wget will result in a timeout, error or something like that (404?) and the second one will immediately return with a downloaded index.html.

If this is the case, we can fix the hardcoded servername in the xperf log parser to use brasstacks.mozilla.com and we can start logging our data there.
(Assignee)

Comment 28

7 years ago
Actually both return an index.html with the same contents :S
(Assignee)

Comment 29

7 years ago
FTR I can ping to the first address but not the second one:

C:\Users\cltbld>ping 10.2.76.100
                
Pinging 10.2.76.100 with 32 bytes of data:                     
Reply from 10.2.76.100: bytes=32 time=3ms TTL=60
Reply from 10.2.76.100: bytes=32 time=2ms TTL=60               
Reply from 10.2.76.100: bytes=32 time=2ms TTL=60
                
Ping statistics for 10.2.76.100:               
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),       
Approximate round trip times in milli-seconds:.215
    Minimum = 2ms, Maximum = 3ms, Average = 2ms.215|:80... 

C:\Users\cltbld>ping brasstacks.mozilla.com
                
Pinging brasstacks.sj.mozilla.com [63.245.208.215] with 32 bytes of data:
Request timed out.

Perhaps arr and dustin can notice something we are doing wrong right away.
Joel, let me know what you're seeing, and what's expected, and I'll be happy to take a look.
(Assignee)

Comment 31

7 years ago
To reboot talos-r3-w7-036 see bug 682698.
Depends on: 682698
(Assignee)

Comment 32

7 years ago
I deployed this to slaves #11 and #19.

We are waiting on a reboot on bug 682698 for #36.

I can't access the ref machine even after the reboot in bug 680445. I will ask IT.
(Assignee)

Comment 33

7 years ago
I took care of slave #36 as well.

We are now waiting on bug 680445.
Whiteboard: [deployment][talos] → [deployment][talos] waiting on talos-r3-w7-ref reboot
(Assignee)

Updated

6 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.