Trace number 207245

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
buggy_2_5 2007-01-08SAT 1.76773 1.79572

General information on the benchmark

Namefapp/test01-04/test02/
test02-0250-10.xml
MD5SUM18b6dc0eb1775fdf92b706b1210b2edc
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark1.76773
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables250
Number of constraints2462
Maximum constraint arity2
Maximum domain size350
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2462
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
-2904 2316 -2876 -2520 -2552 -2352 -2596 -2464 -2448 -2684 -2380 -2608 -2804 -2852 -2376 -2548 -2872 2348 -2648 2324 2444 2328 2520 2732 -2820 -2776 -2516 -2352 2532 -2908 2864 -2608 2260 -2572 2336 -2232 -2916 -2392 -2876 2884 -2688 2764 -2508 -2816 -2336 2756 -2372 2344 -2560 2540 2592 2816 -2236 -2280 -2644 -2900 2344 -2768 -2560 -2484 -2876 -2500 2892 -2628 -2896 -2860 2504 -2260 2260 -2456 -2572 2480 2692 -2596 2304 2556 -2876 -2328 -2260 -2696 -2548 -2916 -2732 -2328 -2688 2856 2648 -2260 2260 -2392 -2424 -2496 2484 2868 2220 -2588 2820 -2652 -2612 -2916 2520 -2352 -2700 -2792 -2688 2756 -2632 -2384 -2728 -2820 2656 -2916 -2628 -2224 -2780 -2392 2764 -2644 2832 -2392 -2724 -2896 -2796 -2264 -2444 -2636 2540 2568 -2804 2772 -2520 2572 -2520 -2392 -2588 -2812 -2916 2296 2816 2260 -2352 2560 -2904 2560 2456 -2652 -2876 -2500 2220 -2364 -2584 -2368 -2396 -2624 -2876 -2916 -2580 2584 -2544 -2668 2328 -2692 2640 -2688 -2592 -2916 2692 -2240 -2300 -2788 -2648 -2632 2648 2288 2272 -2220 -2796 2780 2220 -2332 -2916 -2864 -2660 -2356 -2876 2856 -2392 -2916 2748 2532 2752 2744 -2488 -2856 -2512 2572 -2688 2276 -2304 -2612 -2416 -2448 2340 -2916 -2436 -2344 -2680 2612 -2488 -2876 -2540 -2648 2492 -2376 -2476 2288 -2632 2260 2304 2220 -2436 -2352 -2368 -2624 -2844 2568 -2684 2776 -2332 -2336 2220 -2876 -2860 -2784 -2572 -2264 -2532 -2604 2292 2220 -2260 -2352 -2564 -2684 -2388 2220 -2772 2396 -2876 -2592

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node17/watcher-207245-1168293854 -o ROOT/results/node17/solver-207245-1168293854 -C 1800 -M 900 /tmp/evaluation/207245-1168293854/solver /tmp/evaluation/207245-1168293854/unknown 1800 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB

/proc/loadavg: 0.89 1.11 1.04 5/82 25601
/proc/meminfo: memFree=1494816/2055920 swapFree=4192812/4192956
[pid=25600] ppid=25594 vsize=5352 CPUtime=0
/proc/25600/stat : 25600 (solver) R 25594 25600 19834 0 -1 4194304 280 0 0 0 0 0 0 0 19 0 1 0 177780504 5480448 231 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482711711 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/25600/statm: 1338 231 193 169 0 49 0
[pid=25602] ppid=25600 vsize=0 CPUtime=0
/proc/25602/stat : 25602 (solver) R 25600 25600 19834 0 -1 4194372 26 0 0 0 0 0 0 0 19 0 1 0 177780505 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 65538 0 0 0 17 1 0 0
/proc/25602/statm: 0 0 0 0 0 0 0
[pid=25603] ppid=25600 vsize=5352 CPUtime=0
/proc/25603/stat : 25603 (solver) R 25600 25600 19834 0 -1 4194368 0 0 0 0 0 0 0 0 19 0 1 0 177780505 5480448 231 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482711711 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/25603/statm: 1338 231 193 169 0 49 0

[startup+0.103704 s]
/proc/loadavg: 0.89 1.11 1.04 5/82 25601
/proc/meminfo: memFree=1494816/2055920 swapFree=4192812/4192956
[pid=25600] ppid=25594 vsize=5352 CPUtime=0.05
/proc/25600/stat : 25600 (solver) S 25594 25600 19834 0 -1 4194304 376 2275 0 0 0 0 4 1 17 0 1 0 177780504 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/25600/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 5352

[startup+0.511741 s]
/proc/loadavg: 0.89 1.11 1.04 5/82 25601
/proc/meminfo: memFree=1494816/2055920 swapFree=4192812/4192956
[pid=25600] ppid=25594 vsize=5352 CPUtime=0.05
/proc/25600/stat : 25600 (solver) S 25594 25600 19834 0 -1 4194304 376 2275 0 0 0 0 4 1 17 0 1 0 177780504 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/25600/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 5352

[startup+1.33283 s]
/proc/loadavg: 0.89 1.11 1.04 3/84 26049
/proc/meminfo: memFree=1473808/2055920 swapFree=4192812/4192956
[pid=25600] ppid=25594 vsize=5352 CPUtime=0.86
/proc/25600/stat : 25600 (solver) S 25594 25600 19834 0 -1 4194304 396 6546 0 0 0 0 32 54 16 0 1 0 177780504 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/25600/statm: 1338 242 203 169 0 49 0
[pid=25975] ppid=25600 vsize=10240 CPUtime=0.42
/proc/25975/stat : 25975 (standalone) R 25600 25600 19834 0 -1 4194304 1971 0 0 0 29 13 0 0 21 0 1 0 177780593 10485760 1944 18446744073709551615 134512640 134775488 4294956880 18446744073709551615 4153948110 0 0 4096 0 0 0 0 17 0 0 0
/proc/25975/statm: 2560 1944 136 64 0 1875 0
Current children cumulated CPU time (s) 1.28
Current children cumulated vsize (KiB) 15592

Child status: 0
Real time (s): 1.79572
CPU time (s): 1.76773
CPU user time (s): 1.08283
CPU system time (s): 0.684895
CPU usage (%): 98.4412
Max. virtual memory (cumulated for all children) (KiB): 15600

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.08283
system time used= 0.684895
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8999
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 122
involuntary context switches= 61

runsolver used 0.006998 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node17 on Mon Jan  8 22:04:17 UTC 2007


IDJOB= 207245
IDBENCH= 4278
FILE ID= node17/207245-1168293854

PBS_JOBID= 3501834

Free space on /tmp= 66318 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/test01-04/test02/test02-0250-10.xml
COMMAND LINE= /tmp/evaluation/207245-1168293854/solver /tmp/evaluation/207245-1168293854/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-207245-1168293854 -o ROOT/results/node17/solver-207245-1168293854 -C 1800 -M 900  /tmp/evaluation/207245-1168293854/solver /tmp/evaluation/207245-1168293854/unknown 1800

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  18b6dc0eb1775fdf92b706b1210b2edc

RANDOM SEED= 397981216

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.236
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
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 syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.236
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
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 syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1496136 kB
Buffers:         78864 kB
Cached:         354160 kB
SwapCached:          0 kB
Active:         302556 kB
Inactive:       188688 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1496136 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           11180 kB
Writeback:           0 kB
Mapped:          77176 kB
Slab:            53680 kB
Committed_AS:  5124424 kB
PageTables:       2076 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66305 MiB



End job on node17 on Mon Jan  8 22:04:19 UTC 2007