342549 - AUS does not display nightly updates when it should after migration

Status: RESOLVED FIXED

(AUS Graveyard :: Systems, defect)

Description

[Michael Morgan [:morgamic]]

After the migration we were able to start staging again, and found that there were problems with nightly updates because of discrepancies in the build data and some assumptions on its layout in the XML code.

Paul and I have been working on a fix -- first we need to gain a better understanding of where the null *.txt snippets come from and when they are created.

Second, we needed to upate the XML code to be more robust by removing assumptions about the file structure.  I have already created a patch for this.

Comment 1

[Michael Morgan [:morgamic]]

Attachment: Patch to remove assumptions on second-to-last build and check for latest build properly.

Comment 2

[J. Paul Reed [:preed]]

Comment on attachment 226819 [details] [diff] [review]
Patch to remove assumptions on second-to-last build and check for latest build properly.

This seems to make sense.

r=preed.

Comment 3

[Michael Morgan [:morgamic]]

Comment on attachment 226819 [details] [diff] [review]
Patch to remove assumptions on second-to-last build and check for latest build properly.

Alright, so after more discussion and testing using the sanity script, the XML code was okay so we are going to back this patch out and rerun some more tests to verify that update XML output is correct after the last updates to the build data were run.

Comment 4

[Michael Morgan [:morgamic]]

After reverting back from the patch-that-should-not-have-ever-existed, the output looked more sane, and we've narrowed it down to a few specifics.  See preed's blog for more on that:
http://weblogs.mozillazine.org/preed/2006/06/1919_its_only_updates.html#more

The fix for bug 306864 ended up being correct, hence the pulling of this patch, which caused aus2-staging to advertise updates to the next build (instead of latest, which is the way it already was / should be).

Overall, we've had some much-needed discussion and achieved a relative understanding about how the update system works from end-to-end, so it was a net gain and should prevent future confusion with some effort towards documentation, which I will help with as much as I can.

The plan now is to wait fur successive builds to complete and reevaluate later this weekend or Monday.  We will update then.

Comment 5

[Michael Morgan [:morgamic]]

This particular problem is resolved -- over the weekend the builds were updated and now the information being offered is correct.