[Janak Parekh]

Cause of Zune 30 leapyear problem ISOLATED! - Zune Boards

The problem occurs if days == 366 and IsLeapYear(year) is true.

Does Microsoft unittest this code?

--janak

[Janak Parekh]

Cause of Zune 30 leapyear problem ISOLATED! - Zune Boards

The problem occurs if days == 366 and IsLeapYear(year) is true.

Does Microsoft unittest this code?

--janak

[Rocco Augusto]

You want to know what annoys me the most about this situation? The Zune has a darn internal clock! Why can't we get that clock on the homescreen!?!?!?

I kid of course and my Zune is working again though my screen is still broken

[Jason Dunn]

Originally Posted by Rocco Augusto

Why can't we get that clock on the homescreen!?!?!?

You know that you can now, right? Just go into the options and turn it on.

[twinkyman90]

Originally Posted by Chris Gohlke

Confirmed, mine works fine this morning. Leap year testing is one of those obvious things you test for any time you have a date calculation, so it seems VERY sloppy for them to have missed it.

right. i'm sure you would have thought of this. C'mon people give the zune team a break. Nobody would have thought of this. Now they know to test for this sort of thing in the future. Like it's been said the 30's have only been out for a few years.

[David Tucker]

Yeah, I would have (or at the very least ensure that its in the test scripts) If I missed something like this on some of the systems I work on we could have delays which means money. I expect proffessionals to do their job correctly. Doctors can't afford to make 'little' mistakes. Lawyers can't. Not the good ones. Same rules.

[Janak Parekh]

Originally Posted by twinkyman90

right. i'm sure you would have thought of this. C'mon people give the zune team a break. Nobody would have thought of this. Now they know to test for this sort of thing in the future. Like it's been said the 30's have only been out for a few years.

Sorry, I agree with David on this one. Where I work, code like this would absolutely be extensively tested. Date handling in particular is an area traditionally rife with problems. If you look at the link I posted, it's an elementary infinite loop problem. Good unittesting practices emphasize testing loop and conditionals to make sure all code paths work.

I've heard MS is good on testing in general, so all I can guess is that this slipped through the cracks. But I don't think even Microsoft would excuse themselves on this one.

--janak

[Chris Gohlke]

Originally Posted by twinkyman90

right. i'm sure you would have thought of this. C'mon people give the zune team a break. Nobody would have thought of this. Now they know to test for this sort of thing in the future. Like it's been said the 30's have only been out for a few years.

Yes I would have. I can surely understand that someone not in the computer industry might not think it is obvious. But if you are at all involved in programming/testing, it is standard practice to test for leap years when you have any date related calculations.

[Rocco Augusto]

Originally Posted by Jason Dunn

You know that you can now, right? Just go into the options and turn it on.

Really? I pick the worst time ever to break my screen. Now I can't even utilize the one feature I wanted

[Ed Hansberry]

Seems the Toshiba Gigabeat had the same problem. http://www.engadget.com/2009/01/03/y...freescale-bug/

I wasn't aware the Zune was base, partially at least, on the PMC.

[Chris Gohlke]

And here is an article looking at the code block itself and provides an analysis showing exactly where the infinite loop occurs on the date check. http://www.toddhpoole.com/2009/01/02...s-zune-freeze/