Trace number 209095

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
VALCSP 3.0SAT 11.2303 11.3399

DiagnosticValue
CHECKS8650260
NODES200

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-4.xml
MD5SUM51d70101c37b283f2266144f11c69f10
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.3108
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints2053
Maximum constraint arity2
Maximum domain size190
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2053
Global constraints used (with number of constraints)

Solver Data (download as text)

11.31	s SATISFIABLE
11.31	v -2612 2424 2584 -2580 -2284 2488 -2480 -2532 -2472 -2280 -2320 -2640 2424 -2416 -2492 -2500 -2628 2552 -2292 -2648 2632 -2548 -2312 -2540 -2556 -2464 2564 -2648 2592 2376 -2632 2472 2616 -2360 2508 2512 -2636 2560 2424 -2452 2556 2332 -2532 -2432 -2424 -2404 -2532 -2612 -2508 -2616 -2476 2572 -2348 2400 -2312 2324 2352 -2468 -2452 -2288 2512 -2336 -2464 -2552 2424 -2440 -2532 -2440 2608 -2336 2588 -2408 2596 -2532 2308 2608 -2312 -2592 -2600 2320 2328 2352 2320 2360 2568 2588 -2580 2596 -2492 -2592 2324 2380 -2572 -2532 2436 2492 -2480 -2512 -2528 2540 2596 2648 -2452 2512 -2532 -2460 2576 2540 -2364 2340 -2436 2280 -2416 -2656 -2348 -2552 -2436 2592 -2400 2568 2476 -2512 2340 -2324 -2404 2320 -2424 2400 2376 2464 -2600 -2552 -2440 2464 -2364 -2492 -2572 -2324 -2628 2608 2280 2580 -2464 2348 -2460 2528 2360 -2604 -2412 -2416 2572 -2604 2520 2440 2644 -2368 2588 2388 -2492 -2628 -2436 -2604 -2572 -2312 2552 -2640 -2492 -2420 2632 -2464 2376 -2612 -2284 -2400 -2352 2356 -2492 -2376 -2396 -2388 -2568 -2296 2624 -2284 -2644 -2608 -2420 -2280 -2620 2400 2476 -2336 -2300 -2592 -2444 -2608 -2376 2476 -2352 -2552 
11.31	d CHECKS 8.65026e+06
11.31	d NODES 200
11.31

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-209095-1168191563 -o ROOT/results/node17/solver-209095-1168191563 -C 1800 -M 900 /tmp/evaluation/209095-1168191563/VALCSP /tmp/evaluation/209095-1168191563/unknown.xml 

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: 2.00 2.02 2.00 5/87 23275
/proc/meminfo: memFree=1604296/2055920 swapFree=4192812/4192956
[pid=23274] ppid=23272 vsize=1732 CPUtime=0
/proc/23274/stat : 23274 (VALCSP) R 23272 23274 22076 0 -1 4194304 175 0 0 0 0 0 0 0 20 0 1 0 167551124 1773568 153 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 3293611 0 0 4096 0 0 0 0 17 1 0 0
/proc/23274/statm: 433 153 62 8 0 105 0

[startup+0.10499 s]
/proc/loadavg: 2.00 2.02 2.00 5/87 23275
/proc/meminfo: memFree=1604296/2055920 swapFree=4192812/4192956
[pid=23274] ppid=23272 vsize=3844 CPUtime=0.09
/proc/23274/stat : 23274 (VALCSP) R 23272 23274 22076 0 -1 4194304 712 0 0 0 9 0 0 0 20 0 1 0 167551124 3936256 690 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530948 0 0 4096 0 0 0 0 17 1 0 0
/proc/23274/statm: 961 690 64 8 0 633 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3844

