CR 6860309 - solaris timing issue on thread startup

Gary Adams gary.adams at
Tue Nov 15 21:38:28 UTC 2011

Where can we find the definition of the tag contents?
Whichever way this discussion goes, we should
update that documentation with the conclusions.

On 11/15/11 4:29 PM, David Holmes wrote:
> Alan,
> On 15/11/2011 11:26 PM, Alan Bateman wrote:
>> On 15/11/2011 00:56, David Holmes wrote:
>>> :
>>> 25 * @bug 4820217 6860309
>>> As per other emails and still waiting from confirmation from Alan. I
>>> don't think the @bug should be updated for any of these test fixes.
>> The @bug tag is intended to list the bug numbers of bugs that are useful
>> when you have a test failure and sometimes there can be really useful
>> information in a bug that turns out to be a test bug. I'm not aware of
>> any rule that says that the bug numbers shouldn't include bugs that were
>> test only bugs but it's almost always bug numbers of bugs that caused
>> the test to be extended to cover additional scenarios. For the tests
>> being discussed here then I think we should just use our best judgment.
>> Worse case it's easy to dig into the history with hg.
> That was somewhat non-committal :) To me @bug says "these are the bugs 
> that this test is checking the fix for" hence not applicable in any of 
> the recent timing/race test fixes.
> David
>> -Alan.

More information about the core-libs-dev mailing list