Poster: Llamadruid at 8/23/2005 10:49:29 AM PDT
Subject: Errors #132 and #134 ETA? |
| |
How long will it be till these are fixed? Any ETA? Or already fixed?
Adults are just as capable of being offensive -Eyonix
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-realm-test&t=60487&p=#post60487 |
| |
Poster: tigerclaw at 8/24/2005 4:53:40 PM PDT
Subject: Re: Errors #132 and #134 fix ETA?! |
| |
Q u o t e:
1.7 will probably go live next week, crashes intact.
< muffled noise resembling an amused chuckle >
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-realm-test&t=60487&p=#post61660 |
Poster: tigerclaw at 8/24/2005 5:37:30 PM PDT
Subject: Re: Errors #132 and #134 fix ETA?! |
| |
All-
we don't charge anyone to play on PTR - it's totally optional. The logical thing to do, if you are not happy with the stability of the PTR build, is to simply set it aside for a while and play on Live instead. A new rev of PTR will arrive when it is ready and all the fixes have been verified solid. We are making progress.
The chuckle was simply to indicate that "no, crash bugs of the frequency seen in 4579 won't get onto Live".
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-realm-test&t=60487&p=#post61697 |
Poster: tigerclaw at 8/24/2005 7:29:50 PM PDT
Subject: Re: Errors #132 and #134 fix ETA?! |
| |
I can see that there will always be people who can find the glass to be half full, and those that will find it to be half empty.
If you're not happy with the current PTR build, set it aside. We're going to provide a new build as soon as is possible.
One of the strengths of PTR is it lets us reproduce load/crowd conditions closer to real live servers, without comitting to a rollout on real live servers. It is difficult for us to reproduce the conditions of hundreds of players on a realm without help from the PTR people.
Bugs like the crashes in 4579 can become more common as crowding level goes up - a crash that might have happened a single time in internal QA with no obvious reproducible steps, can blossom into something bigger as the load goes up. Well, it did.
So on the one hand there is inconvenience and frustration - "how can I test the content with this crash bug?" but on the other hand there is success, in exposing and fixing this bug on PTR before it got to Live. Half empty or half full?
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-realm-test&t=60487&p=#post61769 |
Poster: tigerclaw at 8/24/2005 7:39:34 PM PDT
Subject: Re: Errors #132 and #134 fix ETA?! |
| |
Q u o t e:
How about you put the version of WoW that the devs were using for internal testing of Arathi Basin on the PTR? Because it's obvious that these errors did NOT occur on the developer's version for internal testing, as a BG couldn't be designed and balanced if you couldn't test it internally for more than 2 minutes.
You're saying it doesn't cost anything to play on the PTR: That is incorrect. I have to pay $15 a month to play on the PTR, and I highly doubt you let non-subscribers get on the PTR to play around.
PTR was added and no change in game cost resulted. If PTR were to be removed, there would also be no change in cost. PTR is free and optional for subscribers and we appreciate the feedback (both written and automated) that all the active PTR volunteers are generating for us.
Any time there is a bug that is sensitive to crowd level and loading (sheer number of active players in the world), it will be easier to spot and reproduce on PTR than it is on internal test realms. But PTR shouldn't be considered as an equivalent to Live.
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-realm-test&t=60487&p=#post61778 |
Poster: tigerclaw at 8/25/2005 9:11:00 AM PDT
Subject: Re: Errors #132 and #134 fix ETA?! |
| |
Q u o t e:
/hail fellow garonian. Valid points, but still. I don't think how the stress of a larger field of players can affect the various issues of 132/134. My limited and ignorant view is that it could just be game code itself that was botched but compiled.
In the specific case of the 132/134 errors in 4579, there was a plain software bug. I've seen evidence to indicate that the frequency/probability of the bug occurring to any user was proportional to the number of other users in the vicinity of the user.
Coders in the audience can chew on the words "array bounds violation, memory trasher" and see where I'm coming from (and probably also reminisce about the last one they had to hunt down and how long it took).
Not all coding errors result in 100% reproducible errors under all loading conditions. Some do; this one didn't. It might have happened in the QA lab once or twice before release and we just didn't have good steps to reproduce it; PTR made it possible to find it and fix it.
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-realm-test&t=60487&p=#post62081 |
Poster: tigerclaw at 8/25/2005 11:22:09 AM PDT
Subject: Re: Errors #132 and #134 fix ETA?! |
| |
Q u o t e:
Or... it could be fixed internally and going through internal tests and NOT ON THE TEST REALMS YET...
X takes the square
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-realm-test&t=60487&p=#post62154 |
Poster: tigerclaw at 8/25/2005 12:50:35 PM PDT
Subject: Re: Errors #132 and #134 fix ETA?! |
| |
Q u o t e:
I dont mean to sound 'half empty' but, how do you know if you have really fixed the bug in internal testing if you havent put it under PTR conditions yet?
Very fair question, and obviously 100% certainty only comes with larger scale public testing. The original PTR feedback gave us some insights on how to construct an in-house test that would trigger the bug, and the accumulated crash reports helped us zero in on which data structures were being damaged. With that information in hand we were able to devise a test case and catch the offending code red-handed (though this did take a while). Subsequently the developers and QA have done more exercising of the test case to verify that the fix was effective.
edit: and you will get to test the new build with that fix in, as soon as it is ready for PTR release. We can't just hit compile and then ship it, there is a release process with a lot of steps, multiple platforms, multiple locales.[ post edited by tigerclaw ]
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-realm-test&t=60487&p=#post62247 |
