* [LTP] [FIX PATCHES] open_posix_execute.sh
@ 2009-07-20 13:05 naresh kamboju
2009-07-28 6:50 ` naresh kamboju
0 siblings, 1 reply; 10+ messages in thread
From: naresh kamboju @ 2009-07-20 13:05 UTC (permalink / raw)
To: ltp-list; +Cc: Brandon Philips
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
Hi,
As per the execute.sh script file there is time limit of two minutes
for each test case execution if it takes more time it will be reported
as HUNG.
shm_open/23-1.c test case under posix test suite which executes more
than two minitutes so test case reported as HUNG.
I have changed time limit from 120 to 300 sec. that is nothing but two
minutes to five minutes. In low end machines this test case taking 4
min to complete execution.
Now test cases reported as PASS
I have attached patch and below.
Please review the same.
Best regards,
Naresh Kamboju
/*****************************************************/
Before Patch:
conformance/interfaces/shm_open/23-1.test:execution:HUNG
After Patch:
conformance/interfaces/shm_open/23-1.test:execution:PASS
/*****************************************************/
Signed-off-by: Naresh Kamboju < naresh.kernel@gmail.com >
diff -Naurb a/testcases/open_posix_testsuite/execute.sh
b/testcases/open_posix_testsuite/execute.sh
--- a/testcases/open_posix_testsuite/execute.sh 2007-07-26
17:32:11.000000000 +0530
+++ b/testcases/open_posix_testsuite/execute.sh 2009-07-20
17:53:15.000000000 +0530
@@ -163,8 +163,8 @@
declare -i SEGV=0
declare -i OTH=0
-# Maximum Two minutes waiting time period to execute a test. If it
exceeds, the test case will go into the 'HUNG' category.
-TIMEOUT_VAL=120
+# Maximum five minutes waiting time period to execute a test. If it
exceeds, the test case will go into the 'HUNG' category.
+TIMEOUT_VAL=300
# if gcc available then remove the below line comment else put the t0
in posixtestsuite directory.
#gcc -o t0 t0.c
[-- Attachment #2: ltp-posix-execute.patch --]
[-- Type: application/octet-stream, Size: 731 bytes --]
diff -Naurb a/testcases/open_posix_testsuite/execute.sh b/testcases/open_posix_testsuite/execute.sh
--- a/testcases/open_posix_testsuite/execute.sh 2007-07-26 17:32:11.000000000 +0530
+++ b/testcases/open_posix_testsuite/execute.sh 2009-07-20 17:53:15.000000000 +0530
@@ -163,8 +163,8 @@
declare -i SEGV=0
declare -i OTH=0
-# Maximum Two minutes waiting time period to execute a test. If it exceeds, the test case will go into the 'HUNG' category.
-TIMEOUT_VAL=120
+# Maximum five minutes waiting time period to execute a test. If it exceeds, the test case will go into the 'HUNG' category.
+TIMEOUT_VAL=300
# if gcc available then remove the below line comment else put the t0 in posixtestsuite directory.
#gcc -o t0 t0.c
[-- Attachment #3: Type: text/plain, Size: 389 bytes --]
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
[-- Attachment #4: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [LTP] [FIX PATCHES] open_posix_execute.sh
2009-07-20 13:05 [LTP] [FIX PATCHES] open_posix_execute.sh naresh kamboju
@ 2009-07-28 6:50 ` naresh kamboju
2009-07-30 3:35 ` Garrett Cooper
0 siblings, 1 reply; 10+ messages in thread
From: naresh kamboju @ 2009-07-28 6:50 UTC (permalink / raw)
To: ltp-list; +Cc: Brandon Philips
Hi,
Hope you have reviewed below patch.
If you any issue please let me know.
Subrata/ Garrett,
Please review, if you feel okay.
commit.
Best regards,
Naresh Kamboju
On Mon, Jul 20, 2009 at 6:35 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
> Hi,
>
> As per the execute.sh script file there is time limit of two minutes
> for each test case execution if it takes more time it will be reported
> as HUNG.
>
> shm_open/23-1.c test case under posix test suite which executes more
> than two minitutes so test case reported as HUNG.
>
> I have changed time limit from 120 to 300 sec. that is nothing but two
> minutes to five minutes. In low end machines this test case taking 4
> min to complete execution.
>
> Now test cases reported as PASS
>
> I have attached patch and below.
> Please review the same.
>
>
> Best regards,
> Naresh Kamboju
>
>
> /*****************************************************/
> Before Patch:
>
> conformance/interfaces/shm_open/23-1.test:execution:HUNG
>
>
> After Patch:
>
> conformance/interfaces/shm_open/23-1.test:execution:PASS
> /*****************************************************/
>
>
> Signed-off-by: Naresh Kamboju < naresh.kernel@gmail.com >
>
> diff -Naurb a/testcases/open_posix_testsuite/execute.sh
> b/testcases/open_posix_testsuite/execute.sh
> --- a/testcases/open_posix_testsuite/execute.sh 2007-07-26
> 17:32:11.000000000 +0530
> +++ b/testcases/open_posix_testsuite/execute.sh 2009-07-20
> 17:53:15.000000000 +0530
> @@ -163,8 +163,8 @@
> declare -i SEGV=0
> declare -i OTH=0
>
> -# Maximum Two minutes waiting time period to execute a test. If it
> exceeds, the test case will go into the 'HUNG' category.
> -TIMEOUT_VAL=120
> +# Maximum five minutes waiting time period to execute a test. If it
> exceeds, the test case will go into the 'HUNG' category.
> +TIMEOUT_VAL=300
>
> # if gcc available then remove the below line comment else put the t0
> in posixtestsuite directory.
> #gcc -o t0 t0.c
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [LTP] [FIX PATCHES] open_posix_execute.sh
2009-07-28 6:50 ` naresh kamboju
@ 2009-07-30 3:35 ` Garrett Cooper
2009-07-30 6:10 ` naresh kamboju
2009-07-30 10:25 ` naresh kamboju
0 siblings, 2 replies; 10+ messages in thread
From: Garrett Cooper @ 2009-07-30 3:35 UTC (permalink / raw)
To: naresh kamboju; +Cc: ltp-list, Brandon Philips
On Mon, Jul 27, 2009 at 11:50 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
> Hi,
>
> Hope you have reviewed below patch.
> If you any issue please let me know.
>
> Subrata/ Garrett,
> Please review, if you feel okay.
> commit.
>
> Best regards,
> Naresh Kamboju
>
>
> On Mon, Jul 20, 2009 at 6:35 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>> Hi,
>>
>> As per the execute.sh script file there is time limit of two minutes
>> for each test case execution if it takes more time it will be reported
>> as HUNG.
>>
>> shm_open/23-1.c test case under posix test suite which executes more
>> than two minitutes so test case reported as HUNG.
>>
>> I have changed time limit from 120 to 300 sec. that is nothing but two
>> minutes to five minutes. In low end machines this test case taking 4
>> min to complete execution.
>>
>> Now test cases reported as PASS
>>
>> I have attached patch and below.
>> Please review the same.
Naresh,
I looked at the testcase, and I think I can see where your concern
stems from, as this is a stress test, more than a functional test
(1000 child PIDs looping 1000 times each... that's a fair number of
cycles :)...). What I'd be really be interested in is the number of
cycles being generated (msec is `randomly' generated -- see line 75).
However, when I ran the testcase on my machine -- it took less than 10
seconds (!):
I do have more RAM and all, and I have a fairly recent Intel
processor (posted below), but what do you have that's so sluggish by
chance?
I wonder why it failed though *shrugs*.
Thanks,
-Garrett
gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ gcc
-Itestcases/open_posix_testsuite/include/
testcases/open_posix_testsuite/conformance/interfaces/shm_open/23-1.c
gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ time ./a.out
create_cnt: 890
Test FAILED
real 0m10.947s
user 0m4.074s
sys 0m9.189s
gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ uname -a
Linux orangebox 2.6.29-gentoo-r5 #2 SMP PREEMPT Sun Jun 14 01:11:32
PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
GenuineIntel GNU/Linux
gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ cat
/proc/meminfo /proc/cpuinfo
MemTotal: 8197172 kB
MemFree: 180264 kB
Buffers: 227552 kB
Cached: 6427308 kB
SwapCached: 5744 kB
Active: 914940 kB
Inactive: 6820352 kB
Active(anon): 310092 kB
Inactive(anon): 776660 kB
Active(file): 604848 kB
Inactive(file): 6043692 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 6498284 kB
SwapFree: 6472696 kB
Dirty: 484 kB
Writeback: 0 kB
AnonPages: 1075824 kB
Mapped: 56784 kB
Slab: 192872 kB
SReclaimable: 162736 kB
SUnreclaim: 30136 kB
PageTables: 10908 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 10596868 kB
Committed_AS: 1617720 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 334552 kB
VmallocChunk: 34359384571 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 8119808 kB
DirectMap2M: 268288 kB
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
stepping : 10
cpu MHz : 2664.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5343.38
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
stepping : 10
cpu MHz : 2664.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5343.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
stepping : 10
cpu MHz : 2664.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5343.03
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
stepping : 10
cpu MHz : 2664.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5343.03
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [LTP] [FIX PATCHES] open_posix_execute.sh
2009-07-30 3:35 ` Garrett Cooper
@ 2009-07-30 6:10 ` naresh kamboju
2009-07-30 10:25 ` naresh kamboju
1 sibling, 0 replies; 10+ messages in thread
From: naresh kamboju @ 2009-07-30 6:10 UTC (permalink / raw)
To: Garrett Cooper; +Cc: ltp-list, Brandon Philips
On Thu, Jul 30, 2009 at 9:05 AM, Garrett Cooper<yanegomi@gmail.com> wrote:
> On Mon, Jul 27, 2009 at 11:50 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>> Hi,
>>
>> Hope you have reviewed below patch.
>> If you any issue please let me know.
>>
>> Subrata/ Garrett,
>> Please review, if you feel okay.
>> commit.
>>
>> Best regards,
>> Naresh Kamboju
>>
>>
>> On Mon, Jul 20, 2009 at 6:35 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>>> Hi,
>>>
>>> As per the execute.sh script file there is time limit of two minutes
>>> for each test case execution if it takes more time it will be reported
>>> as HUNG.
>>>
>>> shm_open/23-1.c test case under posix test suite which executes more
>>> than two minitutes so test case reported as HUNG.
>>>
>>> I have changed time limit from 120 to 300 sec. that is nothing but two
>>> minutes to five minutes. In low end machines this test case taking 4
>>> min to complete execution.
>>>
>>> Now test cases reported as PASS
>>>
>>> I have attached patch and below.
>>> Please review the same.
>
> Naresh,
> I looked at the testcase, and I think I can see where your concern
> stems from, as this is a stress test, more than a functional test
> (1000 child PIDs looping 1000 times each... that's a fair number of
> cycles :)...). What I'd be really be interested in is the number of
> cycles being generated (msec is `randomly' generated -- see line 75).
> However, when I ran the testcase on my machine -- it took less than 10
> seconds (!):
>
>
> I do have more RAM and all, and I have a fairly recent Intel
> processor (posted below), but what do you have that's so sluggish by
> chance?
Hi Garrett,
Your comments are absolutely correct.
> I wonder why it failed though *shrugs*.
This test case is passed on high end machines with 128 MB and high RAM.
When you execute this test case on 32/16 MB RAM Embedded Board this
test case reports has Hung. because it is taking more than 3 min.
To resolve this issue I made this patch.
This patch is a Max limit of test cases execution time.
If test case exceeds given time then test case will report as HUNG.
I think there is no harm to apply this patch.
It is not going to effect performance of test and the rest of the test cases.
Best regards,
Naresh Kamboju
> Thanks,
> -Garrett
>
> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ gcc
> -Itestcases/open_posix_testsuite/include/
> testcases/open_posix_testsuite/conformance/interfaces/shm_open/23-1.c
> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ time ./a.out
> create_cnt: 890
> Test FAILED
>
> real 0m10.947s
> user 0m4.074s
> sys 0m9.189s
>
> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ uname -a
> Linux orangebox 2.6.29-gentoo-r5 #2 SMP PREEMPT Sun Jun 14 01:11:32
> PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> GenuineIntel GNU/Linux
> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ cat
> /proc/meminfo /proc/cpuinfo
> MemTotal: 8197172 kB
> MemFree: 180264 kB
> Buffers: 227552 kB
> Cached: 6427308 kB
> SwapCached: 5744 kB
> Active: 914940 kB
> Inactive: 6820352 kB
> Active(anon): 310092 kB
> Inactive(anon): 776660 kB
> Active(file): 604848 kB
> Inactive(file): 6043692 kB
> Unevictable: 0 kB
> Mlocked: 0 kB
> SwapTotal: 6498284 kB
> SwapFree: 6472696 kB
> Dirty: 484 kB
> Writeback: 0 kB
> AnonPages: 1075824 kB
> Mapped: 56784 kB
> Slab: 192872 kB
> SReclaimable: 162736 kB
> SUnreclaim: 30136 kB
> PageTables: 10908 kB
> NFS_Unstable: 0 kB
> Bounce: 0 kB
> WritebackTmp: 0 kB
> CommitLimit: 10596868 kB
> Committed_AS: 1617720 kB
> VmallocTotal: 34359738367 kB
> VmallocUsed: 334552 kB
> VmallocChunk: 34359384571 kB
> HugePages_Total: 0
> HugePages_Free: 0
> HugePages_Rsvd: 0
> HugePages_Surp: 0
> Hugepagesize: 2048 kB
> DirectMap4k: 8119808 kB
> DirectMap2M: 268288 kB
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> stepping : 10
> cpu MHz : 2664.000
> cache size : 3072 KB
> physical id : 0
> siblings : 4
> core id : 0
> cpu cores : 4
> apicid : 0
> initial apicid : 0
> fpu : yes
> fpu_exception : yes
> cpuid level : 13
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5343.38
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> stepping : 10
> cpu MHz : 2664.000
> cache size : 3072 KB
> physical id : 0
> siblings : 4
> core id : 1
> cpu cores : 4
> apicid : 1
> initial apicid : 1
> fpu : yes
> fpu_exception : yes
> cpuid level : 13
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5343.00
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 2
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> stepping : 10
> cpu MHz : 2664.000
> cache size : 3072 KB
> physical id : 0
> siblings : 4
> core id : 2
> cpu cores : 4
> apicid : 2
> initial apicid : 2
> fpu : yes
> fpu_exception : yes
> cpuid level : 13
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5343.03
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 3
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> stepping : 10
> cpu MHz : 2664.000
> cache size : 3072 KB
> physical id : 0
> siblings : 4
> core id : 3
> cpu cores : 4
> apicid : 3
> initial apicid : 3
> fpu : yes
> fpu_exception : yes
> cpuid level : 13
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5343.03
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [LTP] [FIX PATCHES] open_posix_execute.sh
2009-07-30 3:35 ` Garrett Cooper
2009-07-30 6:10 ` naresh kamboju
@ 2009-07-30 10:25 ` naresh kamboju
2009-07-30 18:22 ` Garrett Cooper
2009-07-30 18:30 ` Subrata Modak
1 sibling, 2 replies; 10+ messages in thread
From: naresh kamboju @ 2009-07-30 10:25 UTC (permalink / raw)
To: Garrett Cooper; +Cc: ltp-list, Brandon Philips
On Thu, Jul 30, 2009 at 9:05 AM, Garrett Cooper<yanegomi@gmail.com> wrote:
> On Mon, Jul 27, 2009 at 11:50 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>> Hi,
>>
>> Hope you have reviewed below patch.
>> If you any issue please let me know.
>>
>> Subrata/ Garrett,
>> Please review, if you feel okay.
>> commit.
>>
>> Best regards,
>> Naresh Kamboju
>>
>>
>> On Mon, Jul 20, 2009 at 6:35 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>>> Hi,
>>>
>>> As per the execute.sh script file there is time limit of two minutes
>>> for each test case execution if it takes more time it will be reported
>>> as HUNG.
>>>
>>> shm_open/23-1.c test case under posix test suite which executes more
>>> than two minitutes so test case reported as HUNG.
>>>
>>> I have changed time limit from 120 to 300 sec. that is nothing but two
>>> minutes to five minutes. In low end machines this test case taking 4
>>> min to complete execution.
>>>
>>> Now test cases reported as PASS
>>>
>>> I have attached patch and below.
>>> Please review the same.
>
> Naresh,
> I looked at the testcase, and I think I can see where your concern
> stems from, as this is a stress test, more than a functional test
> (1000 child PIDs looping 1000 times each... that's a fair number of
> cycles :)...). What I'd be really be interested in is the number of
> cycles being generated (msec is `randomly' generated -- see line 75).
> However, when I ran the testcase on my machine -- it took less than 10
> seconds (!):
>
>
> I do have more RAM and all, and I have a fairly recent Intel
> processor (posted below), but what do you have that's so sluggish by
> chance?
Hi Garrett,
> I wonder why it failed though *shrugs*.
Oops. I forgot to say some points.
> Thanks,
> -Garrett
>
> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ gcc
> -Itestcases/open_posix_testsuite/include/
> testcases/open_posix_testsuite/conformance/interfaces/shm_open/23-1.c
> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ time ./a.out
> create_cnt: 890
> Test FAILED
>
> real 0m10.947s
> user 0m4.074s
> sys 0m9.189s
Test cases will create shm files under /dev/shm/shm_XXX
Before executing this test case mount /dev/shm as tmpfs
1. Create directory
#mkdir /dev/shm
2. Add below line in /etc/fstab
tmpfs /dev/shm tmpfs defaults 0 0
3. mount
#mount –a
Or
# mount –t tmpfs /dev/shm
#mount
/dev/sda2 on / type ext3 (rw)
/dev/sda3 on /home type ext3 (rw)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
4. go to test case location
#cd ~/ltp/testcases/open_posix_testsuite/conformance/interfaces/shm_open
# time ./23-1.test
create_cnt: 1000
real 3m34.111s
user 0m51.520s
sys 1m54.370s
Best regards,
Naresh Kamboju
>
> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ uname -a
> Linux orangebox 2.6.29-gentoo-r5 #2 SMP PREEMPT Sun Jun 14 01:11:32
> PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> GenuineIntel GNU/Linux
> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ cat
> /proc/meminfo /proc/cpuinfo
> MemTotal: 8197172 kB
> MemFree: 180264 kB
> Buffers: 227552 kB
> Cached: 6427308 kB
> SwapCached: 5744 kB
> Active: 914940 kB
> Inactive: 6820352 kB
> Active(anon): 310092 kB
> Inactive(anon): 776660 kB
> Active(file): 604848 kB
> Inactive(file): 6043692 kB
> Unevictable: 0 kB
> Mlocked: 0 kB
> SwapTotal: 6498284 kB
> SwapFree: 6472696 kB
> Dirty: 484 kB
> Writeback: 0 kB
> AnonPages: 1075824 kB
> Mapped: 56784 kB
> Slab: 192872 kB
> SReclaimable: 162736 kB
> SUnreclaim: 30136 kB
> PageTables: 10908 kB
> NFS_Unstable: 0 kB
> Bounce: 0 kB
> WritebackTmp: 0 kB
> CommitLimit: 10596868 kB
> Committed_AS: 1617720 kB
> VmallocTotal: 34359738367 kB
> VmallocUsed: 334552 kB
> VmallocChunk: 34359384571 kB
> HugePages_Total: 0
> HugePages_Free: 0
> HugePages_Rsvd: 0
> HugePages_Surp: 0
> Hugepagesize: 2048 kB
> DirectMap4k: 8119808 kB
> DirectMap2M: 268288 kB
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> stepping : 10
> cpu MHz : 2664.000
> cache size : 3072 KB
> physical id : 0
> siblings : 4
> core id : 0
> cpu cores : 4
> apicid : 0
> initial apicid : 0
> fpu : yes
> fpu_exception : yes
> cpuid level : 13
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5343.38
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> stepping : 10
> cpu MHz : 2664.000
> cache size : 3072 KB
> physical id : 0
> siblings : 4
> core id : 1
> cpu cores : 4
> apicid : 1
> initial apicid : 1
> fpu : yes
> fpu_exception : yes
> cpuid level : 13
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5343.00
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 2
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> stepping : 10
> cpu MHz : 2664.000
> cache size : 3072 KB
> physical id : 0
> siblings : 4
> core id : 2
> cpu cores : 4
> apicid : 2
> initial apicid : 2
> fpu : yes
> fpu_exception : yes
> cpuid level : 13
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5343.03
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 3
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> stepping : 10
> cpu MHz : 2664.000
> cache size : 3072 KB
> physical id : 0
> siblings : 4
> core id : 3
> cpu cores : 4
> apicid : 3
> initial apicid : 3
> fpu : yes
> fpu_exception : yes
> cpuid level : 13
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5343.03
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [LTP] [FIX PATCHES] open_posix_execute.sh
2009-07-30 10:25 ` naresh kamboju
@ 2009-07-30 18:22 ` Garrett Cooper
2009-08-03 15:49 ` naresh kamboju
2009-07-30 18:30 ` Subrata Modak
1 sibling, 1 reply; 10+ messages in thread
From: Garrett Cooper @ 2009-07-30 18:22 UTC (permalink / raw)
To: naresh kamboju; +Cc: ltp-list, Brandon Philips
On Thu, Jul 30, 2009 at 3:25 AM, naresh kamboju<naresh.kernel@gmail.com> wrote:
> On Thu, Jul 30, 2009 at 9:05 AM, Garrett Cooper<yanegomi@gmail.com> wrote:
>> On Mon, Jul 27, 2009 at 11:50 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>>> Hi,
>>>
>>> Hope you have reviewed below patch.
>>> If you any issue please let me know.
>>>
>>> Subrata/ Garrett,
>>> Please review, if you feel okay.
>>> commit.
>>>
>>> Best regards,
>>> Naresh Kamboju
>>>
>>>
>>> On Mon, Jul 20, 2009 at 6:35 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> As per the execute.sh script file there is time limit of two minutes
>>>> for each test case execution if it takes more time it will be reported
>>>> as HUNG.
>>>>
>>>> shm_open/23-1.c test case under posix test suite which executes more
>>>> than two minitutes so test case reported as HUNG.
>>>>
>>>> I have changed time limit from 120 to 300 sec. that is nothing but two
>>>> minutes to five minutes. In low end machines this test case taking 4
>>>> min to complete execution.
>>>>
>>>> Now test cases reported as PASS
>>>>
>>>> I have attached patch and below.
>>>> Please review the same.
>>
>> Naresh,
>> I looked at the testcase, and I think I can see where your concern
>> stems from, as this is a stress test, more than a functional test
>> (1000 child PIDs looping 1000 times each... that's a fair number of
>> cycles :)...). What I'd be really be interested in is the number of
>> cycles being generated (msec is `randomly' generated -- see line 75).
>> However, when I ran the testcase on my machine -- it took less than 10
>> seconds (!):
>>
>>
>> I do have more RAM and all, and I have a fairly recent Intel
>> processor (posted below), but what do you have that's so sluggish by
>> chance?
> Hi Garrett,
>
>
>> I wonder why it failed though *shrugs*.
> Oops. I forgot to say some points.
>
>> Thanks,
>> -Garrett
>>
>> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ gcc
>> -Itestcases/open_posix_testsuite/include/
>> testcases/open_posix_testsuite/conformance/interfaces/shm_open/23-1.c
>> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ time ./a.out
>> create_cnt: 890
>> Test FAILED
>>
>> real 0m10.947s
>> user 0m4.074s
>> sys 0m9.189s
>
>
> Test cases will create shm files under /dev/shm/shm_XXX
> Before executing this test case mount /dev/shm as tmpfs
>
> 1. Create directory
>
> #mkdir /dev/shm
Already done with fstab in Gentoo Linux.
> 2. Add below line in /etc/fstab
>
> tmpfs /dev/shm tmpfs defaults 0 0
(!) Uhhhhhhhhh.... this stuff should only be done if required.
> 3. mount
> #mount –a
> Or
> # mount –t tmpfs /dev/shm
> #mount
> /dev/sda2 on / type ext3 (rw)
> /dev/sda3 on /home type ext3 (rw)
> /dev/sda1 on /boot type ext3 (rw)
> tmpfs on /dev/shm type tmpfs (rw)
>
>
> 4. go to test case location
>
> #cd ~/ltp/testcases/open_posix_testsuite/conformance/interfaces/shm_open
>
> # time ./23-1.test
> create_cnt: 1000
>
> real 3m34.111s
> user 0m51.520s
> sys 1m54.370s
4. may or may not have been why it was failing *shrug*. I'll have to
run it as designed.
-Garrett
>> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ uname -a
>> Linux orangebox 2.6.29-gentoo-r5 #2 SMP PREEMPT Sun Jun 14 01:11:32
>> PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>> GenuineIntel GNU/Linux
>> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ cat
>> /proc/meminfo /proc/cpuinfo
>> MemTotal: 8197172 kB
>> MemFree: 180264 kB
>> Buffers: 227552 kB
>> Cached: 6427308 kB
>> SwapCached: 5744 kB
>> Active: 914940 kB
>> Inactive: 6820352 kB
>> Active(anon): 310092 kB
>> Inactive(anon): 776660 kB
>> Active(file): 604848 kB
>> Inactive(file): 6043692 kB
>> Unevictable: 0 kB
>> Mlocked: 0 kB
>> SwapTotal: 6498284 kB
>> SwapFree: 6472696 kB
>> Dirty: 484 kB
>> Writeback: 0 kB
>> AnonPages: 1075824 kB
>> Mapped: 56784 kB
>> Slab: 192872 kB
>> SReclaimable: 162736 kB
>> SUnreclaim: 30136 kB
>> PageTables: 10908 kB
>> NFS_Unstable: 0 kB
>> Bounce: 0 kB
>> WritebackTmp: 0 kB
>> CommitLimit: 10596868 kB
>> Committed_AS: 1617720 kB
>> VmallocTotal: 34359738367 kB
>> VmallocUsed: 334552 kB
>> VmallocChunk: 34359384571 kB
>> HugePages_Total: 0
>> HugePages_Free: 0
>> HugePages_Rsvd: 0
>> HugePages_Surp: 0
>> Hugepagesize: 2048 kB
>> DirectMap4k: 8119808 kB
>> DirectMap2M: 268288 kB
>> processor : 0
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 23
>> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>> stepping : 10
>> cpu MHz : 2664.000
>> cache size : 3072 KB
>> physical id : 0
>> siblings : 4
>> core id : 0
>> cpu cores : 4
>> apicid : 0
>> initial apicid : 0
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 13
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>> lahf_lm tpr_shadow vnmi flexpriority
>> bogomips : 5343.38
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 36 bits physical, 48 bits virtual
>> power management:
>>
>> processor : 1
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 23
>> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>> stepping : 10
>> cpu MHz : 2664.000
>> cache size : 3072 KB
>> physical id : 0
>> siblings : 4
>> core id : 1
>> cpu cores : 4
>> apicid : 1
>> initial apicid : 1
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 13
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>> lahf_lm tpr_shadow vnmi flexpriority
>> bogomips : 5343.00
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 36 bits physical, 48 bits virtual
>> power management:
>>
>> processor : 2
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 23
>> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>> stepping : 10
>> cpu MHz : 2664.000
>> cache size : 3072 KB
>> physical id : 0
>> siblings : 4
>> core id : 2
>> cpu cores : 4
>> apicid : 2
>> initial apicid : 2
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 13
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>> lahf_lm tpr_shadow vnmi flexpriority
>> bogomips : 5343.03
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 36 bits physical, 48 bits virtual
>> power management:
>>
>> processor : 3
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 23
>> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>> stepping : 10
>> cpu MHz : 2664.000
>> cache size : 3072 KB
>> physical id : 0
>> siblings : 4
>> core id : 3
>> cpu cores : 4
>> apicid : 3
>> initial apicid : 3
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 13
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>> lahf_lm tpr_shadow vnmi flexpriority
>> bogomips : 5343.03
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 36 bits physical, 48 bits virtual
>> power management:
>>
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [LTP] [FIX PATCHES] open_posix_execute.sh
2009-07-30 10:25 ` naresh kamboju
2009-07-30 18:22 ` Garrett Cooper
@ 2009-07-30 18:30 ` Subrata Modak
2009-08-03 13:24 ` naresh kamboju
1 sibling, 1 reply; 10+ messages in thread
From: Subrata Modak @ 2009-07-30 18:30 UTC (permalink / raw)
To: naresh kamboju; +Cc: ltp-list, Brandon Philips
On Thu, 2009-07-30 at 15:55 +0530, naresh kamboju wrote:
> On Thu, Jul 30, 2009 at 9:05 AM, Garrett Cooper<yanegomi@gmail.com> wrote:
> > On Mon, Jul 27, 2009 at 11:50 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
> >> Hi,
> >>
> >> Hope you have reviewed below patch.
> >> If you any issue please let me know.
> >>
> >> Subrata/ Garrett,
> >> Please review, if you feel okay.
> >> commit.
> >>
> >> Best regards,
> >> Naresh Kamboju
> >>
> >>
> >> On Mon, Jul 20, 2009 at 6:35 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
> >>> Hi,
> >>>
> >>> As per the execute.sh script file there is time limit of two minutes
> >>> for each test case execution if it takes more time it will be reported
> >>> as HUNG.
> >>>
> >>> shm_open/23-1.c test case under posix test suite which executes more
> >>> than two minitutes so test case reported as HUNG.
> >>>
> >>> I have changed time limit from 120 to 300 sec. that is nothing but two
> >>> minutes to five minutes. In low end machines this test case taking 4
> >>> min to complete execution.
> >>>
> >>> Now test cases reported as PASS
> >>>
> >>> I have attached patch and below.
> >>> Please review the same.
> >
> > Naresh,
> > I looked at the testcase, and I think I can see where your concern
> > stems from, as this is a stress test, more than a functional test
> > (1000 child PIDs looping 1000 times each... that's a fair number of
> > cycles :)...). What I'd be really be interested in is the number of
> > cycles being generated (msec is `randomly' generated -- see line 75).
> > However, when I ran the testcase on my machine -- it took less than 10
> > seconds (!):
> >
> >
> > I do have more RAM and all, and I have a fairly recent Intel
> > processor (posted below), but what do you have that's so sluggish by
> > chance?
> Hi Garrett,
>
>
> > I wonder why it failed though *shrugs*.
> Oops. I forgot to say some points.
So, please resend a clean one.
Regards--
Subrata
>
> > Thanks,
> > -Garrett
> >
> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ gcc
> > -Itestcases/open_posix_testsuite/include/
> > testcases/open_posix_testsuite/conformance/interfaces/shm_open/23-1.c
> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ time ./a.out
> > create_cnt: 890
> > Test FAILED
> >
> > real 0m10.947s
> > user 0m4.074s
> > sys 0m9.189s
>
>
> Test cases will create shm files under /dev/shm/shm_XXX
> Before executing this test case mount /dev/shm as tmpfs
>
> 1. Create directory
>
> #mkdir /dev/shm
>
>
> 2. Add below line in /etc/fstab
>
> tmpfs /dev/shm tmpfs defaults 0 0
>
> 3. mount
> #mount –a
> Or
> # mount –t tmpfs /dev/shm
> #mount
> /dev/sda2 on / type ext3 (rw)
> /dev/sda3 on /home type ext3 (rw)
> /dev/sda1 on /boot type ext3 (rw)
> tmpfs on /dev/shm type tmpfs (rw)
>
>
> 4. go to test case location
>
> #cd ~/ltp/testcases/open_posix_testsuite/conformance/interfaces/shm_open
>
> # time ./23-1.test
> create_cnt: 1000
>
> real 3m34.111s
> user 0m51.520s
> sys 1m54.370s
>
> Best regards,
> Naresh Kamboju
>
> >
> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ uname -a
> > Linux orangebox 2.6.29-gentoo-r5 #2 SMP PREEMPT Sun Jun 14 01:11:32
> > PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> > GenuineIntel GNU/Linux
> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ cat
> > /proc/meminfo /proc/cpuinfo
> > MemTotal: 8197172 kB
> > MemFree: 180264 kB
> > Buffers: 227552 kB
> > Cached: 6427308 kB
> > SwapCached: 5744 kB
> > Active: 914940 kB
> > Inactive: 6820352 kB
> > Active(anon): 310092 kB
> > Inactive(anon): 776660 kB
> > Active(file): 604848 kB
> > Inactive(file): 6043692 kB
> > Unevictable: 0 kB
> > Mlocked: 0 kB
> > SwapTotal: 6498284 kB
> > SwapFree: 6472696 kB
> > Dirty: 484 kB
> > Writeback: 0 kB
> > AnonPages: 1075824 kB
> > Mapped: 56784 kB
> > Slab: 192872 kB
> > SReclaimable: 162736 kB
> > SUnreclaim: 30136 kB
> > PageTables: 10908 kB
> > NFS_Unstable: 0 kB
> > Bounce: 0 kB
> > WritebackTmp: 0 kB
> > CommitLimit: 10596868 kB
> > Committed_AS: 1617720 kB
> > VmallocTotal: 34359738367 kB
> > VmallocUsed: 334552 kB
> > VmallocChunk: 34359384571 kB
> > HugePages_Total: 0
> > HugePages_Free: 0
> > HugePages_Rsvd: 0
> > HugePages_Surp: 0
> > Hugepagesize: 2048 kB
> > DirectMap4k: 8119808 kB
> > DirectMap2M: 268288 kB
> > processor : 0
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 23
> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> > stepping : 10
> > cpu MHz : 2664.000
> > cache size : 3072 KB
> > physical id : 0
> > siblings : 4
> > core id : 0
> > cpu cores : 4
> > apicid : 0
> > initial apicid : 0
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 13
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> > lahf_lm tpr_shadow vnmi flexpriority
> > bogomips : 5343.38
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 36 bits physical, 48 bits virtual
> > power management:
> >
> > processor : 1
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 23
> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> > stepping : 10
> > cpu MHz : 2664.000
> > cache size : 3072 KB
> > physical id : 0
> > siblings : 4
> > core id : 1
> > cpu cores : 4
> > apicid : 1
> > initial apicid : 1
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 13
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> > lahf_lm tpr_shadow vnmi flexpriority
> > bogomips : 5343.00
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 36 bits physical, 48 bits virtual
> > power management:
> >
> > processor : 2
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 23
> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> > stepping : 10
> > cpu MHz : 2664.000
> > cache size : 3072 KB
> > physical id : 0
> > siblings : 4
> > core id : 2
> > cpu cores : 4
> > apicid : 2
> > initial apicid : 2
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 13
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> > lahf_lm tpr_shadow vnmi flexpriority
> > bogomips : 5343.03
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 36 bits physical, 48 bits virtual
> > power management:
> >
> > processor : 3
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 23
> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> > stepping : 10
> > cpu MHz : 2664.000
> > cache size : 3072 KB
> > physical id : 0
> > siblings : 4
> > core id : 3
> > cpu cores : 4
> > apicid : 3
> > initial apicid : 3
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 13
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> > lahf_lm tpr_shadow vnmi flexpriority
> > bogomips : 5343.03
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 36 bits physical, 48 bits virtual
> > power management:
> >
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [LTP] [FIX PATCHES] open_posix_execute.sh
2009-07-30 18:30 ` Subrata Modak
@ 2009-08-03 13:24 ` naresh kamboju
2009-08-04 12:08 ` Subrata Modak
0 siblings, 1 reply; 10+ messages in thread
From: naresh kamboju @ 2009-08-03 13:24 UTC (permalink / raw)
To: subrata; +Cc: ltp-list, Brandon Philips
[-- Attachment #1: Type: text/plain, Size: 10942 bytes --]
Hi Subrata,
As per the execute.sh script file there is time limit of two minutes
for each test case execution if it takes more time it will be reported
as HUNG.
shm_open/23-1.c test case under posix test suite which executes more
than two minutes so test case reported as HUNG.
I have changed time limit from 120 to 300 sec. that is nothing but two
minutes to five minutes. In low end machines this test case taking 4
min to complete execution.
Now test cases reported as PASS
I have attached patch and below.
Best regards,
Naresh Kamboju
/*****************************************************/
Before Patch:
conformance/interfaces/shm_open/23-1.test:execution:HUNG
After Patch:
conformance/interfaces/shm_open/23-1.test:execution:PASS
/*****************************************************/
Signed-off-by: Naresh Kamboju < naresh.kernel@gmail.com >
diff -Naurb a/testcases/open_posix_testsuite/execute.sh
b/testcases/open_posix_testsuite/execute.sh
--- a/testcases/open_posix_testsuite/execute.sh 2007-07-26
17:32:11.000000000 +0530
+++ b/testcases/open_posix_testsuite/execute.sh 2009-07-20
17:53:15.000000000 +0530
@@ -163,8 +163,8 @@
declare -i SEGV=0
declare -i OTH=0
-# Maximum Two minutes waiting time period to execute a test. If it
exceeds, the test case will go into the 'HUNG' category.
-TIMEOUT_VAL=120
+# Maximum five minutes waiting time period to execute a test. If it
exceeds, the test case will go into the 'HUNG' category.
+TIMEOUT_VAL=300
# if gcc available then remove the below line comment else put the t0
in posixtestsuite directory.
#gcc -o t0 t0.c
On Fri, Jul 31, 2009 at 12:00 AM, Subrata
Modak<subrata@linux.vnet.ibm.com> wrote:
> On Thu, 2009-07-30 at 15:55 +0530, naresh kamboju wrote:
>> On Thu, Jul 30, 2009 at 9:05 AM, Garrett Cooper<yanegomi@gmail.com> wrote:
>> > On Mon, Jul 27, 2009 at 11:50 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>> >> Hi,
>> >>
>> >> Hope you have reviewed below patch.
>> >> If you any issue please let me know.
>> >>
>> >> Subrata/ Garrett,
>> >> Please review, if you feel okay.
>> >> commit.
>> >>
>> >> Best regards,
>> >> Naresh Kamboju
>> >>
>> >>
>> >> On Mon, Jul 20, 2009 at 6:35 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>> >>> Hi,
>> >>>
>> >>> As per the execute.sh script file there is time limit of two minutes
>> >>> for each test case execution if it takes more time it will be reported
>> >>> as HUNG.
>> >>>
>> >>> shm_open/23-1.c test case under posix test suite which executes more
>> >>> than two minitutes so test case reported as HUNG.
>> >>>
>> >>> I have changed time limit from 120 to 300 sec. that is nothing but two
>> >>> minutes to five minutes. In low end machines this test case taking 4
>> >>> min to complete execution.
>> >>>
>> >>> Now test cases reported as PASS
>> >>>
>> >>> I have attached patch and below.
>> >>> Please review the same.
>> >
>> > Naresh,
>> > I looked at the testcase, and I think I can see where your concern
>> > stems from, as this is a stress test, more than a functional test
>> > (1000 child PIDs looping 1000 times each... that's a fair number of
>> > cycles :)...). What I'd be really be interested in is the number of
>> > cycles being generated (msec is `randomly' generated -- see line 75).
>> > However, when I ran the testcase on my machine -- it took less than 10
>> > seconds (!):
>> >
>> >
>> > I do have more RAM and all, and I have a fairly recent Intel
>> > processor (posted below), but what do you have that's so sluggish by
>> > chance?
>> Hi Garrett,
>>
>>
>> > I wonder why it failed though *shrugs*.
>> Oops. I forgot to say some points.
>
> So, please resend a clean one.
>
> Regards--
> Subrata
>
>>
>> > Thanks,
>> > -Garrett
>> >
>> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ gcc
>> > -Itestcases/open_posix_testsuite/include/
>> > testcases/open_posix_testsuite/conformance/interfaces/shm_open/23-1.c
>> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ time ./a.out
>> > create_cnt: 890
>> > Test FAILED
>> >
>> > real 0m10.947s
>> > user 0m4.074s
>> > sys 0m9.189s
>>
>>
>> Test cases will create shm files under /dev/shm/shm_XXX
>> Before executing this test case mount /dev/shm as tmpfs
>>
>> 1. Create directory
>>
>> #mkdir /dev/shm
>>
>>
>> 2. Add below line in /etc/fstab
>>
>> tmpfs /dev/shm tmpfs defaults 0 0
>>
>> 3. mount
>> #mount –a
>> Or
>> # mount –t tmpfs /dev/shm
>> #mount
>> /dev/sda2 on / type ext3 (rw)
>> /dev/sda3 on /home type ext3 (rw)
>> /dev/sda1 on /boot type ext3 (rw)
>> tmpfs on /dev/shm type tmpfs (rw)
>>
>>
>> 4. go to test case location
>>
>> #cd ~/ltp/testcases/open_posix_testsuite/conformance/interfaces/shm_open
>>
>> # time ./23-1.test
>> create_cnt: 1000
>>
>> real 3m34.111s
>> user 0m51.520s
>> sys 1m54.370s
>>
>> Best regards,
>> Naresh Kamboju
>>
>> >
>> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ uname -a
>> > Linux orangebox 2.6.29-gentoo-r5 #2 SMP PREEMPT Sun Jun 14 01:11:32
>> > PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>> > GenuineIntel GNU/Linux
>> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ cat
>> > /proc/meminfo /proc/cpuinfo
>> > MemTotal: 8197172 kB
>> > MemFree: 180264 kB
>> > Buffers: 227552 kB
>> > Cached: 6427308 kB
>> > SwapCached: 5744 kB
>> > Active: 914940 kB
>> > Inactive: 6820352 kB
>> > Active(anon): 310092 kB
>> > Inactive(anon): 776660 kB
>> > Active(file): 604848 kB
>> > Inactive(file): 6043692 kB
>> > Unevictable: 0 kB
>> > Mlocked: 0 kB
>> > SwapTotal: 6498284 kB
>> > SwapFree: 6472696 kB
>> > Dirty: 484 kB
>> > Writeback: 0 kB
>> > AnonPages: 1075824 kB
>> > Mapped: 56784 kB
>> > Slab: 192872 kB
>> > SReclaimable: 162736 kB
>> > SUnreclaim: 30136 kB
>> > PageTables: 10908 kB
>> > NFS_Unstable: 0 kB
>> > Bounce: 0 kB
>> > WritebackTmp: 0 kB
>> > CommitLimit: 10596868 kB
>> > Committed_AS: 1617720 kB
>> > VmallocTotal: 34359738367 kB
>> > VmallocUsed: 334552 kB
>> > VmallocChunk: 34359384571 kB
>> > HugePages_Total: 0
>> > HugePages_Free: 0
>> > HugePages_Rsvd: 0
>> > HugePages_Surp: 0
>> > Hugepagesize: 2048 kB
>> > DirectMap4k: 8119808 kB
>> > DirectMap2M: 268288 kB
>> > processor : 0
>> > vendor_id : GenuineIntel
>> > cpu family : 6
>> > model : 23
>> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>> > stepping : 10
>> > cpu MHz : 2664.000
>> > cache size : 3072 KB
>> > physical id : 0
>> > siblings : 4
>> > core id : 0
>> > cpu cores : 4
>> > apicid : 0
>> > initial apicid : 0
>> > fpu : yes
>> > fpu_exception : yes
>> > cpuid level : 13
>> > wp : yes
>> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>> > lahf_lm tpr_shadow vnmi flexpriority
>> > bogomips : 5343.38
>> > clflush size : 64
>> > cache_alignment : 64
>> > address sizes : 36 bits physical, 48 bits virtual
>> > power management:
>> >
>> > processor : 1
>> > vendor_id : GenuineIntel
>> > cpu family : 6
>> > model : 23
>> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>> > stepping : 10
>> > cpu MHz : 2664.000
>> > cache size : 3072 KB
>> > physical id : 0
>> > siblings : 4
>> > core id : 1
>> > cpu cores : 4
>> > apicid : 1
>> > initial apicid : 1
>> > fpu : yes
>> > fpu_exception : yes
>> > cpuid level : 13
>> > wp : yes
>> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>> > lahf_lm tpr_shadow vnmi flexpriority
>> > bogomips : 5343.00
>> > clflush size : 64
>> > cache_alignment : 64
>> > address sizes : 36 bits physical, 48 bits virtual
>> > power management:
>> >
>> > processor : 2
>> > vendor_id : GenuineIntel
>> > cpu family : 6
>> > model : 23
>> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>> > stepping : 10
>> > cpu MHz : 2664.000
>> > cache size : 3072 KB
>> > physical id : 0
>> > siblings : 4
>> > core id : 2
>> > cpu cores : 4
>> > apicid : 2
>> > initial apicid : 2
>> > fpu : yes
>> > fpu_exception : yes
>> > cpuid level : 13
>> > wp : yes
>> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>> > lahf_lm tpr_shadow vnmi flexpriority
>> > bogomips : 5343.03
>> > clflush size : 64
>> > cache_alignment : 64
>> > address sizes : 36 bits physical, 48 bits virtual
>> > power management:
>> >
>> > processor : 3
>> > vendor_id : GenuineIntel
>> > cpu family : 6
>> > model : 23
>> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>> > stepping : 10
>> > cpu MHz : 2664.000
>> > cache size : 3072 KB
>> > physical id : 0
>> > siblings : 4
>> > core id : 3
>> > cpu cores : 4
>> > apicid : 3
>> > initial apicid : 3
>> > fpu : yes
>> > fpu_exception : yes
>> > cpuid level : 13
>> > wp : yes
>> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>> > lahf_lm tpr_shadow vnmi flexpriority
>> > bogomips : 5343.03
>> > clflush size : 64
>> > cache_alignment : 64
>> > address sizes : 36 bits physical, 48 bits virtual
>> > power management:
>> >
>
>
[-- Attachment #2: ltp-posix-execute.patch --]
[-- Type: application/octet-stream, Size: 731 bytes --]
diff -Naurb a/testcases/open_posix_testsuite/execute.sh b/testcases/open_posix_testsuite/execute.sh
--- a/testcases/open_posix_testsuite/execute.sh 2007-07-26 17:32:11.000000000 +0530
+++ b/testcases/open_posix_testsuite/execute.sh 2009-07-20 17:53:15.000000000 +0530
@@ -163,8 +163,8 @@
declare -i SEGV=0
declare -i OTH=0
-# Maximum Two minutes waiting time period to execute a test. If it exceeds, the test case will go into the 'HUNG' category.
-TIMEOUT_VAL=120
+# Maximum five minutes waiting time period to execute a test. If it exceeds, the test case will go into the 'HUNG' category.
+TIMEOUT_VAL=300
# if gcc available then remove the below line comment else put the t0 in posixtestsuite directory.
#gcc -o t0 t0.c
[-- Attachment #3: Type: text/plain, Size: 355 bytes --]
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
[-- Attachment #4: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [LTP] [FIX PATCHES] open_posix_execute.sh
2009-07-30 18:22 ` Garrett Cooper
@ 2009-08-03 15:49 ` naresh kamboju
0 siblings, 0 replies; 10+ messages in thread
From: naresh kamboju @ 2009-08-03 15:49 UTC (permalink / raw)
To: Garrett Cooper; +Cc: ltp-list, Brandon Philips
On Thu, Jul 30, 2009 at 11:52 PM, Garrett Cooper<yanegomi@gmail.com> wrote:
> On Thu, Jul 30, 2009 at 3:25 AM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>> On Thu, Jul 30, 2009 at 9:05 AM, Garrett Cooper<yanegomi@gmail.com> wrote:
>>> On Mon, Jul 27, 2009 at 11:50 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> Hope you have reviewed below patch.
>>>> If you any issue please let me know.
>>>>
>>>> Subrata/ Garrett,
>>>> Please review, if you feel okay.
>>>> commit.
>>>>
>>>> Best regards,
>>>> Naresh Kamboju
>>>>
>>>>
>>>> On Mon, Jul 20, 2009 at 6:35 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
>>>>> Hi,
>>>>>
>>>>> As per the execute.sh script file there is time limit of two minutes
>>>>> for each test case execution if it takes more time it will be reported
>>>>> as HUNG.
>>>>>
>>>>> shm_open/23-1.c test case under posix test suite which executes more
>>>>> than two minitutes so test case reported as HUNG.
>>>>>
>>>>> I have changed time limit from 120 to 300 sec. that is nothing but two
>>>>> minutes to five minutes. In low end machines this test case taking 4
>>>>> min to complete execution.
>>>>>
>>>>> Now test cases reported as PASS
>>>>>
>>>>> I have attached patch and below.
>>>>> Please review the same.
>>>
>>> Naresh,
>>> I looked at the testcase, and I think I can see where your concern
>>> stems from, as this is a stress test, more than a functional test
>>> (1000 child PIDs looping 1000 times each... that's a fair number of
>>> cycles :)...). What I'd be really be interested in is the number of
>>> cycles being generated (msec is `randomly' generated -- see line 75).
>>> However, when I ran the testcase on my machine -- it took less than 10
>>> seconds (!):
>>>
>>>
>>> I do have more RAM and all, and I have a fairly recent Intel
>>> processor (posted below), but what do you have that's so sluggish by
>>> chance?
>> Hi Garrett,
>>
>>
>>> I wonder why it failed though *shrugs*.
>> Oops. I forgot to say some points.
>>
>>> Thanks,
>>> -Garrett
>>>
>>> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ gcc
>>> -Itestcases/open_posix_testsuite/include/
>>> testcases/open_posix_testsuite/conformance/interfaces/shm_open/23-1.c
>>> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ time ./a.out
>>> create_cnt: 890
>>> Test FAILED
>>>
>>> real 0m10.947s
>>> user 0m4.074s
>>> sys 0m9.189s
>>
>>
>> Test cases will create shm files under /dev/shm/shm_XXX
>> Before executing this test case mount /dev/shm as tmpfs
>>
>> 1. Create directory
>>
>> #mkdir /dev/shm
>
> Already done with fstab in Gentoo Linux.
>
>> 2. Add below line in /etc/fstab
>>
>> tmpfs /dev/shm tmpfs defaults 0 0
>
> (!) Uhhhhhhhhh.... this stuff should only be done if required.
>
>> 3. mount
>> #mount –a
>> Or
>> # mount –t tmpfs /dev/shm
>> #mount
>> /dev/sda2 on / type ext3 (rw)
>> /dev/sda3 on /home type ext3 (rw)
>> /dev/sda1 on /boot type ext3 (rw)
>> tmpfs on /dev/shm type tmpfs (rw)
>>
>>
>> 4. go to test case location
>>
>> #cd ~/ltp/testcases/open_posix_testsuite/conformance/interfaces/shm_open
>>
>> # time ./23-1.test
>> create_cnt: 1000
>>
>> real 3m34.111s
>> user 0m51.520s
>> sys 1m54.370s
>
> 4. may or may not have been why it was failing *shrug*. I'll have to
> run it as designed.
Please execute this test and share the results.
-Naresh
>
> -Garrett
>
>>> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ uname -a
>>> Linux orangebox 2.6.29-gentoo-r5 #2 SMP PREEMPT Sun Jun 14 01:11:32
>>> PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>>> GenuineIntel GNU/Linux
>>> gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ cat
>>> /proc/meminfo /proc/cpuinfo
>>> MemTotal: 8197172 kB
>>> MemFree: 180264 kB
>>> Buffers: 227552 kB
>>> Cached: 6427308 kB
>>> SwapCached: 5744 kB
>>> Active: 914940 kB
>>> Inactive: 6820352 kB
>>> Active(anon): 310092 kB
>>> Inactive(anon): 776660 kB
>>> Active(file): 604848 kB
>>> Inactive(file): 6043692 kB
>>> Unevictable: 0 kB
>>> Mlocked: 0 kB
>>> SwapTotal: 6498284 kB
>>> SwapFree: 6472696 kB
>>> Dirty: 484 kB
>>> Writeback: 0 kB
>>> AnonPages: 1075824 kB
>>> Mapped: 56784 kB
>>> Slab: 192872 kB
>>> SReclaimable: 162736 kB
>>> SUnreclaim: 30136 kB
>>> PageTables: 10908 kB
>>> NFS_Unstable: 0 kB
>>> Bounce: 0 kB
>>> WritebackTmp: 0 kB
>>> CommitLimit: 10596868 kB
>>> Committed_AS: 1617720 kB
>>> VmallocTotal: 34359738367 kB
>>> VmallocUsed: 334552 kB
>>> VmallocChunk: 34359384571 kB
>>> HugePages_Total: 0
>>> HugePages_Free: 0
>>> HugePages_Rsvd: 0
>>> HugePages_Surp: 0
>>> Hugepagesize: 2048 kB
>>> DirectMap4k: 8119808 kB
>>> DirectMap2M: 268288 kB
>>> processor : 0
>>> vendor_id : GenuineIntel
>>> cpu family : 6
>>> model : 23
>>> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>>> stepping : 10
>>> cpu MHz : 2664.000
>>> cache size : 3072 KB
>>> physical id : 0
>>> siblings : 4
>>> core id : 0
>>> cpu cores : 4
>>> apicid : 0
>>> initial apicid : 0
>>> fpu : yes
>>> fpu_exception : yes
>>> cpuid level : 13
>>> wp : yes
>>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>>> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>>> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>>> lahf_lm tpr_shadow vnmi flexpriority
>>> bogomips : 5343.38
>>> clflush size : 64
>>> cache_alignment : 64
>>> address sizes : 36 bits physical, 48 bits virtual
>>> power management:
>>>
>>> processor : 1
>>> vendor_id : GenuineIntel
>>> cpu family : 6
>>> model : 23
>>> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>>> stepping : 10
>>> cpu MHz : 2664.000
>>> cache size : 3072 KB
>>> physical id : 0
>>> siblings : 4
>>> core id : 1
>>> cpu cores : 4
>>> apicid : 1
>>> initial apicid : 1
>>> fpu : yes
>>> fpu_exception : yes
>>> cpuid level : 13
>>> wp : yes
>>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>>> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>>> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>>> lahf_lm tpr_shadow vnmi flexpriority
>>> bogomips : 5343.00
>>> clflush size : 64
>>> cache_alignment : 64
>>> address sizes : 36 bits physical, 48 bits virtual
>>> power management:
>>>
>>> processor : 2
>>> vendor_id : GenuineIntel
>>> cpu family : 6
>>> model : 23
>>> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>>> stepping : 10
>>> cpu MHz : 2664.000
>>> cache size : 3072 KB
>>> physical id : 0
>>> siblings : 4
>>> core id : 2
>>> cpu cores : 4
>>> apicid : 2
>>> initial apicid : 2
>>> fpu : yes
>>> fpu_exception : yes
>>> cpuid level : 13
>>> wp : yes
>>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>>> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>>> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>>> lahf_lm tpr_shadow vnmi flexpriority
>>> bogomips : 5343.03
>>> clflush size : 64
>>> cache_alignment : 64
>>> address sizes : 36 bits physical, 48 bits virtual
>>> power management:
>>>
>>> processor : 3
>>> vendor_id : GenuineIntel
>>> cpu family : 6
>>> model : 23
>>> model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
>>> stepping : 10
>>> cpu MHz : 2664.000
>>> cache size : 3072 KB
>>> physical id : 0
>>> siblings : 4
>>> core id : 3
>>> cpu cores : 4
>>> apicid : 3
>>> initial apicid : 3
>>> fpu : yes
>>> fpu_exception : yes
>>> cpuid level : 13
>>> wp : yes
>>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>>> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
>>> monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
>>> lahf_lm tpr_shadow vnmi flexpriority
>>> bogomips : 5343.03
>>> clflush size : 64
>>> cache_alignment : 64
>>> address sizes : 36 bits physical, 48 bits virtual
>>> power management:
>>>
>>
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [LTP] [FIX PATCHES] open_posix_execute.sh
2009-08-03 13:24 ` naresh kamboju
@ 2009-08-04 12:08 ` Subrata Modak
0 siblings, 0 replies; 10+ messages in thread
From: Subrata Modak @ 2009-08-04 12:08 UTC (permalink / raw)
To: naresh kamboju; +Cc: ltp-list, Brandon Philips
On Mon, 2009-08-03 at 18:54 +0530, naresh kamboju wrote:
> Hi Subrata,
>
> As per the execute.sh script file there is time limit of two minutes
> for each test case execution if it takes more time it will be reported
> as HUNG.
>
> shm_open/23-1.c test case under posix test suite which executes more
> than two minutes so test case reported as HUNG.
>
> I have changed time limit from 120 to 300 sec. that is nothing but two
> minutes to five minutes. In low end machines this test case taking 4
> min to complete execution.
>
> Now test cases reported as PASS
>
> I have attached patch and below.
>
>
> Best regards,
> Naresh Kamboju
>
>
> /*****************************************************/
> Before Patch:
>
> conformance/interfaces/shm_open/23-1.test:execution:HUNG
>
>
> After Patch:
>
> conformance/interfaces/shm_open/23-1.test:execution:PASS
> /*****************************************************/
>
>
> Signed-off-by: Naresh Kamboju < naresh.kernel@gmail.com >
Thanks.
Regards--
Subrata
>
> diff -Naurb a/testcases/open_posix_testsuite/execute.sh
> b/testcases/open_posix_testsuite/execute.sh
> --- a/testcases/open_posix_testsuite/execute.sh 2007-07-26
> 17:32:11.000000000 +0530
> +++ b/testcases/open_posix_testsuite/execute.sh 2009-07-20
> 17:53:15.000000000 +0530
> @@ -163,8 +163,8 @@
> declare -i SEGV=0
> declare -i OTH=0
>
> -# Maximum Two minutes waiting time period to execute a test. If it
> exceeds, the test case will go into the 'HUNG' category.
> -TIMEOUT_VAL=120
> +# Maximum five minutes waiting time period to execute a test. If it
> exceeds, the test case will go into the 'HUNG' category.
> +TIMEOUT_VAL=300
>
> # if gcc available then remove the below line comment else put the t0
> in posixtestsuite directory.
> #gcc -o t0 t0.c
>
>
>
>
>
>
> On Fri, Jul 31, 2009 at 12:00 AM, Subrata
> Modak<subrata@linux.vnet.ibm.com> wrote:
> > On Thu, 2009-07-30 at 15:55 +0530, naresh kamboju wrote:
> >> On Thu, Jul 30, 2009 at 9:05 AM, Garrett Cooper<yanegomi@gmail.com> wrote:
> >> > On Mon, Jul 27, 2009 at 11:50 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
> >> >> Hi,
> >> >>
> >> >> Hope you have reviewed below patch.
> >> >> If you any issue please let me know.
> >> >>
> >> >> Subrata/ Garrett,
> >> >> Please review, if you feel okay.
> >> >> commit.
> >> >>
> >> >> Best regards,
> >> >> Naresh Kamboju
> >> >>
> >> >>
> >> >> On Mon, Jul 20, 2009 at 6:35 PM, naresh kamboju<naresh.kernel@gmail.com> wrote:
> >> >>> Hi,
> >> >>>
> >> >>> As per the execute.sh script file there is time limit of two minutes
> >> >>> for each test case execution if it takes more time it will be reported
> >> >>> as HUNG.
> >> >>>
> >> >>> shm_open/23-1.c test case under posix test suite which executes more
> >> >>> than two minitutes so test case reported as HUNG.
> >> >>>
> >> >>> I have changed time limit from 120 to 300 sec. that is nothing but two
> >> >>> minutes to five minutes. In low end machines this test case taking 4
> >> >>> min to complete execution.
> >> >>>
> >> >>> Now test cases reported as PASS
> >> >>>
> >> >>> I have attached patch and below.
> >> >>> Please review the same.
> >> >
> >> > Naresh,
> >> > I looked at the testcase, and I think I can see where your concern
> >> > stems from, as this is a stress test, more than a functional test
> >> > (1000 child PIDs looping 1000 times each... that's a fair number of
> >> > cycles :)...). What I'd be really be interested in is the number of
> >> > cycles being generated (msec is `randomly' generated -- see line 75).
> >> > However, when I ran the testcase on my machine -- it took less than 10
> >> > seconds (!):
> >> >
> >> >
> >> > I do have more RAM and all, and I have a fairly recent Intel
> >> > processor (posted below), but what do you have that's so sluggish by
> >> > chance?
> >> Hi Garrett,
> >>
> >>
> >> > I wonder why it failed though *shrugs*.
> >> Oops. I forgot to say some points.
> >
> > So, please resend a clean one.
> >
> > Regards--
> > Subrata
> >
> >>
> >> > Thanks,
> >> > -Garrett
> >> >
> >> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ gcc
> >> > -Itestcases/open_posix_testsuite/include/
> >> > testcases/open_posix_testsuite/conformance/interfaces/shm_open/23-1.c
> >> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ time ./a.out
> >> > create_cnt: 890
> >> > Test FAILED
> >> >
> >> > real 0m10.947s
> >> > user 0m4.074s
> >> > sys 0m9.189s
> >>
> >>
> >> Test cases will create shm files under /dev/shm/shm_XXX
> >> Before executing this test case mount /dev/shm as tmpfs
> >>
> >> 1. Create directory
> >>
> >> #mkdir /dev/shm
> >>
> >>
> >> 2. Add below line in /etc/fstab
> >>
> >> tmpfs /dev/shm tmpfs defaults 0 0
> >>
> >> 3. mount
> >> #mount –a
> >> Or
> >> # mount –t tmpfs /dev/shm
> >> #mount
> >> /dev/sda2 on / type ext3 (rw)
> >> /dev/sda3 on /home type ext3 (rw)
> >> /dev/sda1 on /boot type ext3 (rw)
> >> tmpfs on /dev/shm type tmpfs (rw)
> >>
> >>
> >> 4. go to test case location
> >>
> >> #cd ~/ltp/testcases/open_posix_testsuite/conformance/interfaces/shm_open
> >>
> >> # time ./23-1.test
> >> create_cnt: 1000
> >>
> >> real 3m34.111s
> >> user 0m51.520s
> >> sys 1m54.370s
> >>
> >> Best regards,
> >> Naresh Kamboju
> >>
> >> >
> >> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ uname -a
> >> > Linux orangebox 2.6.29-gentoo-r5 #2 SMP PREEMPT Sun Jun 14 01:11:32
> >> > PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> >> > GenuineIntel GNU/Linux
> >> > gcooper@orangebox /scratch/ltp-makefile-infra-rework/ltp $ cat
> >> > /proc/meminfo /proc/cpuinfo
> >> > MemTotal: 8197172 kB
> >> > MemFree: 180264 kB
> >> > Buffers: 227552 kB
> >> > Cached: 6427308 kB
> >> > SwapCached: 5744 kB
> >> > Active: 914940 kB
> >> > Inactive: 6820352 kB
> >> > Active(anon): 310092 kB
> >> > Inactive(anon): 776660 kB
> >> > Active(file): 604848 kB
> >> > Inactive(file): 6043692 kB
> >> > Unevictable: 0 kB
> >> > Mlocked: 0 kB
> >> > SwapTotal: 6498284 kB
> >> > SwapFree: 6472696 kB
> >> > Dirty: 484 kB
> >> > Writeback: 0 kB
> >> > AnonPages: 1075824 kB
> >> > Mapped: 56784 kB
> >> > Slab: 192872 kB
> >> > SReclaimable: 162736 kB
> >> > SUnreclaim: 30136 kB
> >> > PageTables: 10908 kB
> >> > NFS_Unstable: 0 kB
> >> > Bounce: 0 kB
> >> > WritebackTmp: 0 kB
> >> > CommitLimit: 10596868 kB
> >> > Committed_AS: 1617720 kB
> >> > VmallocTotal: 34359738367 kB
> >> > VmallocUsed: 334552 kB
> >> > VmallocChunk: 34359384571 kB
> >> > HugePages_Total: 0
> >> > HugePages_Free: 0
> >> > HugePages_Rsvd: 0
> >> > HugePages_Surp: 0
> >> > Hugepagesize: 2048 kB
> >> > DirectMap4k: 8119808 kB
> >> > DirectMap2M: 268288 kB
> >> > processor : 0
> >> > vendor_id : GenuineIntel
> >> > cpu family : 6
> >> > model : 23
> >> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> >> > stepping : 10
> >> > cpu MHz : 2664.000
> >> > cache size : 3072 KB
> >> > physical id : 0
> >> > siblings : 4
> >> > core id : 0
> >> > cpu cores : 4
> >> > apicid : 0
> >> > initial apicid : 0
> >> > fpu : yes
> >> > fpu_exception : yes
> >> > cpuid level : 13
> >> > wp : yes
> >> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> >> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> >> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> >> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> >> > lahf_lm tpr_shadow vnmi flexpriority
> >> > bogomips : 5343.38
> >> > clflush size : 64
> >> > cache_alignment : 64
> >> > address sizes : 36 bits physical, 48 bits virtual
> >> > power management:
> >> >
> >> > processor : 1
> >> > vendor_id : GenuineIntel
> >> > cpu family : 6
> >> > model : 23
> >> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> >> > stepping : 10
> >> > cpu MHz : 2664.000
> >> > cache size : 3072 KB
> >> > physical id : 0
> >> > siblings : 4
> >> > core id : 1
> >> > cpu cores : 4
> >> > apicid : 1
> >> > initial apicid : 1
> >> > fpu : yes
> >> > fpu_exception : yes
> >> > cpuid level : 13
> >> > wp : yes
> >> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> >> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> >> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> >> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> >> > lahf_lm tpr_shadow vnmi flexpriority
> >> > bogomips : 5343.00
> >> > clflush size : 64
> >> > cache_alignment : 64
> >> > address sizes : 36 bits physical, 48 bits virtual
> >> > power management:
> >> >
> >> > processor : 2
> >> > vendor_id : GenuineIntel
> >> > cpu family : 6
> >> > model : 23
> >> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> >> > stepping : 10
> >> > cpu MHz : 2664.000
> >> > cache size : 3072 KB
> >> > physical id : 0
> >> > siblings : 4
> >> > core id : 2
> >> > cpu cores : 4
> >> > apicid : 2
> >> > initial apicid : 2
> >> > fpu : yes
> >> > fpu_exception : yes
> >> > cpuid level : 13
> >> > wp : yes
> >> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> >> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> >> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> >> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> >> > lahf_lm tpr_shadow vnmi flexpriority
> >> > bogomips : 5343.03
> >> > clflush size : 64
> >> > cache_alignment : 64
> >> > address sizes : 36 bits physical, 48 bits virtual
> >> > power management:
> >> >
> >> > processor : 3
> >> > vendor_id : GenuineIntel
> >> > cpu family : 6
> >> > model : 23
> >> > model name : Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
> >> > stepping : 10
> >> > cpu MHz : 2664.000
> >> > cache size : 3072 KB
> >> > physical id : 0
> >> > siblings : 4
> >> > core id : 3
> >> > cpu cores : 4
> >> > apicid : 3
> >> > initial apicid : 3
> >> > fpu : yes
> >> > fpu_exception : yes
> >> > cpuid level : 13
> >> > wp : yes
> >> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> >> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> >> > syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64
> >> > monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
> >> > lahf_lm tpr_shadow vnmi flexpriority
> >> > bogomips : 5343.03
> >> > clflush size : 64
> >> > cache_alignment : 64
> >> > address sizes : 36 bits physical, 48 bits virtual
> >> > power management:
> >> >
> >
> >
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2009-08-04 12:08 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-07-20 13:05 [LTP] [FIX PATCHES] open_posix_execute.sh naresh kamboju
2009-07-28 6:50 ` naresh kamboju
2009-07-30 3:35 ` Garrett Cooper
2009-07-30 6:10 ` naresh kamboju
2009-07-30 10:25 ` naresh kamboju
2009-07-30 18:22 ` Garrett Cooper
2009-08-03 15:49 ` naresh kamboju
2009-07-30 18:30 ` Subrata Modak
2009-08-03 13:24 ` naresh kamboju
2009-08-04 12:08 ` Subrata Modak
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.