Investigate D3D11 Errors/Warnings Generated from running tests

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Build ANGLE with Debug
2. Drop DLLs in Canary
3. Run with --gpu-startup-dialog, attach, and run the CTS

What is the expected output? What do you see instead?
We see error messages in the log such as:

    D3D11 WARNING: ID3D11Device::CreateInputLayout: The provided input signature expects to read an element with SemanticName/Index: 'TEXCOORD'/0 and component(s) of the type 'uint32'.  However, the matching entry in the Input Layout declaration, element[0], specifies mismatched format: 'R16G16B16A16_SINT'.  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. [ STATE_CREATION WARNING #391: CREATEINPUTLAYOUT_TYPE_MISMATCH]
      D3D11 ERROR: ID3D11DeviceContext::CopySubresourceRegion: pSrcBox is not a valid box for the source subresource. *pSrcBox = { left:0, top:0, front:0, right:786444, bottom:1, back:1 }. SrcSubresource = { left:0, top:0, front:0, right:786432, bottom:1, back:1 }. [ RESOURCE_MANIPULATION ERROR #280: COPYSUBRESOURCEREGION_INVALIDSOURCEBOX]
      D3D11 WARNING: ID3D11DeviceContext::DrawIndexedInstanced: Vertex Buffer at the input vertex slot 1 is not big enough for what the Draw*() call expects to traverse. This is OK, as reading off the end of the Buffer is defined to return 0. However the developer probably did not intend to make use of this behavior.  [ EXECUTION WARNING #356: DEVICE_DRAW_VERTEX_BUFFER_TOO_SMALL]

Original issue reported on code.google.com by jmad...@chromium.org on 5 Jun 2014 at 6:17

[GoogleCodeExporter]

Note this was with a series of patches -- I'll run it again shortly with ToT 
and see if that isn't a false alarm.

Original comment by jmad...@chromium.org on 5 Jun 2014 at 6:19

[GoogleCodeExporter]

It seems the CopySubresourceRegion error was crashing older nVidia drives, 
though new ones are more robust. See issue chromium:384420. The error is during 
native buffer storage resize data copy step using the new large size instead of 
the old smaller size.

Also we are triggering D3D11 errors in the gl-pointcoord test and we should 
investigate those.

Original comment by jmad...@chromium.org on 16 Jun 2014 at 5:18

• Changed state: Started

[GoogleCodeExporter]

Original comment by jmad...@chromium.org on 16 Jun 2014 at 5:18

[GoogleCodeExporter]

https://chromium-review.googlesource.com/#/c/203776

Original comment by jmad...@chromium.org on 16 Jun 2014 at 5:21

• Changed state: Review

[GoogleCodeExporter]

https://chromium-review.googlesource.com/#/c/203778/

Original comment by jmad...@chromium.org on 23 Jun 2014 at 2:58

[GoogleCodeExporter]

Just picked up these from angle_tests:

D3D11 WARNING: ID3D11DeviceContext::DrawIndexed: Vertex Buffer at the input 
vertex slot 0 is not big enough for what the Draw*() call expects to traverse. 
This is OK, as reading off the end of the Buffer is defined to return 0. 
However the developer probably did not intend to make use of this behavior.  [ 
EXECUTION WARNING #356: DEVICE_DRAW_VERTEX_BUFFER_TOO_SMALL]
D3D11 ERROR: ID3D11DeviceContext::Map: This resource is already mapped! [ 
RESOURCE_MANIPULATION ERROR #2097213: RESOURCE_MAP_ALREADYMAPPED]
D3D11 ERROR: ID3D11DeviceContext::CopySubresourceRegion: Cannot invoke 
CopySubresourceRegion while a Subresource of the source is mapped.Source 
subresource (0) is mapped. [ RESOURCE_MANIPULATION ERROR #283: 
COPYSUBRESOURCEREGION_INVALIDSOURCESTATE]

Looks like some of them are from the PBO/ReadPixels tests.

Original comment by jmad...@chromium.org on 12 Sep 2014 at 8:25

• Changed title: Investigate D3D11 Errors/Warnings Generated from running tests