New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 666077 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature

Blocked on: View detail
issue 680631
issue 680675
issue 680797
issue 680341
issue 680684
issue 680720
issue 680838
issue 682438



Sign in to add a comment

machine to run angle/ozone tests

Project Member Reported by fjhenigman@chromium.org, Nov 16 2016

Issue description

Need a physical machine with latest possible Ubuntu (xenial might work, yakkety might be better) and an Intel GPU (something a few years old will suffice).
 
Cc: fjhenigman@chromium.org
Labels: OS-Linux
Status: Available
Ken, again can you send this to the right person?

We'll need this to test Ozone angle_end2end_tests on the chromium.gpy.fyi waterfall. This machine should have the same hardware and OS installed as the "New Intel" Linux tester:

http://build.chromium.org/p/chromium.gpu.fyi/waterfall?builder=Linux%20Release%20(New%20Intel)

Comment 2 by kbr@chromium.org, Nov 16 2016

Cc: d...@chromium.org jo...@chromium.org pschmidt@chromium.org
Labels: -Type-Bug Type-Feature
Owner: ----
Bryce, Peter, John: could one of you please handle this hardware request?

It's to allocate another machine with the same hardware (if possible) as build73-b1:
https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20%28New%20Intel%29

and to image it with either Xenial or Yakkety, whichever image you have available.

It should be able to talk to master.chromium.gpu.fyi.

Thanks very much.

Comment 3 by d...@chromium.org, Nov 16 2016

build73-b1 is one of the small form factor Optiplex 9020Ms. I don't know if we have any on hand (Peter would know, I believe he's ordered these the last couple of times they've been requested).

Peter - it might be worth while to work with Vince on ordering a few of these to keep in inventory now that we've got a handful of them kicking around and now another request for one?

Comment 4 by pschm...@google.com, Nov 16 2016

Owner: pschmidt@chromium.org
Status: Assigned (was: Available)
I chatted with Vince a few weeks ago about getting some more.   I'll see where we are at with that.
Cc: kbr@chromium.org
+kbr  since he may request that we update the hardware on his side at the same time.

The Optiplex 9020M's are no longer available.   They have the i5-4590T with HD4600 graphics ( http://ark.intel.com/products/78928/Intel-Core-i5-4590T-Processor-6M-Cache-up-to-3_00-GHz )

Nothing in that processor is available anymore.

