Trace number 268378

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.1? (MO) 9.15561 9.16047

General information on the benchmark

Namedomino/
domino-800-800.xml
MD5SUM6472778b62dfa718a441514d3c300120
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.050991
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables800
Number of constraints800
Maximum constraint arity2
Maximum domain size800
Number of constraints which are defined in extension0
Number of constraints which are defined in intension800
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/node61/watcher-268378-1168978748 -o ROOT/results/node61/solver-268378-1168978748 -C 1800 -M 900 /tmp/evaluation/268378-1168978748/VALCSP /tmp/evaluation/268378-1168978748/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.00 0.99 0.65 2/65 20249
/proc/meminfo: memFree=1639048/2055920 swapFree=4191892/4192956
[pid=20248] ppid=20246 vsize=3976 CPUtime=0
/proc/20248/stat : 20248 (VALCSP) R 20246 20248 19616 0 -1 4194304 723 0 0 0 0 0 0 0 18 0 1 0 246272668 4071424 701 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 10819195 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 994 707 64 8 0 666 0

[startup+0.102515 s]
/proc/loadavg: 1.00 0.99 0.65 2/65 20249
/proc/meminfo: memFree=1639048/2055920 swapFree=4191892/4192956
[pid=20248] ppid=20246 vsize=29188 CPUtime=0.09
/proc/20248/stat : 20248 (VALCSP) R 20246 20248 19616 0 -1 4194304 7052 0 0 0 6 3 0 0 18 0 1 0 246272668 29888512 7030 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134529406 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 7297 7030 64 8 0 6969 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 29188

[startup+0.510583 s]
/proc/loadavg: 1.00 0.99 0.65 2/65 20249
/proc/meminfo: memFree=1639048/2055920 swapFree=4191892/4192956
[pid=20248] ppid=20246 vsize=69448 CPUtime=0.5
/proc/20248/stat : 20248 (VALCSP) R 20246 20248 19616 0 -1 4194304 17093 0 0 0 43 7 0 0 21 0 1 0 246272668 71114752 17071 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528607 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 17362 17071 64 8 0 17034 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 69448

[startup+1.33073 s]
/proc/loadavg: 1.00 0.99 0.65 2/65 20249
/proc/meminfo: memFree=1508040/2055920 swapFree=4191892/4192956
[pid=20248] ppid=20246 vsize=152212 CPUtime=1.31
/proc/20248/stat : 20248 (VALCSP) R 20246 20248 19616 0 -1 4194304 37801 0 0 0 116 15 0 0 25 0 1 0 246272668 155865088 37779 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528683 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 38053 37779 64 8 0 37725 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 152212

[startup+2.96801 s]
/proc/loadavg: 1.00 0.99 0.65 2/65 20249
/proc/meminfo: memFree=1394824/2055920 swapFree=4191892/4192956
[pid=20248] ppid=20246 vsize=315364 CPUtime=2.95
/proc/20248/stat : 20248 (VALCSP) R 20246 20248 19616 0 -1 4194304 78589 0 0 0 263 32 0 0 25 0 1 0 246272668 322932736 78567 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528582 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 78841 78567 64 8 0 78513 0
Current children cumulated CPU time (s) 2.95
Current children cumulated vsize (KiB) 315364

[startup+6.24459 s]
/proc/loadavg: 1.00 0.99 0.65 2/65 20249
/proc/meminfo: memFree=1057800/2055920 swapFree=4191892/4192956
[pid=20248] ppid=20246 vsize=644176 CPUtime=6.23
/proc/20248/stat : 20248 (VALCSP) R 20246 20248 19616 0 -1 4194304 160793 0 0 0 557 66 0 0 25 0 1 0 246272668 659636224 160771 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134529272 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 161044 160771 64 8 0 160716 0
Current children cumulated CPU time (s) 6.23
Current children cumulated vsize (KiB) 644176



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+9.01008 s]
/proc/loadavg: 1.00 0.99 0.65 2/65 20249
/proc/meminfo: memFree=715720/2055920 swapFree=4191892/4192956
[pid=20248] ppid=20246 vsize=922828 CPUtime=9
/proc/20248/stat : 20248 (VALCSP) R 20246 20248 19616 0 -1 4194304 230448 0 0 0 805 95 0 0 25 0 1 0 246272668 944975872 230426 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528704 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 230707 230426 64 8 0 230379 0
Current children cumulated CPU time (s) 9
Current children cumulated vsize (KiB) 922828

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

Child ended because it received signal 15 (SIGTERM)
Real time (s): 9.16047
CPU time (s): 9.15561
CPU user time (s): 8.05777
CPU system time (s): 1.09783
CPU usage (%): 99.9469
Max. virtual memory (cumulated for all children) (KiB): 922828

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

runsolver used 0.009998 s user time and 0.026995 s system time

The end



Launcher Data (download as text)




Begin job on node61 on Tue Jan 16 20:19:08 UTC 2007


IDJOB= 268378
IDBENCH= 4002
IDSOLVER= 90
FILE ID= node61/268378-1168978748

PBS_JOBID= 3566134

Free space on /tmp= 66565 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-800-800.xml
COMMAND LINE= /tmp/evaluation/268378-1168978748/VALCSP /tmp/evaluation/268378-1168978748/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node61/watcher-268378-1168978748 -o ROOT/results/node61/solver-268378-1168978748 -C 1800 -M 900  /tmp/evaluation/268378-1168978748/VALCSP /tmp/evaluation/268378-1168978748/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  6472778b62dfa718a441514d3c300120

RANDOM SEED= 947326943

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.259
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.259
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:       1639464 kB
Buffers:         61272 kB
Cached:         285456 kB
SwapCached:        480 kB
Active:         154304 kB
Inactive:       207284 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1639464 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:             252 kB
Writeback:           0 kB
Mapped:          23564 kB
Slab:            41032 kB
Committed_AS:  4927092 kB
PageTables:       1388 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= 66565 MiB



End job on node61 on Tue Jan 16 20:19:17 UTC 2007