New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 850170 link

Starred by 2 users
Status: Assigned
Owner:
█ andypaicu@chromium.org
Last visit > 30 days ago
Cc:
█ andypaicu@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug

Blocking:
issue 704259



Sign in to add a comment

"virtual/reporting-api/external/wpt/content-security-policy/reporting-api/reporting-api-doesnt-send-reports-without-violation.https.sub.html" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jun 6 2018 
"virtual/reporting-api/external/wpt/content-security-policy/reporting-api/reporting-api-doesnt-send-reports-without-violation.https.sub.html" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNylwELEgVGbGFrZSKLAXZpcnR1YWwvcmVwb3J0aW5nLWFwaS9leHRlcm5hbC93cHQvY29udGVudC1zZWN1cml0eS1wb2xpY3kvcmVwb3J0aW5nLWFwaS9yZXBvcnRpbmctYXBpLWRvZXNudC1zZW5kLXJlcG9ydHMtd2l0aG91dC12aW9sYXRpb24uaHR0cHMuc3ViLmh0bWwM.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs

Comment 1 by mcnee@chromium.org, Jun 6 2018

Cc: andypaicu@chromium.org
Components: Blink>SecurityFeature>ContentSecurityPolicy

Comment 2 by glider@chromium.org, Jun 7 2018

Owner: andypaicu@chromium.org
Status: Assigned (was: Untriaged)
Andy, can you please take a look? Thanks!

Comment 3 by mpear...@chromium.org, Jun 8 2018 

FYI, these are timeouts.

Comment 4 by mpear...@chromium.org, Jun 8 2018 

Sending disable changelist to commit queue:
https://chromium-review.googlesource.com/c/chromium/src/+/1093654
Project Member

Comment 5 by bugdroid1@chromium.org, Jun 8 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1eb9ae81e31e95eec7e66f62b851b1f7a97e0b97

commit 1eb9ae81e31e95eec7e66f62b851b1f7a97e0b97
Author: Mark Pearson <mpearson@chromium.org>
Date: Fri Jun 08 20:58:38 2018

Disable Reporting API Test on Mac

Disables
virtual/reporting-api/external/wpt/content-security-policy/reporting-api/reporting-api-doesnt-send-reports-without-violation.https.sub.html

TBR=andypaicu
NOTRY=true

Bug: 850170
Change-Id: I3b2c5d73152ef72a13fd6e3e2efb2337f2b66d5a
Reviewed-on: https://chromium-review.googlesource.com/1093654
Commit-Queue: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565738}
[modify] https://crrev.com/1eb9ae81e31e95eec7e66f62b851b1f7a97e0b97/third_party/WebKit/LayoutTests/TestExpectations

Comment 6 by mpear...@chromium.org, Jun 8 2018

Labels: -Sheriff-Chromium
Removing from sheriff queue.

Comment 7 by kbr@chromium.org, Jul 1

Blocking: 704259
Labels: OS-Linux OS-Mac OS-Windows
This test has been seen to crash on linux_chromium_rel_ng as well:

Failing tryjob:
https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux_chromium_rel_ng/131166

Failing shard:
https://chromium-swarm.appspot.com/task?id=3e6ba83f852f1610&refresh=10&show_raw=1

There are already Timeout exceptions for this test on Win10, Mac and Linux.

Expanding existing Timeout suppression on Linux.

