DISABLE WireBufferMappingWriteTests.DestroyInsideMapWriteCallback
Fails with ASAN, should be fixed after at the same time as dawn:1619. Bug: dawn:1619, dawn:1621 Change-Id: Ia1efbb5466b8e8fbb871c07dd6af53a530620935 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/116360 Reviewed-by: Austin Eng <enga@chromium.org> Kokoro: Kokoro <noreply+kokoro@google.com> Commit-Queue: James Price <jrprice@google.com>
This commit is contained in:
parent
8937ec4e72
commit
3a2573e93c
|
@ -538,7 +538,9 @@ TEST_F(WireBufferMappingWriteTests, UnmapInsideMapWriteCallback) {
|
|||
|
||||
// Test that the MapWriteCallback isn't fired twice the buffer external refcount reaches 0 in
|
||||
// the callback
|
||||
TEST_F(WireBufferMappingWriteTests, DestroyInsideMapWriteCallback) {
|
||||
// TODO(dawn:1621): Suppressed because the mapping handling still touches the buffer after it is
|
||||
// destroyed triggering an ASAN error.
|
||||
TEST_F(WireBufferMappingWriteTests, DISABLED_DestroyInsideMapWriteCallback) {
|
||||
wgpuBufferMapAsync(buffer, WGPUMapMode_Write, 0, kBufferSize, ToMockBufferMapCallback, nullptr);
|
||||
|
||||
uint32_t bufferContent = 31337;
|
||||
|
|
Loading…
Reference in New Issue