Trace number 207277

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 2.36264 2.40635

General information on the benchmark

Namefapp/test01-04/test02/
test02-0250-7.xml
MD5SUM7edaebac28aceb5d9a3e91647880067c
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 benchmark2.36264
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
-2244 2428 2828 -2888 -2648 -2344 -2488 -2344 -2544 -2916 -2360 2528 2860 -2788 -2352 2676 2812 2916 -2644 -2392 2400 -2604 2748 -2492 -2820 2756 -2480 -2352 -2700 -2848 2852 -2656 2284 -2476 2416 -2652 -2232 -2392 -2272 2768 -2676 2820 2636 -2796 2640 -2300 -2352 2324 2788 -2444 2260 -2308 -2484 -2376 -2688 -2876 2400 -2468 -2236 2440 2812 -2404 -2828 -2532 2340 -2840 2876 -2668 -2876 -2476 -2544 -2684 -2552 -2596 2440 -2636 -2876 -2352 -2708 -2720 2520 -2916 2832 -2260 2596 2348 -2516 -2624 2656 -2316 2304 -2436 2780 2888 2564 -2580 2800 2596 -2504 -2916 -2276 -2332 2632 -2848 -2556 -2276 -2648 -2364 2508 -2868 2680 2896 -2620 -2720 -2828 -2368 2496 -2420 2772 2384 -2876 2648 -2260 -2760 2820 -2448 -2620 -2696 2536 2828 -2644 2784 2504 -2372 -2560 -2868 -2312 2600 -2744 -2440 -2328 -2848 2892 -2544 -2400 -2592 2220 -2500 -2696 -2352 2516 -2392 -2316 -2272 -2688 2260 -2580 -2232 -2916 -2572 -2372 -2556 -2532 -2604 2632 -2876 2452 -2336 -2244 -2820 2636 -2220 -2560 2220 -2692 -2480 -2236 2780 2668 -2312 2852 2284 -2672 -2468 -2352 -2300 -2392 -2648 2780 2588 2808 -2256 -2384 -2688 -2688 2548 -2520 2444 -2220 -2824 -2360 2424 -2320 -2868 -2356 -2448 2572 -2436 2584 -2876 -2540 2636 -2680 2376 -2440 2564 -2672 2524 -2488 2628 -2220 -2352 -2332 -2556 -2808 -2568 -2380 -2704 2580 -2392 2664 -2856 2916 -2296 2660 2260 -2640 -2480 2540 -2456 -2496 -2356 2520 -2648 2876 2916 2792 2260 -2916 -2688

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-207277-1168293856 -o ROOT/results/node17/solver-207277-1168293856 -C 1800 -M 900 /tmp/evaluation/207277-1168293856/solver /tmp/evaluation/207277-1168293856/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: 1.06 1.14 1.05 5/83 26286
/proc/meminfo: memFree=1481560/2055920 swapFree=4192812/4192956
[pid=26285] ppid=26277 vsize=5352 CPUtime=0
/proc/26285/stat : 26285 (solver) S 26277 26285 19807 0 -1 4194304 295 0 0 0 0 0 0 0 18 0 1 0 177780713 5480448 232 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/26285/statm: 1338 232 194 169 0 49 0
[pid=26287] ppid=26285 vsize=0 CPUtime=0
/proc/26287/stat : 26287 (solver) D 26285 26285 19807 0 -1 4194372 26 0 0 0 0 0 0 0 18 0 1 0 177780713 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 65538 18446744072100051646 0 0 17 1 0 0
/proc/26287/statm: 0 0 0 0 0 0 0
[pid=26288] ppid=26285 vsize=0 CPUtime=0
/proc/26288/stat : 26288 (grep) D 26285 26285 19807 0 -1 4194308 164 0 0 0 0 0 0 0 21 0 1 0 177780713 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 0 18446744072100051646 0 0 17 1 0 0
/proc/26288/statm: 0 0 0 0 0 0 0

[startup+0.102973 s]
/proc/loadavg: 1.06 1.14 1.05 5/83 26286
/proc/meminfo: memFree=1481560/2055920 swapFree=4192812/4192956
[pid=26285] ppid=26277 vsize=5352 CPUtime=0.05
/proc/26285/stat : 26285 (solver) S 26277 26285 19807 0 -1 4194304 376 2274 0 0 0 0 4 1 17 0 1 0 177780713 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/26285/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 5352

[startup+0.511011 s]
/proc/loadavg: 1.06 1.14 1.05 5/83 26286
/proc/meminfo: memFree=1481560/2055920 swapFree=4192812/4192956
[pid=26285] ppid=26277 vsize=5352 CPUtime=0.05
/proc/26285/stat : 26285 (solver) S 26277 26285 19807 0 -1 4194304 376 2274 0 0 0 0 4 1 17 0 1 0 177780713 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/26285/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 5352

[startup+1.3321 s]
/proc/loadavg: 1.06 1.14 1.05 2/82 26301
/proc/meminfo: memFree=1475488/2055920 swapFree=4192812/4192956
[pid=26285] ppid=26277 vsize=5352 CPUtime=0.91
/proc/26285/stat : 26285 (solver) S 26277 26285 19807 0 -1 4194304 396 6541 0 0 0 0 34 57 16 0 1 0 177780713 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 245482709828 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/26285/statm: 1338 242 203 169 0 49 0
[pid=26301] ppid=26285 vsize=10240 CPUtime=0.36
/proc/26301/stat : 26301 (standalone) R 26285 26285 19807 0 -1 4194304 1972 0 0 0 23 13 0 0 20 0 1 0 177780809 10485760 1945 18446744073709551615 134512640 134775488 4294956880 18446744073709551615 134554211 0 0 4096 0 0 0 0 17 0 0 0
/proc/26301/statm: 2560 1945 136 64 0 1875 0
Current children cumulated CPU time (s) 1.27
Current children cumulated vsize (KiB) 15592

Child status: 0
Real time (s): 2.40635
CPU time (s): 2.36264
CPU user time (s): 1.62675
CPU system time (s): 0.735888
CPU usage (%): 98.1834
Max. virtual memory (cumulated for all children) (KiB): 15600

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.62675
system time used= 0.735888
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8997
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= 129
involuntary context switches= 120

runsolver used 0.000999 s user time and 0.015997 s system time

The end

Launcher Data (download as text)

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


IDJOB= 207277
IDBENCH= 4280
FILE ID= node17/207277-1168293856

PBS_JOBID= 3501833

Free space on /tmp= 66305 MiB

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

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  7edaebac28aceb5d9a3e91647880067c

RANDOM SEED= 391913428

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:       1474072 kB
Buffers:         79068 kB
Cached:         367284 kB
SwapCached:          0 kB
Active:         323004 kB
Inactive:       189368 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1474072 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           23856 kB
Writeback:           0 kB
Mapped:          86204 kB
Slab:            54256 kB
Committed_AS:  5153648 kB
PageTables:       2252 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= 66303 MiB



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