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

Issue 629245 link

Starred by 2 users
Status: Duplicate
Owner:
█ dimu@chromium.org
Last visit > 30 days ago
Closed: Aug 2016
Cc:
mmoss@chromium.org
ihf@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Making symbol upload more robust for Flash

Project Member Reported by lafo...@chromium.org, Jul 18 2016 
There have been a number of instances where Flash symbols haven't been properly uploaded, in the current Flash staging flow.

We should get to the bottom of what's failing (logging/ emails) and figure out the right next steps to bolster the system (e.g. retries, ACLs, etc...).

Comment 1 by dimu@google.com, Jul 18 2016 

22.0.0.209 was uploaded manually by running the bash script as the machine didn't fetch TOWNSEND+1 folder as the latest ftp folder (I haven't got time to look at the root reason as we are deprecating the bash script, as it is hard to debug, returns false success when scripts break early with errors, and still uses svn). It's possible that the symbol upload error was skipped during the initial run.

I wrote a python script https://chrome-internal.googlesource.com/chrome/tools/buildspec/+/master/scripts/flash_updater.py for uploading flash symbols now, it has much better error alerting.

Comment 2 by lafo...@chromium.org, Aug 19 2016 

Should we just call this fixed?

Comment 3 by dimu@google.com, Aug 19 2016

Mergedinto: 609901
Status: Duplicate (was: Assigned)
yep it fixed as we are deprecated the bash and switch to the python script now.

Comment 4 by lafo...@chromium.org, Aug 19 2016 

Nice, thank you.
►

Sign in to add a comment