Pixel_CSSFilterEffects and Pixel_WebGLSadCanvas flaky on ATI GPU on Mac Retina on Mac-10.13.6 |
||||
Issue descriptionhttps://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Experimental%20Retina%20Release%20%28AMD%29/3931 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Experimental%20Retina%20Release%20%28AMD%29/3926 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Experimental%20Retina%20Release%20%28AMD%29/3925 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Experimental%20Retina%20Release%20%28AMD%29/3922 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Experimental%20Retina%20Release%20%28AMD%29/3917 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Experimental%20Retina%20Release%20%28AMD%29/3915 Pixel_WebGLSadCanvas seems to crash, Received signal 11 SEGV_MAPERR 000000000000 0 Chromium Framework 0x0000000113a286ac base::debug::StackTrace::StackTrace(unsigned long) + 28 1 Chromium Framework 0x0000000113a284e1 base::debug::(anonymous namespace)::StackDumpSignalHandler(int, __siginfo*, void*) + 2401 2 libsystem_platform.dylib 0x00007fff5134ff5a _sigtramp + 26 3 Chromium Framework 0x000000011398fed7 base::SequenceCheckerImpl::CalledOnValidSequence() const + 183 4 Chromium Framework 0x0000000115988d6d viz::GpuServiceImpl::Crash() + 173 5 Chromium Framework 0x0000000110c9f90a viz::mojom::GpuServiceStubDispatch::Accept(viz::mojom::GpuService*, mojo::Message*) + 2762 6 Chromium Framework 0x0000000113a9b556 mojo::InterfaceEndpointClient::HandleValidatedMessage(mojo::Message*) + 982 7 Chromium Framework 0x0000000113a9adf6 mojo::FilterChain::Accept(mojo::Message*) + 150 8 Chromium Framework 0x0000000113a9c935 mojo::InterfaceEndpointClient::HandleIncomingMessage(mojo::Message*) + 117 9 Chromium Framework 0x0000000113aa318b mojo::internal::MultiplexRouter::ProcessIncomingMessage(mojo::internal::MultiplexRouter::MessageWrapper*, mojo::internal::MultiplexRouter::ClientCallBehavior, base::SequencedTaskRunner*) + 1451 10 Chromium Framework 0x0000000113aa2570 mojo::internal::MultiplexRouter::Accept(mojo::Message*) + 368 11 Chromium Framework 0x0000000113a9adf6 mojo::FilterChain::Accept(mojo::Message*) + 150 12 Chromium Framework 0x0000000113a95e93 mojo::Connector::ReadSingleMessage(unsigned int*) + 419 13 Chromium Framework 0x0000000113a96961 mojo::Connector::ReadAllAvailableMessages() + 97 14 Chromium Framework 0x0000000113a96819 mojo::Connector::OnHandleReadyInternal(unsigned int) + 137 15 Chromium Framework 0x00000001104910a7 mojo::SimpleWatcher::DiscardReadyState(base::RepeatingCallback<void (unsigned int)> const&, unsigned int, mojo::HandleSignalsState const&) + 103 16 Chromium Framework 0x0000000113abd84d mojo::SimpleWatcher::OnHandleReady(int, unsigned int, mojo::HandleSignalsState const&) + 365 17 Chromium Framework 0x0000000113abdc86 mojo::SimpleWatcher::Context::Notify(unsigned int, MojoHandleSignalsState, unsigned int) + 854 18 Chromium Framework 0x0000000113abc873 mojo::SimpleWatcher::Context::CallNotify(MojoTrapEvent const*) + 35 19 Chromium Framework 0x0000000110d09787 mojo::core::WatcherDispatcher::InvokeWatchCallback(unsigned long, unsigned int, mojo::core::HandleSignalsState const&, unsigned int) + 119 20 Chromium Framework 0x0000000110d08de2 mojo::core::Watch::InvokeCallback(unsigned int, mojo::core::HandleSignalsState const&, unsigned int) + 194 21 Chromium Framework 0x0000000110d03903 mojo::core::RequestContext::~RequestContext() + 1027 22 Chromium Framework 0x0000000110cf45be mojo::core::NodeChannel::OnChannelMessage(void const*, unsigned long, std::__1::vector<mojo::PlatformHandle, std::__1::allocator<mojo::PlatformHandle> >) + 302 23 Chromium Framework 0x0000000110ce0923 mojo::core::Channel::OnReadComplete(unsigned long, unsigned long*) + 819 24 Chromium Framework 0x0000000110d0fc77 mojo::core::(anonymous namespace)::ChannelPosix::OnFileCanReadWithoutBlocking(int) + 727 25 Chromium Framework 0x0000000113a47890 base::MessagePumpLibevent::OnLibeventNotification(int, short, void*) + 352 26 Chromium Framework 0x0000000113a4907c event_base_loop + 1196 27 Chromium Framework 0x0000000113a47c02 base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) + 434 28 Chromium Framework 0x000000011394bb94 base::MessageLoop::Run(bool) + 132 29 Chromium Framework 0x0000000113988ee9 base::RunLoop::Run() + 249 30 Chromium Framework 0x00000001139ec59e base::Thread::Run(base::RunLoop*) + 206 31 Chromium Framework 0x00000001139ecb17 base::Thread::ThreadMain() + 839 32 Chromium Framework 0x0000000113a3777f base::(anonymous namespace)::ThreadFunc(void*) + 95 33 libsystem_pthread.dylib 0x00007fff51359661 _pthread_body + 340 34 libsystem_pthread.dylib 0x00007fff5135950d _pthread_body + 0 35 libsystem_pthread.dylib 0x00007fff51358bf9 thread_start + 13 Not sure what's wrong with Pixel_CSSFilterEffects. The diff looks all black, but maybe there is more than naked eye can see. http://chromium-browser-gpu-tests.commondatastorage.googleapis.com/view_test_results.html?c9aedcdc73cdaf5656a490ee46b97fa45b535535_Mac_FYI_Experimental_Retina_Release_AMD__telemetry Should we mark these Flaky?
,
Aug 8
Note: Pixel_WebGLSadCanvas deliberately crashes the GPU process. The bug is that we don't always correctly render the sad-canvas icon. Have a CL in progress in Issue 835867.
,
Aug 9
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/25ed0ad36dfd29d69a7ad090a450214e4cddffc5 commit 25ed0ad36dfd29d69a7ad090a450214e4cddffc5 Author: Kenneth Russell <kbr@chromium.org> Date: Thu Aug 09 23:41:24 2018 Suppress flaky tests on macOS 10.13.6 with AMD GPUs. WebGL conformance suppressions: conformance2/textures/misc/tex-mipmap-levels.html conformance2/textures/misc/tex-base-level-bug.html Pixel test suppressions: Pixel_CSSFilterEffects Pixel_WebGLSadCanvas Tbr: ynovikov@chromium.org Bug: 870856, 872423 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Change-Id: I1420fe20b7a64bb40f3ba0209fd9bb08b3213b14 Reviewed-on: https://chromium-review.googlesource.com/1168470 Reviewed-by: Kenneth Russell <kbr@chromium.org> Reviewed-by: Yuly Novikov <ynovikov@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#581958} [modify] https://crrev.com/25ed0ad36dfd29d69a7ad090a450214e4cddffc5/content/test/gpu/gpu_tests/pixel_expectations.py [modify] https://crrev.com/25ed0ad36dfd29d69a7ad090a450214e4cddffc5/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
,
Aug 12
Still flaking even after flaky suppression. When it flakes, it fails 3 times in a row. https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Experimental%20Retina%20Release%20%28AMD%29/3998 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Experimental%20Retina%20Release%20%28AMD%29/3977 Marking failing on this configuration instead.
,
Aug 13
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/57093b6021e8c98eeaa4ee14f24d5dce643e3971 commit 57093b6021e8c98eeaa4ee14f24d5dce643e3971 Author: Kenneth Russell <kbr@chromium.org> Date: Mon Aug 13 01:49:44 2018 Mark Pixel_CSSFilterEffects failing on Mac/AMD 10.13. This test became unacceptably flaky with the upgrade to 10.13.6. Tbr: ynovikov@chromium.org Bug: 872423 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Change-Id: I8fded8d47792dce57ea6da6532f7d42b5c075bd4 Reviewed-on: https://chromium-review.googlesource.com/1172148 Reviewed-by: Kenneth Russell <kbr@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#582492} [modify] https://crrev.com/57093b6021e8c98eeaa4ee14f24d5dce643e3971/content/test/gpu/gpu_tests/pixel_expectations.py
,
Aug 23
,
Aug 23
,
Aug 24
The flakiness has been suppressed. Fixing Pixel_WebGLSadCanvas properly will be done in Issue 835867. We will not fix the Pixel_CSSFilterEffects flakiness. |
||||
►
Sign in to add a comment |
||||
Comment 1 by kbr@chromium.org
, Aug 8Owner: kbr@chromium.org
Status: Assigned (was: Unconfirmed)