Trace number 209127

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.6202 11.6823

DiagnosticValue
CHECKS9047680
NODES200

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-6.xml
MD5SUMe899673b69f535aa8fc65e273d782cac
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.37279
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.65	s SATISFIABLE
11.65	v -2640 2424 2584 -2488 2280 2512 -2472 -2524 -2484 -2312 2352 -2596 2452 -2368 -2484 2496 2616 2512 -2284 -2648 2580 -2540 -2320 2536 -2632 -2460 2600 -2648 2592 2408 2584 2488 -2620 -2348 2500 -2552 -2612 2520 -2424 -2440 2548 2324 2492 -2444 -2424 -2308 2428 -2616 -2424 -2544 -2492 -2616 -2340 -2460 -2320 2320 2368 -2464 2408 -2320 -2528 2352 -2464 -2512 -2420 -2480 -2492 -2380 2608 -2336 -2656 -2484 -2572 -2532 2296 -2588 -2292 -2620 2636 2328 2280 2280 2280 2420 2656 -2548 -2648 -2592 -2480 -2624 2312 2420 2484 -2524 2440 2452 -2520 -2484 -2616 -2656 2588 2628 -2492 -2508 -2532 -2500 2584 2608 -2324 -2356 -2468 -2288 -2384 2580 -2348 -2444 -2440 2572 -2420 2656 2480 -2552 -2460 -2348 2332 2280 2440 -2452 -2360 -2480 2600 2584 -2432 -2464 -2372 2532 -2600 -2364 2556 -2608 2320 -2616 -2492 2336 2420 2552 2412 -2656 2368 -2400 -2656 2560 2560 -2412 -2556 -2524 2596 -2388 -2452 -2588 -2452 2596 2468 2408 2532 -2640 -2492 -2460 2632 -2464 2376 -2656 -2352 -2388 -2332 2372 -2572 -2376 -2412 -2380 2648 -2392 2624 -2308 -2616 -2608 2460 2320 2528 -2452 -2428 -2416 -2316 -2624 -2348 -2616 -2424 2480 -2280 -2548 
11.65	d CHECKS 9.04768e+06
11.65	d NODES 200
11.65

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/node38/watcher-209127-1168191653 -o ROOT/results/node38/solver-209127-1168191653 -C 1800 -M 900 /tmp/evaluation/209127-1168191653/VALCSP /tmp/evaluation/209127-1168191653/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.65 2.12 1.61 3/81 21043
/proc/meminfo: memFree=1273800/2055920 swapFree=4192812/4192956
[pid=21042] ppid=21040 vsize=1600 CPUtime=0
/proc/21042/stat : 21042 (VALCSP) R 21040 21042 20681 0 -1 4194304 140 0 0 0 0 0 0 0 20 0 1 0 167564958 1638400 118 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 9041531 0 0 4096 0 0 0 0 17 1 0 0
/proc/21042/statm: 400 118 62 8 0 72 0

[startup+0.104654 s]
/proc/loadavg: 2.65 2.12 1.61 3/81 21043
/proc/meminfo: memFree=1273800/2055920 swapFree=4192812/4192956
[pid=21042] ppid=21040 vsize=3580 CPUtime=0.09
/proc/21042/stat : 21042 (VALCSP) R 21040 21042 20681 0 -1 4194304 640 0 0 0 9 0 0 0 20 0 1 0 167564958 3665920 618 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134540282 0 0 4096 0 0 0 0 17 1 0 0
/proc/21042/statm: 895 618 64 8 0 567 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3580

[startup+0.516727 s]
/proc/loadavg: 2.65 2.12 1.61 3/81 21043
/proc/meminfo: memFree=1273800/2055920 swapFree=4192812/4192956
[pid=21042] ppid=21040 vsize=9652 CPUtime=0.5
/proc/21042/stat : 21042 (VALCSP) R 21040 21042 20681 0 -1 4194304 2161 0 0 0 49 1 0 0 24 0 1 0 167564958 9883648 2139 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530258 0 0 4096 0 0 0 0 17 1 0 0
/proc/21042/statm: 2413 2139 64 8 0 2085 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 9652

[startup+1.33989 s]
/proc/loadavg: 2.60 2.12 1.62 3/81 21043
/proc/meminfo: memFree=1257288/2055920 swapFree=4192812/4192956
[pid=21042] ppid=21040 vsize=20608 CPUtime=1.32
/proc/21042/stat : 21042 (VALCSP) R 21040 21042 20681 0 -1 4194304 4883 0 0 0 130 2 0 0 25 0 1 0 167564958 21102592 4861 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530960 0 0 4096 0 0 0 0 17 1 0 0
/proc/21042/statm: 5152 4861 64 8 0 4824 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 20608

[startup+2.97721 s]
/proc/loadavg: 2.60 2.12 1.62 3/81 21043
/proc/meminfo: memFree=1242632/2055920 swapFree=4192812/4192956
[pid=21042] ppid=21040 vsize=42520 CPUtime=2.95
/proc/21042/stat : 21042 (VALCSP) R 21040 21042 20681 0 -1 4194304 10378 0 0 0 289 6 0 0 25 0 1 0 167564958 43540480 10356 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530192 0 0 4096 0 0 0 0 17 1 0 0
/proc/21042/statm: 10630 10356 64 8 0 10302 0
Current children cumulated CPU time (s) 2.95
Current children cumulated vsize (KiB) 42520

[startup+6.26385 s]
/proc/loadavg: 2.55 2.12 1.62 3/81 21043
/proc/meminfo: memFree=1195088/2055920 swapFree=4192812/4192956
[pid=21042] ppid=21040 vsize=85552 CPUtime=6.22
/proc/21042/stat : 21042 (VALCSP) R 21040 21042 20681 0 -1 4194304 21122 0 0 0 611 11 0 0 25 0 1 0 167564958 87605248 21100 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530218 0 0 4096 0 0 0 0 17 1 0 0
/proc/21042/statm: 21388 21100 64 8 0 21060 0
Current children cumulated CPU time (s) 6.22
Current children cumulated vsize (KiB) 85552

Child status: 0
Real time (s): 11.6823
CPU time (s): 11.6202
CPU user time (s): 11.3763
CPU system time (s): 0.243962
CPU usage (%): 99.4686
Max. virtual memory (cumulated for all children) (KiB): 155908

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 11.3763
system time used= 0.243962
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= 133

runsolver used 0.018997 s user time and 0.040993 s system time

The end

Launcher Data (download as text)

Begin job on node38 on Sun Jan  7 17:40:53 UTC 2007


IDJOB= 209127
IDBENCH= 4497
FILE ID= node38/209127-1168191653

PBS_JOBID= 3479271

Free space on /tmp= 66513 MiB

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

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  e899673b69f535aa8fc65e273d782cac

RANDOM SEED= 601525600

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.267
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.267
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:       1274408 kB
Buffers:         22556 kB
Cached:         217960 kB
SwapCached:          0 kB
Active:         559320 kB
Inactive:       160532 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1274408 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             340 kB
Writeback:           0 kB
Mapped:         498472 kB
Slab:            46032 kB
Committed_AS:  4397392 kB
PageTables:       2864 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= 66513 MiB



End job on node38 on Sun Jan  7 17:41:05 UTC 2007