Some Windows GPU swarming machines missing D3D11 debug runtime |
||||||
Issue descriptionSee prior issue 756123 where successfully set up the D3D11 debug runtime on the swarming GPU testers. It looks like this package is missing from one or more machines. One missing machine is an NVIDIA Windows 10 tester: https://chromium-swarm.appspot.com/task?id=3c57710e8a412d10&refresh=10&show_raw=1 Here you can find a lot of messages like this: [ RUN ] AttributeLayoutNonIndexed.Test/ES2_D3D11 Warning: initializeD3DDevice(776): Failed creating Debug D3D11 device - falling back to release runtime. Other machines correctly have the runtime installed, for example these AMD and Intel machines: https://chromium-swarm.appspot.com/task?id=3c57720225ee0e10&refresh=10&show_raw=1 https://chromium-swarm.appspot.com/task?id=3c57728381fc4d10&refresh=10&show_raw=1 Here these machines caught a real error with the installed runtime: Message 0: ID3D11Device::CreateInputLayout: The provided input signature expects to read an element with SemanticName/Index: 'TEXCOORD'/1 and component(s) of the type 'uint32'. However, the matching entry in the Input Layout declaration, element[1], specifies mismatched format: 'R32G32B32A32_FLOAT'. This is not an error, since behavior is well defined: The element format determines what data conversion algorithm gets applied before it shows up in a shader register. Independently, the shader input signature defines how the shader will interpret the data that has been placed in its input registers, with no change in the bits stored. It is valid for the application to reinterpret data as a different type once it is in the vertex shader, so this warning is issued just in case reinterpretation was not intended by the author. ../../third_party/angle/src/tests/test_utils/ANGLETest.cpp(741): error: Failed 1 D3D11 SDK Layers message(s) detected! Test Failed. Could we check to see which machines need to have the feature installed, and update them?
,
Mar 27 2018
,
Mar 27 2018
I don't recall ever installing the Graphics Feature on any Win10 image. I'm updating the current image and will include it in the new spin.
,
Mar 29 2018
John, any chance you can help push this through?
,
Mar 30 2018
Will investigate. Thanks!
,
Apr 6 2018
My guess here is that the package is targeted at the old GT610 GPU_ID, and some bots may have been re-installed or deployed since they got new GPUs. https://chrome-internal.googlesource.com/infra/puppet/+/998d8185d0bed41e38150c4601dc90afd63a614d/puppetm/opt/puppet/conf/nodes.yaml#1593 Also, it does look like the package is now included in the latest Win10 base-image (comment #3), but what we can do is also update puppet to target 10de:1cb3 to get it pushed out to any bots that are currently missing it.
,
Apr 6 2018
SGTM to push a new image to the Win10 NVIDIA bots. We just need to make sure that the NVIDIA driver version is the same as currently, which is 388.16: https://cs.chromium.org/chromium/src/content/test/gpu/generate_buildbot_json.py?q=generate_buildbot_js&sq=package:chromium&l=23 Can you confirm that John? Thanks.
,
Apr 6 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/infra/puppet/+/7f7d0b7ac1b469cfce4b45dcff625afd6f517f0c commit 7f7d0b7ac1b469cfce4b45dcff625afd6f517f0c Author: John Weathersby <johnw@google.com> Date: Fri Apr 06 19:02:04 2018
,
Apr 6 2018
I don't think we'll need to push a new image, just the right package, targeted to the right hosts. This was done in c#8. Verified with build904-m4 which was previously missing the package. It now appears to have the optional feature installed. Hopefully that takes care of any stragglers. Thanks!
,
Apr 6 2018
Thanks very much for this John.
,
Apr 7 2018
Thank you John! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kbr@chromium.org
, Mar 21 2018