SigComp torture test numbers misleading

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
Attempt to starts tests at test x but starts with a different test.

What version of the product are you using? On what operating system?
2.0.132.811

Please provide any additional information below.

Above each toture test definition tests[] of test_tortures.h is a comment 
indicating the absolute number of the tests.  New tests have been added and 
these numbers have not been aligned.

For example...
    {
        //*** 4**
        "A.1.5.(2)  LOAD and MULTILOAD",
        RFC4465_A_1_5__LOAD_and_MULTILOAD_2,
        58,
        {21, "MULTILOAD_OVERWRITTEN"},
        36,
        IS_STREAM_NO,
        XFAIL_YES,
        COMPARTMENT_ID
    }
    ,
    {
        //*** 4**
        "A.1.5.(3)  LOAD and MULTILOAD",
        RFC4465_A_1_5__LOAD_and_MULTILOAD_3,
        58,
        {21, "MULTILOAD_OVERWRITTEN"},
        36,
        IS_STREAM_NO,
        XFAIL_YES,
        COMPARTMENT_ID
    }

The comment with the absolute test number is useful for debug when startign 
with a specific test, for example...

#if RUN_TEST_ALL
        start = 73, end = sizeof(tests)/sizeof(tests[0]);
//      start = 0, end = sizeof(tests)/sizeof(tests[0]);
#else
        start = RUN_TEST_NO, end = RUN_TEST_NO + 1;
#endif

Original issue reported on code.google.com by alistair...@gmail.com on 4 Feb 2013 at 2:46

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 5 Feb 2013 at 4:54

• Changed state: Accepted
• Added labels: SigComp

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 6 Feb 2013 at 9:45

• Changed state: NextRelease

[GoogleCodeExporter]

Fixed by r814

Original comment by boss...@yahoo.fr on 6 Feb 2013 at 12:09

• Changed state: Fixed