Closed Bug 344676 Opened 18 years ago Closed 18 years ago

AUS Partial Update System Partially Broken (Full update instead of binary partials)

Categories

(AUS Graveyard :: General, defect)

Product:
AUS Graveyard
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME
Milestone:
4.x (triaged)

People

(Reporter: jliebson, Assigned: morgamic)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060713 BonEcho/2.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060713 Thunderbird/2.0a1 - Build ID: 2006071304 A few minutes ago, with the Build Identifier shown above, TB notified me that there was an update available. I clicked on the button to download this install, which immediately informed me that TB was unable to verify the integrity of the partial update and would, therefore, download the complete update package. This is the third time that this has happened over the past four or five Thunderbird updates. This should not be happening, and does not happen with Bon Echo partial updates. Please see http://forums.mozillazine.org/viewtopic.php?t=437729 , starting with my entry in that thread, for other information about this problem. Reproducible: Sometimes Steps to Reproduce: 1. See "Details" 2. 3. Expected Results: Partial update should be successfully downloaded and installed instead of full update.
Confirming this because same thing happened with me past 3 nightlies. On another note: grrr why can't I change both product and component at the same time.
Status: UNCONFIRMED → NEW
Component: Installer → General
Ever confirmed: true
Product: Thunderbird → AUS
Summary: AUS Partial Update System Broken → AUS Partial Update System Partially Broken (Full update instead of binary partials)
Version: unspecified → 1.0
Assignee: mscott → morgamic
QA Contact: installer → general
Forgot to say that when I upgraded from Bon Echo Alpha 3 to beta 1 today, that I got the whole 6.8mb update file instead of the binary patch.
(In reply to comment #2) > Forgot to say that when I upgraded from Bon Echo Alpha 3 to beta 1 today, that > I got the whole 6.8mb update file instead of the binary patch. That's expected - there was no a3->b1 partial.
INVALID, per comment #3, plus I've since gotten the nightly partial for b1.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You guys misunderstood this bug because of comment 2. I thought that alpha 3 to b1 no partial was related to this bug. But as gavin said its not. But the bug still exists with the thunderbird nightlys...no binary partials from one day to the next, only the full update.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
There is an up to 10 minute window where AUS says there is an update and the partial actually being on the FTP server, which gives the behaviour of the initial report. (Strictly, this is what I have observed with Firefox but the update system is app agnostic and it shouldn't make a difference.) Now this is a pretty narrow time window to hit. Are you checking manually when you see the tinderbox finish the nightly ? You should allow at least 15 minutes for partial generation and files to propagate. If you are letting Thunderbird check, have you modifed the delay between checks (app.update.interval) ? I've checked the update information for the 20060725 --> 26 transition. It appears to be valid, the partial files are on the FTP server and the sizes and hashes are correct. Updating Windows 2006072504 WFM too.
Reply to comment #6: I wait until Bon Echo and Thunderbird notify me that there is an update available. In only one case over the past twelve days (since I started this butg report) has Bon Echo failed to deliver a partial update; in that same time, only once has TB delivered a partial update. All other TB updates have been full updates. This morning, for example, both Bon Echo and Thunderbird stated that updates were available, without my querying the system manually. BE's update was a partial, TB's a failed partial, followed by a full update. Yes, I've changed the app.update interval, which I have had set to 5000 in both Bon Echo and Thunderbird for perhaps several months now. Until recently, TB partial updating worked correctly with that setting--and Bon Echo continues to do so. Given the evidence of the difference between Bon Echo and Thunderbird updating, I remain unconvinced that there is not a problem with the TB AUS.
Ok, that's useful information. I'll try to figure out if Thunderbird has a much larger gap between AUS and FTP being up to date. The patch generator seems to semi-continously update the timestamps on the partials, so it's a bit of a pain. Do you have a regression date for this ? The 10th of July ?
From comment #8: "Do you have a regression date for this ? The 10th of July ?" No, sorry, I don't have a specific date. I suspect that it started a few weekends ago, when the computers were all being moved, at which time no partials were available for Bon Echo nor Thunderbird. It was after BE partials started working again, as I recall, that I noticed that TB partials were not working. There was some traffic about this on MozillaZine, mostly in the Bon Echo daily build threads, messages which helped explain what the problems were, and when users could expect them to be fixed; however--again--TB's problem(s) don't seem to have been taken care of, unlike those for BE.
Manual or Automatic notification of an update both produce same results. Manually I've checked at all hours of the day/night with the same result.
There are definite problems syncing the FTP staging server to ftp.mozilla.org. Today that means that the windows trunk partial-update is missing from ftp [1], so the partial would fail there. All the windows updates (branch & trunk) for the last 6 builds seem to be present at the moment. #bmo says that there is an issue with tinderboxes not publishing files with the right permissions, so that rsync barfs, and that the build engineers are going to fix this (cc'ing preed as a reminder). I'm not sure that can be the whole story, because the partials all come from the one box. They seem to get an updated timestamp every 5 minutes, which I don't recall remember noticing before. [1] http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2006-07-25-06-trunk/ has only: thunderbird-3.0a1.en-US.win32.complete.mar 25-Jul-2006 08:14 7.9M thunderbird-3.0a1.en-US.win32.installer.exe 25-Jul-2006 08:09 6.3M thunderbird-3.0a1.en-US.win32.zip 25-Jul-2006 08:11 8.6M and no thunderbird-3.0a1.en-US.win32.partial.2006072506-2006072606.mar 26-Jul-2006 15:55 448K
On 27July2006, I updated TB successfully with a partial update, based on an AUS notification. However, I don't know how long that popup had been on the screen, so don't know if the successful partial update was related to the timing problem mentioned in comment #6: "There is an up to 10 minute window where AUS says there is an update and the partial actually being on the FTP server, which gives the behaviour of the initial report." A few minutes ago, I was at the computer when I got another AUS notification of a TB update, so I immediately asked for it to be downloaded. I got another partial update,this time to Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060728 Thunderbird/2.0a1 - Build ID: 2006072803. Based on the results of the last two updates, it appears that the problem *may* have been solved. (I'm not quite willing to close this bug after only two successful updates--perhaps if I wait for the next two hundred...). Nick Thomas, I don't know who you are, but it certainly appears that you know what you are talking about in this case and that you have been quite helpful.
No updates on Thunderbird since this one: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060726 Thunderbird/2.0a1 ID:2006072610 I've tried off and on since. Firefox also still not working on 1.5.0 branch.
(In reply to comment #13) > No updates on Thunderbird since this one: > Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060726 > Thunderbird/2.0a1 ID:2006072610 > > I've tried off and on since. Firefox also still not working on 1.5.0 branch. Thunderbird nightlies default to the "beta" channel at the moment, because that's what is needed for the RC for 2.0a1. If you manually install a build from 20060526 or later then you'll not find any updates because of this. To fix, change the channel back to "nightly", see last paragraph at http://kb.mozillazine.org/Software_update#Update_channels (Update Channel Changer needs Mr Tech or Nightly Tester Tools to install in 2.0 and trunk builds)
Unfortunately, AUS did not provide the partial update for Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060729 Thunderbird/2.0a1 - Build ID: 2006072906, only a complete one. I guess the system has not been entirely fixed as of yet.
Using the Win32 branch nightly (version 2 alpha 1 (20060728)), I did a manual check for updates, at 6:57 PM EST. I received a partial update of 438 KB and updated without issue to: version 2 alpha 1 (20060729)
In reply to Comment #16: Notice the time difference between #16 and my #15. I tried the download as soon as the notice of an update showed up, and, as stated, the partial update failed. As you were able to get a partial, I have to suspect that at least part of the problem is what is discussed in Comment #6. However, keep in mind that yesterday, I was successful in getting a partial update under the same conditions as today's failure; see my #12.
I've been keeping an eye on the Firefox & Thunderbird partials on ftp.m.o, and my unscientific observations are that it's only Thunderbird for Windows on the trunk and Mozilla1.8 branch that exhibit this problem. It also comes right eventually, usually by the next day when the partial is useless, so it's hard to track what's happening.
In reply to Comment #18: Yes, it is still problematic with TB branch/Windows. Yesterday and today, I once again got failed partial updates. Yesterday, I was at the computer when the pop-up appeared of a new update being available, so I tried it immediately, and it failed. Today, I was not in the room when the announcement appeared, and don't know how long it had been visible; at any rate, once again the partial update failed. I've not updated Bon Echo for several days, due to Bug #346308, which I posted 28July2006; however, as I've reported, I almost never saw any partial-update problems with Bon Echo before that date.
My comments were really aimed at which platforms were affected rather than which app, as we have didn't really have any info for non-windows ones. In the time between comment #18 and now the Windows branch partial has appeared on ftp.m.o.
Is this fixed for you? Tb 2.0a1 partial update has been wfm for about 3 weeks (both Win and Lin)
As the originator of this report, and given that Thunderbird has been properly updating using partial updates for perhaps two weeks now, I'm going to mark this as Fixed. (I'm sure some nit picker will come along and change this to "Worksforme", on the meaningless grounds that nothing was actually fixed; no matter, the update system works.)
Status: REOPENED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → FIXED
In this case that nit-picker is going to be me. FIXED really is reserved for cases where someone makes a positive identifiable change, and WORKSFORME covers all those odd occurances where people have not figured out what was broken but it has gone away in the meantime. Anyway, good news that it's working. Please reopen if you start having trouble again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.