Log excerpt:
15:38:54.193 26861 worker/3 virtual/reporting-api/external/wpt/content-security-policy/reporting-api/reporting-api-doesnt-send-reports-without-violation.https.sub.html crashed, (stderr lines):
15:38:54.193 26861   [1655:1716:0630/153853.799464:FATAL:reporting_cache.cc(210)] Check failed: client. 
15:38:54.193 26861   #0 0x000003caa69c base::debug::StackTrace::StackTrace()
15:38:54.194 26861   #1 0x000003c2324b logging::LogMessage::~LogMessage()
15:38:54.194 26861   #2 0x000004122c99 net::(anonymous namespace)::ReportingCacheImpl::IncrementEndpointDeliveries()
15:38:54.194 26861   #3 0x000004129b89 net::(anonymous namespace)::ReportingDeliveryAgentImpl::OnUploadComplete()
15:38:54.194 26861   #4 0x000001f2cb14 _ZN4base8internal7InvokerINS0_9BindStateIMN5media13FFmpegDemuxerEFvRKNS_17RepeatingCallbackIFvNS3_14PipelineStatusEEEEiEJNS_7WeakPtrIS4_EES8_EEEFviEE3RunEPNS0_13BindStateBaseEi
15:38:54.194 26861   #5 0x00000412c23d net::(anonymous namespace)::ReportingUploaderImpl::OnResponseStarted()
15:38:54.194 26861   #6 0x0000040ea952 net::URLRequest::NotifyResponseStarted()
15:38:54.194 26861   #7 0x0000041101b1 net::URLRequestJob::NotifyHeadersComplete()
15:38:54.194 26861   #8 0x000004113681 net::URLRequestHttpJob::NotifyHeadersComplete()
15:38:54.194 26861   #9 0x0000041160fd net::URLRequestHttpJob::SaveCookiesAndNotifyHeadersComplete()
15:38:54.194 26861   #10 0x000004115389 net::URLRequestHttpJob::OnStartCompleted()
15:38:54.194 26861   #11 0x000003f3b669 net::HttpCache::Transaction::DoLoop()
15:38:54.194 26861   #12 0x000001da7ccc _ZN4base8internal7InvokerINS0_9BindStateIMN5media12PipelineImpl15RendererWrapperEFvNS3_14PipelineStatusEEJNS_7WeakPtrIS5_EEEEEFvS6_EE3RunEPNS0_13BindStateBaseES6_
15:38:54.194 26861   #13 0x000003f5aa0b net::HttpNetworkTransaction::DoCallback()
15:38:54.194 26861   #14 0x000003f87f6e net::HttpStreamParser::OnIOComplete()
15:38:54.194 26861   #15 0x000001da7ccc _ZN4base8internal7InvokerINS0_9BindStateIMN5media12PipelineImpl15RendererWrapperEFvNS3_14PipelineStatusEEJNS_7WeakPtrIS5_EEEEEFvS6_EE3RunEPNS0_13BindStateBaseES6_
15:38:54.194 26861   #16 0x000003f7a25b net::SSLClientSocketImpl::DoReadCallback()
15:38:54.194 26861   #17 0x000003f79ffd net::SSLClientSocketImpl::RetryAllOperations()
15:38:54.194 26861   #18 0x000003f7f12a net::SocketBIOAdapter::OnSocketReadIfReadyComplete()
15:38:54.194 26861   #19 0x000001da7ccc _ZN4base8internal7InvokerINS0_9BindStateIMN5media12PipelineImpl15RendererWrapperEFvNS3_14PipelineStatusEEJNS_7WeakPtrIS5_EEEEEFvS6_EE3RunEPNS0_13BindStateBaseES6_
15:38:54.194 26861   #20 0x000003ffb97c net::TCPClientSocket::DidCompleteRead()
15:38:54.194 26861   #21 0x000003ff5b5c _ZN4base8internal7InvokerINS0_9BindStateIMN3net17SOCKSClientSocketEFvNS_12OnceCallbackIFviEEEiEJNS0_17UnretainedWrapperIS4_EES7_EEES6_E7RunOnceEPNS0_13BindStateBaseEi
15:38:54.194 26861   #22 0x00000412fc7a net::TCPSocketPosix::ReadIfReadyCompleted()
15:38:54.194 26861   #23 0x000003ff5b5c _ZN4base8internal7InvokerINS0_9BindStateIMN3net17SOCKSClientSocketEFvNS_12OnceCallbackIFviEEEiEJNS0_17UnretainedWrapperIS4_EES7_EEES6_E7RunOnceEPNS0_13BindStateBaseEi
15:38:54.194 26861   #24 0x00000413431f net::SocketPosix::ReadCompleted()
15:38:54.194 26861   #25 0x000004134029 net::SocketPosix::OnFileCanReadWithoutBlocking()
15:38:54.194 26861   #26 0x000003cc926c base::MessagePumpLibevent::OnLibeventNotification()
15:38:54.194 26861   #27 0x000003cd2efd event_base_loop
15:38:54.194 26861   #28 0x000003cc95f1 base::MessagePumpLibevent::Run()
15:38:54.194 26861   #29 0x000003c29471 base::MessageLoop::Run()
15:38:54.194 26861   #30 0x000003c4da56 base::RunLoop::Run()
15:38:54.194 26861   #31 0x000003c7c5ca base::Thread::Run()
15:38:54.194 26861   #32 0x0000032f2f94 content::BrowserProcessSubThread::IOThreadRun()
15:38:54.194 26861   #33 0x0000032f2edf content::BrowserProcessSubThread::Run()
15:38:54.194 26861   #34 0x000003c7c91f base::Thread::ThreadMain()
15:38:54.194 26861   #35 0x000003cbcccf base::(anonymous namespace)::ThreadFunc()
15:38:54.194 26861   #36 0x7f892d0ba184 start_thread
15:38:54.195 26861   #37 0x7f892889803d clone
Project Member

Comment 8 by bugdroid1@chromium.org, Jul 1 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/43985e3c31cd93188ad13ebee39bce32d73bf04d

commit 43985e3c31cd93188ad13ebee39bce32d73bf04d
Author: Kenneth Russell <kbr@chromium.org>
Date: Sun Jul 01 23:18:40 2018

Expand reporting API layout test suppression.

  virtual/reporting-api/external/wpt/content-security-policy/reporting-api/
    reporting-api-doesnt-send-reports-without-violation.https.sub.html

is flakily timing out / crashing on essentially all platforms.
Simplify suppression.

Bug: 626703, 850170
Change-Id: I69a010337561cd8e5f794aa9673d1ec42cc126c6
Tbr: mpearson@chromium.org
Tbr: andypaicu@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1121833
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571799}
[modify] https://crrev.com/43985e3c31cd93188ad13ebee39bce32d73bf04d/third_party/WebKit/LayoutTests/TestExpectations
►

Sign in to add a comment