Currently being offered in the same form factor from dell is based on a i5-6500T with HD530 graphics ( http://ark.intel.com/products/88183/Intel-Core-i5-6500T-Processor-6M-Cache-up-to-3_10-GHz)
New desktops have been ordered.  ETA end of next week.

Comment 8 by kbr@chromium.org, Nov 21 2016

Thank you Peter!

Thanks Peter and Ken!
Status: Started (was: Assigned)
The replacement desktops have arrived.  Re: #8, want the same driver versions (if possible)?
On mine I'd like the latest stock Ubuntu you can manage, hopefully at least xenial, and later might be better.

Ken will let you know about the others.  Perhaps they should be a different bug.

Comment 12 by kbr@chromium.org, Dec 9 2016

Peter: for the new Windows machines we'd like Windows 10, to match the newly-renamed:

https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Release%20(New%20Intel)
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Debug%20(New%20Intel)

For the new Linux desktops, Xenial sounds good. If there's a later Ubuntu version that offers a Mesa upgrade (the current bots run 11.2.0), that would be fine too.

https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20(New%20Intel)
https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Debug%20(New%20Intel)

(look at e.g. https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20%28New%20Intel%29/builds/3461/steps/webgl_conformance_tests/logs/stdio and search for "driver_version")

Thanks again.

To recap. These are Dell Optiplex 7040 with Intel HD530 graphics.

The windows 10 bots are build{159,160}-b1  and have driver version 22.20.16.4542 installed (the latest stable from Intel)

The linux bots are build{156..158}-b1.  They are running Ubuntu 16.10 as that is what the latest Intel supports per https://01.org/linuxgraphics/downloads/intel-graphics-update-tool-linux-os-v2.0.3   Ken gets 2 of these.

Let me know when I can reclaim the old ones.
Thanks Peter - Frank can you look at the next steps for integrating I think one of the Linux bots (build{156..158}-b1) as a ChromeOS Ozone tester? I'm not sure if we want to swarm this configuration - that would allow us to run on the CQ but we might not have enough capacity. Ken, any thoughts on this?
Looking at #13, I think we got two machines. I think we should only use one for the GPY FYI bots and forget about swarming, didn't realize the situation.

Peter/Ken, which machine should we use for the Ozone tester? How do we make it appear on the waterfall? I looked in the GPU testing docs and didn't see a note of how to add an entirely new bot.
I'm able to log in to build158-b1.  I'll play around with it to see if it meets my needs.
Ken: feel free to claim 156 and 157.

Comment 17 by kbr@chromium.org, Jan 10 2017

Jamie: the GPU bot details at https://www.chromium.org/developers/testing/gpu-testing/gpu-bot-details discuss how to add a completely new bot. If the documentation is inadequate, please tell me.

Peter: thanks for the hardware. I'm working on deploying it now.

Project Member

Comment 18 by bugdroid1@chromium.org, Jan 10 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build.git/+/f159e1653968e108583688efa5043a7903d8772c

commit f159e1653968e108583688efa5043a7903d8772c
Author: Kenneth Russell <kbr@chromium.org>
Date: Tue Jan 10 03:36:56 2017

Deploy new Win and Linux Intel HD 530 GPU bots.

BUG= 666077 

Change-Id: Ib8eab45a4027e775a8b7dc28bc10ce283677af8d
TBR=dpranke@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/426069
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>

[modify] https://crrev.com/f159e1653968e108583688efa5043a7903d8772c/masters/master.chromium.gpu.fyi/slaves.cfg
[modify] https://crrev.com/f159e1653968e108583688efa5043a7903d8772c/scripts/slave/recipe_modules/chromium_tests/chromium_gpu_fyi.py
[modify] https://crrev.com/f159e1653968e108583688efa5043a7903d8772c/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_GPU_Linux_Builder.json
[modify] https://crrev.com/f159e1653968e108583688efa5043a7903d8772c/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_GPU_Linux_Builder__dbg_.json
[modify] https://crrev.com/f159e1653968e108583688efa5043a7903d8772c/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_GPU_Win_Builder.json
[modify] https://crrev.com/f159e1653968e108583688efa5043a7903d8772c/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_GPU_Win_Builder__dbg_.json
[add] https://crrev.com/f159e1653968e108583688efa5043a7903d8772c/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_Linux_Debug__Intel_HD_530_.json
[add] https://crrev.com/f159e1653968e108583688efa5043a7903d8772c/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_Linux_Release__Intel_HD_530_.json
[add] https://crrev.com/f159e1653968e108583688efa5043a7903d8772c/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_Win10_Debug__Intel_HD_530_.json
[add] https://crrev.com/f159e1653968e108583688efa5043a7903d8772c/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_Win10_Release__Intel_HD_530_.json

Project Member

Comment 19 by bugdroid1@chromium.org, Jan 10 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager.git/+/64ddf0f5ee75c83bda1e3fc3b52bb27be5cd1718

commit 64ddf0f5ee75c83bda1e3fc3b52bb27be5cd1718
Author: Kenneth Russell <kbr@chromium.org>
Date: Tue Jan 10 04:41:41 2017

Project Member

Comment 20 by bugdroid1@chromium.org, Jan 10 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7ee72b94db9dae6d1198b2a48f1db3981e487137

commit 7ee72b94db9dae6d1198b2a48f1db3981e487137
Author: kbr <kbr@chromium.org>
Date: Tue Jan 10 04:48:23 2017

Deploy new Win and Linux Intel HD 530 GPU bots.

Also removed entries for obsolete Win7 Intel bots.

BUG= 666077 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=zmo@chromium.org
NOTRY=true

Review-Url: https://codereview.chromium.org/2623773003
Cr-Commit-Position: refs/heads/master@{#442479}

[modify] https://crrev.com/7ee72b94db9dae6d1198b2a48f1db3981e487137/content/test/gpu/generate_buildbot_json.py
[modify] https://crrev.com/7ee72b94db9dae6d1198b2a48f1db3981e487137/testing/buildbot/chromium.gpu.fyi.json

Comment 21 by kbr@chromium.org, Jan 10 2017

Cc: yang...@intel.com

Comment 22 by kbr@chromium.org, Jan 12 2017

Blockedon: 680341
Project Member

Comment 23 by bugdroid1@chromium.org, Jan 12 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/aafe57504428af825ec9aaf4f690194bb504acbe

commit aafe57504428af825ec9aaf4f690194bb504acbe
Author: kbr <kbr@chromium.org>
Date: Thu Jan 12 01:11:01 2017

Run WebGL2 ANGLE tests on Linux Intel HD 530.

Thanks to zmo@ for catching this omission.

BUG= 666077 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
NOTRY=true

Review-Url: https://codereview.chromium.org/2623223004
Cr-Commit-Position: refs/heads/master@{#443102}

[modify] https://crrev.com/aafe57504428af825ec9aaf4f690194bb504acbe/content/test/gpu/generate_buildbot_json.py
[modify] https://crrev.com/aafe57504428af825ec9aaf4f690194bb504acbe/testing/buildbot/chromium.gpu.fyi.json

Comment 24 by zmo@chromium.org, Jan 12 2017

Blockedon: 680631

Comment 25 by zmo@chromium.org, Jan 12 2017

Blockedon: 680675

Comment 26 by zmo@chromium.org, Jan 12 2017

Blockedon: 680684

Comment 27 by zmo@chromium.org, Jan 12 2017

Blockedon: 680720

Comment 28 by zmo@chromium.org, Jan 13 2017

Blockedon: 680797
Cc: yunchao...@intel.com qiankun....@intel.com

Comment 30 by kbr@chromium.org, Jan 13 2017

Blockedon: 680838

Comment 31 by kbr@chromium.org, Jan 18 2017

Blockedon: 682438
Project Member

Comment 32 by bugdroid1@chromium.org, Jan 18 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build.git/+/1d19b1dfa232e1b0a12b16187f16078c54f81d10

commit 1d19b1dfa232e1b0a12b16187f16078c54f81d10
Author: Kenneth Russell <kbr@chromium.org>
Date: Wed Jan 18 22:37:19 2017

Deploy experimental NVIDIA Retina bot. Remove old Intel bots.

BUG= 666077 ,  682432 
TBR=dpranke@chromium.org,zmo@chromium.org

Change-Id: I1700c67285cf135106fd402e29a4a83aaaed3592
Reviewed-on: https://chromium-review.googlesource.com/430191
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>

[modify] https://crrev.com/1d19b1dfa232e1b0a12b16187f16078c54f81d10/masters/master.chromium.gpu.fyi/builders.pyl
[modify] https://crrev.com/1d19b1dfa232e1b0a12b16187f16078c54f81d10/scripts/slave/recipe_modules/chromium_tests/chromium_gpu_fyi.py
[modify] https://crrev.com/1d19b1dfa232e1b0a12b16187f16078c54f81d10/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_GPU_Linux_Builder.json
[modify] https://crrev.com/1d19b1dfa232e1b0a12b16187f16078c54f81d10/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_GPU_Linux_Builder__dbg_.json
[modify] https://crrev.com/1d19b1dfa232e1b0a12b16187f16078c54f81d10/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_GPU_Mac_Builder.json
[modify] https://crrev.com/1d19b1dfa232e1b0a12b16187f16078c54f81d10/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_GPU_Win_Builder.json
[modify] https://crrev.com/1d19b1dfa232e1b0a12b16187f16078c54f81d10/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_GPU_Win_Builder__dbg_.json
[delete] https://crrev.com/f60ccbbb9edc5836a86c2df49d4f6879eaa19ec4/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_Linux_Release__New_Intel_.json
[rename] https://crrev.com/1d19b1dfa232e1b0a12b16187f16078c54f81d10/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_Mac_Experimental_Retina_Release__NVIDIA_.json
[delete] https://crrev.com/f60ccbbb9edc5836a86c2df49d4f6879eaa19ec4/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_Win10_Debug__New_Intel_.json
[delete] https://crrev.com/f60ccbbb9edc5836a86c2df49d4f6879eaa19ec4/scripts/slave/recipes/chromium.expected/full_chromium_gpu_fyi_Win10_Release__New_Intel_.json

Project Member

Comment 33 by bugdroid1@chromium.org, Jan 18 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8bec6b2ef1c8d45c613aa0aca47f1ae15bd05281

commit 8bec6b2ef1c8d45c613aa0aca47f1ae15bd05281
Author: kbr <kbr@chromium.org>
Date: Wed Jan 18 23:08:29 2017

Deploy experimental NVIDIA Retina bot. Remove old Intel bots.

BUG= 666077 ,  682432 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=zmo@chromium.org
NOTRY=true

Review-Url: https://codereview.chromium.org/2640813003
Cr-Commit-Position: refs/heads/master@{#444533}

[modify] https://crrev.com/8bec6b2ef1c8d45c613aa0aca47f1ae15bd05281/content/test/gpu/generate_buildbot_json.py
[modify] https://crrev.com/8bec6b2ef1c8d45c613aa0aca47f1ae15bd05281/testing/buildbot/chromium.gpu.fyi.json

Status: Fixed (was: Started)

Sign in to add a comment