Trace number 204014

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.29658 9.39147

General information on the benchmark

Namedomino/
domino-1000-500.xml
MD5SUMcf4c14e973e5eac4065be1e42f44f4a4
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.061989
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables1000
Number of constraints1000
Maximum constraint arity2
Maximum domain size500
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/node6/watcher-204014-1168165168 -o ROOT/results/node6/solver-204014-1168165168 -C 1800 -M 900 /tmp/evaluation/204014-1168165168/VALCSP /tmp/evaluation/204014-1168165168/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: 1.92 1.99 1.99 5/88 7703
/proc/meminfo: memFree=1443096/2055924 swapFree=4165672/4192956
[pid=7702] ppid=7700 vsize=2920 CPUtime=0
/proc/7702/stat : 7702 (VALCSP) R 7700 7702 7006 0 -1 4194304 460 0 0 0 0 0 0 0 21 0 1 0 164912388 2990080 438 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 2623099 0 0 4096 0 0 0 0 17 1 0 0
/proc/7702/statm: 730 438 62 8 0 402 0

[startup+0.105632 s]
/proc/loadavg: 1.92 1.99 1.99 5/88 7703
/proc/meminfo: memFree=1443096/2055924 swapFree=4165672/4192956
[pid=7702] ppid=7700 vsize=30112 CPUtime=0.09
/proc/7702/stat : 7702 (VALCSP) R 7700 7702 7006 0 -1 4194304 7277 0 0 0 6 3 0 0 21 0 1 0 164912388 30834688 7255 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530793 0 0 4096 0 0 0 0 17 1 0 0
/proc/7702/statm: 7528 7255 64 8 0 7200 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 30112

[startup+0.513681 s]
/proc/loadavg: 1.92 1.99 1.99 5/88 7703
/proc/meminfo: memFree=1443096/2055924 swapFree=4165672/4192956
[pid=7702] ppid=7700 vsize=69448 CPUtime=0.5
/proc/7702/stat : 7702 (VALCSP) R 7700 7702 7006 0 -1 4194304 17115 0 0 0 43 7 0 0 24 0 1 0 164912388 71114752 17093 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 2623099 0 0 4096 0 0 0 0 17 1 0 0
/proc/7702/statm: 17362 17093 64 8 0 17034 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 69448

[startup+1.33477 s]
/proc/loadavg: 1.92 1.99 1.99 3/88 7703
/proc/meminfo: memFree=1314776/2055924 swapFree=4165672/4192956
[pid=7702] ppid=7700 vsize=150100 CPUtime=1.3
/proc/7702/stat : 7702 (VALCSP) R 7700 7702 7006 0 -1 4194304 37262 0 0 0 114 16 0 0 25 0 1 0 164912388 153702400 37240 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134531019 0 0 4096 0 0 0 0 17 1 0 0
/proc/7702/statm: 37525 37240 64 8 0 37197 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 150100

[startup+2.97197 s]
/proc/loadavg: 1.93 1.99 1.99 3/88 7703
/proc/meminfo: memFree=1203416/2055924 swapFree=4165672/4192956
[pid=7702] ppid=7700 vsize=311272 CPUtime=2.94
/proc/7702/stat : 7702 (VALCSP) R 7700 7702 7006 0 -1 4194304 77570 0 0 0 260 34 0 0 25 0 1 0 164912388 318742528 77548 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530249 0 0 4096 0 0 0 0 17 1 0 0
/proc/7702/statm: 77818 77548 64 8 0 77490 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 311272

[startup+6.25535 s]
/proc/loadavg: 1.93 1.99 1.99 3/88 7703
/proc/meminfo: memFree=869528/2055924 swapFree=4165672/4192956
[pid=7702] ppid=7700 vsize=634672 CPUtime=6.19
/proc/7702/stat : 7702 (VALCSP) R 7700 7702 7006 0 -1 4194304 158431 0 0 0 552 67 0 0 25 0 1 0 164912388 649904128 158409 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530249 0 0 4096 0 0 0 0 17 1 0 0
/proc/7702/statm: 158668 158409 64 8 0 158340 0
Current children cumulated CPU time (s) 6.19
Current children cumulated vsize (KiB) 634672



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+9.2387 s]
/proc/loadavg: 1.93 1.99 1.99 3/89 7704
/proc/meminfo: memFree=511952/2055924 swapFree=4165672/4192956
[pid=7702] ppid=7700 vsize=930616 CPUtime=9.14
/proc/7702/stat : 7702 (VALCSP) R 7700 7702 7006 0 -1 4194304 232410 0 0 0 814 100 0 0 25 0 1 0 164912388 952950784 232388 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530227 0 0 4096 0 0 0 0 17 1 0 0
/proc/7702/statm: 232654 232388 64 8 0 232326 0
Current children cumulated CPU time (s) 9.14
Current children cumulated vsize (KiB) 930616

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

Child ended because it received signal 15 (SIGTERM)
Real time (s): 9.39147
CPU time (s): 9.29658
CPU user time (s): 8.14476
CPU system time (s): 1.15182
CPU usage (%): 98.9896
Max. virtual memory (cumulated for all children) (KiB): 930616

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 8.14476
system time used= 1.15182
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 232410
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= 207

runsolver used 0.020996 s user time and 0.033994 s system time

The end



Launcher Data (download as text)




Begin job on node6 on Sun Jan  7 10:19:30 UTC 2007


IDJOB= 204014
IDBENCH= 3995
FILE ID= node6/204014-1168165168

PBS_JOBID= 3478303

Free space on /tmp= 66551 MiB

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

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  cf4c14e973e5eac4065be1e42f44f4a4

RANDOM SEED= 101564592

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.240
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.240
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:      2055924 kB
MemFree:       1443576 kB
Buffers:         63336 kB
Cached:         410376 kB
SwapCached:       2424 kB
Active:         122288 kB
Inactive:       406196 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1443576 kB
SwapTotal:     4192956 kB
SwapFree:      4165672 kB
Dirty:             300 kB
Writeback:           0 kB
Mapped:          65764 kB
Slab:            68648 kB
Committed_AS:  4701532 kB
PageTables:       2364 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= 66551 MiB



End job on node6 on Sun Jan  7 10:19:39 UTC 2007