Trace number 204174

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.0? (MO) 9.12861 9.18337

General information on the benchmark

Namedomino/
domino-1000-800.xml
MD5SUM6727656a2a127d0a117213d0dafe2f9e
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 benchmark0.063989
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables1000
Number of constraints1000
Maximum constraint arity2
Maximum domain size800
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1000
Global constraints used (with number of constraints)

Solver Data (download as text)



Verifier Data (download as text)




ERROR: Unexpected answer ! (SAT/UNSAT expected)
Got answer: 



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-204174-1168165373 -o ROOT/results/node17/solver-204174-1168165373 -C 1800 -M 900 /tmp/evaluation/204174-1168165373/VALCSP /tmp/evaluation/204174-1168165373/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: 0.76 1.46 1.79 5/97 14646
/proc/meminfo: memFree=1485392/2055920 swapFree=4192812/4192956
[pid=14645] ppid=14643 vsize=2920 CPUtime=0
/proc/14645/stat : 14645 (VALCSP) R 14643 14645 14391 0 -1 4194304 470 0 0 0 0 0 0 0 20 0 1 0 164932348 2990080 448 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 3294843 0 0 4096 0 0 0 0 17 1 0 0
/proc/14645/statm: 730 448 62 8 0 402 0

[startup+0.106153 s]
/proc/loadavg: 0.76 1.46 1.79 5/97 14646
/proc/meminfo: memFree=1485392/2055920 swapFree=4192812/4192956
[pid=14645] ppid=14643 vsize=36316 CPUtime=0.09
/proc/14645/stat : 14645 (VALCSP) R 14643 14645 14391 0 -1 4194304 8829 0 0 0 5 4 0 0 20 0 1 0 164932348 37187584 8807 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134540022 0 0 4096 0 0 0 0 17 1 0 0
/proc/14645/statm: 9079 8807 64 8 0 8751 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 36316

[startup+0.514191 s]
/proc/loadavg: 0.76 1.46 1.79 5/97 14646
/proc/meminfo: memFree=1485392/2055920 swapFree=4192812/4192956
[pid=14645] ppid=14643 vsize=76840 CPUtime=0.5
/proc/14645/stat : 14645 (VALCSP) R 14643 14645 14391 0 -1 4194304 18945 0 0 0 42 8 0 0 23 0 1 0 164932348 78684160 18923 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530362 0 0 4096 0 0 0 0 17 1 0 0
/proc/14645/statm: 19210 18923 64 8 0 18882 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 76840

[startup+1.33528 s]
/proc/loadavg: 0.76 1.46 1.79 3/97 14646
/proc/meminfo: memFree=1347728/2055920 swapFree=4192812/4192956
[pid=14645] ppid=14643 vsize=159604 CPUtime=1.31
/proc/14645/stat : 14645 (VALCSP) R 14643 14645 14391 0 -1 4194304 39652 0 0 0 115 16 0 0 25 0 1 0 164932348 163434496 39630 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530198 0 0 4096 0 0 0 0 17 1 0 0
/proc/14645/statm: 39901 39630 64 8 0 39573 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 159604

[startup+2.97245 s]
/proc/loadavg: 0.76 1.46 1.79 3/97 14646
/proc/meminfo: memFree=1236112/2055920 swapFree=4192812/4192956
[pid=14645] ppid=14643 vsize=322756 CPUtime=2.95
/proc/14645/stat : 14645 (VALCSP) R 14643 14645 14391 0 -1 4194304 80442 0 0 0 261 34 0 0 25 0 1 0 164932348 330502144 80420 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530192 0 0 4096 0 0 0 0 17 1 0 0
/proc/14645/statm: 80689 80420 64 8 0 80361 0
Current children cumulated CPU time (s) 2.95
Current children cumulated vsize (KiB) 322756

[startup+6.25179 s]
/proc/loadavg: 0.86 1.47 1.79 3/97 14646
/proc/meminfo: memFree=898384/2055920 swapFree=4192812/4192956
[pid=14645] ppid=14643 vsize=646552 CPUtime=6.21
/proc/14645/stat : 14645 (VALCSP) R 14643 14645 14391 0 -1 4194304 161391 0 0 0 549 72 0 0 25 0 1 0 164932348 662069248 161369 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530886 0 0 4096 0 0 0 0 17 1 0 0
/proc/14645/statm: 161638 161369 64 8 0 161310 0
Current children cumulated CPU time (s) 6.21
Current children cumulated vsize (KiB) 646552



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+9.03108 s]
/proc/loadavg: 0.86 1.47 1.79 3/97 14646
/proc/meminfo: memFree=565904/2055920 swapFree=4192812/4192956
[pid=14645] ppid=14643 vsize=922696 CPUtime=8.98
/proc/14645/stat : 14645 (VALCSP) R 14643 14645 14391 0 -1 4194304 230418 0 0 0 795 103 0 0 25 0 1 0 164932348 944840704 230396 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530258 0 0 4096 0 0 0 0 17 1 0 0
/proc/14645/statm: 230674 230396 64 8 0 230346 0
Current children cumulated CPU time (s) 8.98
Current children cumulated vsize (KiB) 922696

Sending SIGTERM to process tree (bottom up)
Sleeping 2 seconds

Child ended because it received signal 15 (SIGTERM)
Real time (s): 9.18337
CPU time (s): 9.12861
CPU user time (s): 7.95179
CPU system time (s): 1.17682
CPU usage (%): 99.4037
Max. virtual memory (cumulated for all children) (KiB): 922696

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 7.95179
system time used= 1.17682
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 230418
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= 6
involuntary context switches= 135

runsolver used 0.009998 s user time and 0.043993 s system time

The end



Launcher Data (download as text)




Begin job on node17 on Sun Jan  7 10:22:55 UTC 2007


IDJOB= 204174
IDBENCH= 4005
FILE ID= node17/204174-1168165373

PBS_JOBID= 3478338

Free space on /tmp= 66326 MiB

BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-1000-800.xml
COMMAND LINE= /tmp/evaluation/204174-1168165373/VALCSP /tmp/evaluation/204174-1168165373/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-204174-1168165373 -o ROOT/results/node17/solver-204174-1168165373 -C 1800 -M 900  /tmp/evaluation/204174-1168165373/VALCSP /tmp/evaluation/204174-1168165373/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  6727656a2a127d0a117213d0dafe2f9e

RANDOM SEED= 568075956

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:       1486064 kB
Buffers:         50044 kB
Cached:         109688 kB
SwapCached:          0 kB
Active:         417568 kB
Inactive:        90332 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1486064 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2952 kB
Writeback:           0 kB
Mapped:         377676 kB
Slab:            46216 kB
Committed_AS:  5061668 kB
PageTables:       2872 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 10:23:07 UTC 2007