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

Issue 697367 link

Starred by 1 user
Status: WontFix
Owner:
sebmarchand@chromium.org
Closed: Mar 2017
Cc:
gov...@chromium.org
█ manoranj...@chromium.org
nyerramilli@chromium.org
mmoss@chromium.org
█ dimu@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Exception in shell_2 is observed for Build 58.0.3027.1 in Official desktop builder.

Project Member Reported by ranjitkan@chromium.org, Mar 1 2017 
Link to Builder:
================
https://uberchromegw.corp.google.com/i/official.desktop/builders/win-asan/builds/543

Link to Log File:
=================
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/mac%20trunk/builds/46290/steps/compile/logs/stdio

Error from the log:
===================
C:\b\build\slave\win-asan\build>call python C:\b\build\scripts\slave\..\..\..\depot_tools\gsutil.py -- cp file://C:\b\build\slave\win-asan\build\src\out\Release\symsrc\chrome_child.dll.pdb\38614B4EE29E466B874F45B56BC3FBAF1\chrome_child.dll.pd_ gs://chromium-browser-symsrv/chrome_child.dll.pdb/38614B4EE29E466B874F45B56BC3FBAF1/chrome_child.dll.pd_ 
Copying file://C:\b\build\slave\win-asan\build\src\out\Release\symsrc\chrome_child.dll.pdb\38614B4EE29E466B874F45B56BC3FBAF1\chrome_child.dll.pd_ [Content-Type=application/octet-stream]...
==> NOTE: You are uploading one or more large file(s), which would run
significantly faster if you enable parallel composite uploads. This
feature can be enabled by editing the
"parallel_composite_upload_threshold" value in your .boto
configuration file. However, note that if you do this you and any
users that download such composite files will need to have a compiled
crcmod installed (see "gsutil help crcmod").

Uploading   ...4EE29E466B874F45B56BC3FBAF1/chrome_child.dll.pd_: 0 B/217.82 MiB    
Uploading   ...4EE29E466B874F45B56BC3FBAF1/chrome_child.dll.pd_: 65.36 KiB/217.82 MiB    
Uploading   ...4EE29E466B874F45B56BC3FBAF1/chrome_child.dll.pd_: 137.36 KiB/217.82 MiB    
Uploading   ...4EE29E466B874F45B56BC3FBAF1/chrome_child.dll.pd_: 209.36 KiB/217.82 MiB    
Uploading   ...4EE29E466B874F45B56BC3FBAF1/chrome_child.dll.pd_: 281.36 KiB/217.82 MiB    
Uploading   ...4EE29E466B874F45B56BC3FBAF1/chrome_child.dll.pd_: 353.36 KiB/217.82 MiB    
Uploading   ...4EE29E466B874F45B56BC3FBAF1/chrome_child.dll.pd_: 425.36 KiB/217.82 MiB    
...

@Sebmarchand or @mmoss, request you to please take a look into it. 

Note: Builds are available for build#58.0.3027.1, but builder is displayed purple.

Thanks.!

Comment 1 by sebmarchand@chromium.org, Mar 1 2017 

Hum, I really can't tell why it's failing, I can't see any explicit failure in the log, could it just be a master restart?

Comment 2 by mmoss@chromium.org, Mar 1 2017

Status: WontFix (was: Assigned)
I think it may have failed because of the earlier error:

Uploading   ...hrome_child.dll/58B66B694ab6000/chrome_child.dll: 11.66 MiB/73.02 MiB    
Uploading   ...hrome_child.dll/58B6
command timed out: 1800 seconds without output, attempting to kill

I'm not really sure what made that take so long though. 73MB is not a particularly large file, and the subsequent chrome_child.dll.pd_ file was larger, and appears to have succeeded. Maybe just some external network issues, or some trouble on the cloud storage end. Probably not anything we can do about it at this point, other than keep an eye on it, and maybe have chrome-labs@ investigate if it continues.
►

Sign in to add a comment