Trace number 268381

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) 8.91564 8.96225

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/node75/watcher-268381-1168978753 -o ROOT/results/node75/solver-268381-1168978753 -C 1800 -M 900 /tmp/evaluation/268381-1168978753/VALCSP /tmp/evaluation/268381-1168978753/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.02 1.25 0.89 3/73 25391
/proc/meminfo: memFree=1281368/2055920 swapFree=4184548/4192956
[pid=25390] ppid=25388 vsize=140 CPUtime=0
/proc/25390/stat : 25390 (VALCSP) R 25388 25390 25162 0 -1 4194304 38 0 0 0 0 0 0 0 23 0 1 0 246274670 143360 23 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 6734628 0 0 4096 0 0 0 0 17 1 0 0
/proc/25390/statm: 35 23 18 8 0 2 0

[startup+0.103232 s]
/proc/loadavg: 1.02 1.25 0.89 3/73 25391
/proc/meminfo: memFree=1281368/2055920 swapFree=4184548/4192956
[pid=25390] ppid=25388 vsize=34072 CPUtime=0.08
/proc/25390/stat : 25390 (VALCSP) R 25388 25390 25162 0 -1 4194304 8277 0 0 0 4 4 0 0 23 0 1 0 246274670 34889728 8255 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528624 0 0 4096 0 0 0 0 17 0 0 0
/proc/25390/statm: 8518 8255 64 8 0 8190 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 34072

[startup+0.515277 s]
/proc/loadavg: 1.02 1.25 0.89 3/73 25391
/proc/meminfo: memFree=1281368/2055920 swapFree=4184548/4192956
[pid=25390] ppid=25388 vsize=76840 CPUtime=0.5
/proc/25390/stat : 25390 (VALCSP) R 25388 25390 25162 0 -1 4194304 18945 0 0 0 40 10 0 0 25 0 1 0 246274670 78684160 18923 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528697 0 0 4096 0 0 0 0 17 0 0 0
/proc/25390/statm: 19210 18923 64 8 0 18882 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 76840

[startup+1.34337 s]
/proc/loadavg: 1.10 1.26 0.90 3/73 25391
/proc/meminfo: memFree=1145304/2055920 swapFree=4184548/4192956
[pid=25390] ppid=25388 vsize=159604 CPUtime=1.32
/proc/25390/stat : 25390 (VALCSP) R 25388 25390 25162 0 -1 4194304 39652 0 0 0 111 21 0 0 25 0 1 0 246274670 163434496 39630 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528577 0 0 4096 0 0 0 0 17 0 0 0
/proc/25390/statm: 39901 39630 64 8 0 39573 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 159604

[startup+2.98457 s]
/proc/loadavg: 1.10 1.26 0.90 3/73 25391
/proc/meminfo: memFree=1030552/2055920 swapFree=4184548/4192956
[pid=25390] ppid=25388 vsize=322756 CPUtime=2.97
/proc/25390/stat : 25390 (VALCSP) R 25388 25390 25162 0 -1 4194304 80442 0 0 0 255 42 0 0 25 0 1 0 246274670 330502144 80420 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528617 0 0 4096 0 0 0 0 17 0 0 0
/proc/25390/statm: 80689 80420 64 8 0 80361 0
Current children cumulated CPU time (s) 2.97
Current children cumulated vsize (KiB) 322756

[startup+6.26395 s]
/proc/loadavg: 1.10 1.26 0.90 3/70 25399
/proc/meminfo: memFree=873904/2055920 swapFree=4184548/4192956
[pid=25390] ppid=25388 vsize=654076 CPUtime=6.22
/proc/25390/stat : 25390 (VALCSP) R 25388 25390 25162 0 -1 4194304 163274 0 0 0 539 83 0 0 25 0 1 0 246274670 669773824 163252 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528582 0 0 4096 0 0 0 0 17 0 0 0
/proc/25390/statm: 163519 163252 64 8 0 163191 0
Current children cumulated CPU time (s) 6.22
Current children cumulated vsize (KiB) 654076



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+8.82524 s]
/proc/loadavg: 1.09 1.25 0.90 2/68 25403
/proc/meminfo: memFree=538176/2055920 swapFree=4184548/4192956
[pid=25390] ppid=25388 vsize=925204 CPUtime=8.77
/proc/25390/stat : 25390 (VALCSP) R 25388 25390 25162 0 -1 4194304 231045 0 0 0 766 111 0 0 25 0 1 0 246274670 947408896 231023 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134529232 0 0 4096 0 0 0 0 17 1 0 0
/proc/25390/statm: 231301 231023 64 8 0 230973 0
Current children cumulated CPU time (s) 8.77
Current children cumulated vsize (KiB) 925204

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

Child ended because it received signal 15 (SIGTERM)
Real time (s): 8.96225
CPU time (s): 8.91564
CPU user time (s): 7.66683
CPU system time (s): 1.24881
CPU usage (%): 99.48
Max. virtual memory (cumulated for all children) (KiB): 925204

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

runsolver used 0.005999 s user time and 0.034994 s system time

The end



Launcher Data (download as text)




Begin job on node75 on Tue Jan 16 20:19:13 UTC 2007


IDJOB= 268381
IDBENCH= 4005
IDSOLVER= 90
FILE ID= node75/268381-1168978753

PBS_JOBID= 3566210

Free space on /tmp= 66564 MiB

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

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  6727656a2a127d0a117213d0dafe2f9e

RANDOM SEED= 86049180

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.218
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.218
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1281784 kB
Buffers:         43792 kB
Cached:         461444 kB
SwapCached:       2452 kB
Active:         288668 kB
Inactive:       412628 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1281784 kB
SwapTotal:     4192956 kB
SwapFree:      4184548 kB
Dirty:             712 kB
Writeback:           0 kB
Mapped:         203392 kB
Slab:            57856 kB
Committed_AS:  5288684 kB
PageTables:       2100 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= 66564 MiB



End job on node75 on Tue Jan 16 20:19:23 UTC 2007