Kai Ninomiya cb71ba7b3a Don't use ConsumedError on device initialization errors ... If there's an error during device initialization, it's too early to use ConsumedError (SetErrorCallback can't possibly have been called). In this case, manually handle the error from initialization. This will help us diagnose issue chromium:917555, where device initialization is failing but the error is not printed. TBR: cwallez@chromium.org Bug: chromium:917555 Change-Id: I63ba3983688f508550afe2815ca1dda36130fed1 Reviewed-on: https://dawn-review.googlesource.com/c/3520 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org>		2018-12-22 05:40:11 +00:00
..
common	Disable/avoid some warnings.	2018-12-06 19:01:22 +00:00
dawn_native	Don't use ConsumedError on device initialization errors	2018-12-22 05:40:11 +00:00
dawn_wire	Implement timeline fences in Dawn	2018-12-03 16:57:34 +00:00
fuzzers	WireAndFrontendFuzzer "wait" for all commands before freeing	2018-12-15 10:34:02 +00:00
include	Collect GPU device information for end2end tests - Part I	2018-09-19 00:32:52 +00:00
tests	Rename SetRenderPipeline and SetComputePipeline to SetPipeline	2018-12-21 10:40:26 +00:00
utils	Guard header files in utils with #ifdef and #endif	2018-12-20 11:21:04 +00:00