[startup+0.513032 s]
/proc/loadavg: 2.00 2.02 2.00 5/87 23275
/proc/meminfo: memFree=1604296/2055920 swapFree=4192812/4192956
[pid=23274] ppid=23272 vsize=9784 CPUtime=0.49
/proc/23274/stat : 23274 (VALCSP) R 23272 23274 22076 0 -1 4194304 2197 0 0 0 49 0 0 0 24 0 1 0 167551124 10018816 2175 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530305 0 0 4096 0 0 0 0 17 1 0 0
/proc/23274/statm: 2446 2175 64 8 0 2118 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 9784

[startup+1.33512 s]
/proc/loadavg: 2.00 2.02 2.00 3/87 23275
/proc/meminfo: memFree=1587336/2055920 swapFree=4192812/4192956
[pid=23274] ppid=23272 vsize=21004 CPUtime=1.31
/proc/23274/stat : 23274 (VALCSP) R 23272 23274 22076 0 -1 4194304 4977 0 0 0 130 1 0 0 25 0 1 0 167551124 21508096 4955 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530207 0 0 4096 0 0 0 0 17 1 0 0
/proc/23274/statm: 5251 4955 64 8 0 4923 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 21004

[startup+2.97929 s]
/proc/loadavg: 2.00 2.02 2.00 3/87 23275
/proc/meminfo: memFree=1572296/2055920 swapFree=4192812/4192956
[pid=23274] ppid=23272 vsize=43576 CPUtime=2.94
/proc/23274/stat : 23274 (VALCSP) R 23272 23274 22076 0 -1 4194304 10621 0 0 0 290 4 0 0 25 0 1 0 167551124 44621824 10599 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530945 0 0 4096 0 0 0 0 17 1 0 0
/proc/23274/statm: 10894 10599 64 8 0 10566 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 43576

[startup+6.25863 s]
/proc/loadavg: 2.00 2.02 2.00 3/87 23275
/proc/meminfo: memFree=1526024/2055920 swapFree=4192812/4192956
[pid=23274] ppid=23272 vsize=87400 CPUtime=6.18
/proc/23274/stat : 23274 (VALCSP) R 23272 23274 22076 0 -1 4194304 21599 0 0 0 610 8 0 0 25 0 1 0 167551124 89497600 21577 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530957 0 0 4096 0 0 0 0 17 1 0 0
/proc/23274/statm: 21850 21577 64 8 0 21522 0
Current children cumulated CPU time (s) 6.18
Current children cumulated vsize (KiB) 87400

Child status: 0
Real time (s): 11.3399
CPU time (s): 11.2303
CPU user time (s): 11.0463
CPU system time (s): 0.183972
CPU usage (%): 99.0332
Max. virtual memory (cumulated for all children) (KiB): 155908

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 11.0463
system time used= 0.183972
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 38770
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= 8
involuntary context switches= 242

runsolver used 0.013997 s user time and 0.044993 s system time

The end

Launcher Data (download as text)

Begin job on node17 on Sun Jan  7 17:39:23 UTC 2007


IDJOB= 209095
IDBENCH= 4495
FILE ID= node17/209095-1168191563

PBS_JOBID= 3478968

Free space on /tmp= 66326 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp01-05/fapp01/fapp01-0200-4.xml
COMMAND LINE= /tmp/evaluation/209095-1168191563/VALCSP /tmp/evaluation/209095-1168191563/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-209095-1168191563 -o ROOT/results/node17/solver-209095-1168191563 -C 1800 -M 900  /tmp/evaluation/209095-1168191563/VALCSP /tmp/evaluation/209095-1168191563/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  51d70101c37b283f2266144f11c69f10

RANDOM SEED= 447244850

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:       1604712 kB
Buffers:         67748 kB
Cached:         244372 kB
SwapCached:          0 kB
Active:         191520 kB
Inactive:       197476 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1604712 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             416 kB
Writeback:           0 kB
Mapped:          97100 kB
Slab:            47060 kB
Committed_AS:  4494476 kB
PageTables:       2260 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= 66326 MiB



End job on node17 on Sun Jan  7 17:39:35 UTC 2007