Trace number 268380

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.02063 9.07567

General information on the benchmark

Namedomino/
domino-1000-1000.xml
MD5SUM96861b95f17b67d8ffe8959ec5be8494
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.06199
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables1000
Number of constraints1000
Maximum constraint arity2
Maximum domain size1000
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/node12/watcher-268380-1168978750 -o ROOT/results/node12/solver-268380-1168978750 -C 1800 -M 900 /tmp/evaluation/268380-1168978750/VALCSP /tmp/evaluation/268380-1168978750/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.89 1.83 1.16 3/86 27810
/proc/meminfo: memFree=1375448/2055920 swapFree=4160348/4192956
[pid=27809] ppid=27807 vsize=18540 CPUtime=0
/proc/27809/stat : 27809 (runsolver) R 27807 27809 27753 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 246270038 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 252429528359 0 0 4096 24578 0 0 0 17 1 0 0
/proc/27809/statm: 4635 279 244 17 0 2626 0

[startup+0.102175 s]
/proc/loadavg: 1.89 1.83 1.16 3/86 27810
/proc/meminfo: memFree=1375448/2055920 swapFree=4160348/4192956
[pid=27809] ppid=27807 vsize=40804 CPUtime=0.09
/proc/27809/stat : 27809 (VALCSP) R 27807 27809 27753 0 -1 4194304 9958 0 0 0 6 3 0 0 20 0 1 0 246270038 41783296 9936 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528607 0 0 4096 0 0 0 0 17 1 0 0
/proc/27809/statm: 10201 9936 64 8 0 9873 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 40804

[startup+0.51024 s]
/proc/loadavg: 1.89 1.83 1.16 3/86 27810
/proc/meminfo: memFree=1375448/2055920 swapFree=4160348/4192956
[pid=27809] ppid=27807 vsize=80008 CPUtime=0.5
/proc/27809/stat : 27809 (VALCSP) R 27807 27809 27753 0 -1 4194304 19755 0 0 0 43 7 0 0 24 0 1 0 246270038 81928192 19733 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529416 0 0 4096 0 0 0 0 17 1 0 0
/proc/27809/statm: 20002 19733 64 8 0 19674 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 80008

[startup+1.33139 s]
/proc/loadavg: 1.89 1.83 1.16 3/86 27810
/proc/meminfo: memFree=1233816/2055920 swapFree=4160348/4192956
[pid=27809] ppid=27807 vsize=162376 CPUtime=1.32
/proc/27809/stat : 27809 (VALCSP) R 27807 27809 27753 0 -1 4194304 40327 0 0 0 116 16 0 0 25 0 1 0 246270038 166273024 40305 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529272 0 0 4096 0 0 0 0 17 1 0 0
/proc/27809/statm: 40594 40305 64 8 0 40266 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 162376

[startup+2.97468 s]
/proc/loadavg: 1.89 1.83 1.16 3/86 27810
/proc/meminfo: memFree=1119896/2055920 swapFree=4160348/4192956
[pid=27809] ppid=27807 vsize=326980 CPUtime=2.95
/proc/27809/stat : 27809 (VALCSP) R 27807 27809 27753 0 -1 4194304 81473 0 0 0 263 32 0 0 25 0 1 0 246270038 334827520 81451 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528591 0 0 4096 0 0 0 0 17 1 0 0
/proc/27809/statm: 81745 81451 64 8 0 81417 0
Current children cumulated CPU time (s) 2.95
Current children cumulated vsize (KiB) 326980

[startup+6.25428 s]
/proc/loadavg: 1.89 1.84 1.16 3/86 27810
/proc/meminfo: memFree=782240/2055920 swapFree=4160348/4192956
[pid=27809] ppid=27807 vsize=656056 CPUtime=6.22
/proc/27809/stat : 27809 (VALCSP) R 27807 27809 27753 0 -1 4194304 163765 0 0 0 554 68 0 0 25 0 1 0 246270038 671801344 163743 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528653 0 0 4096 0 0 0 0 17 1 0 0
/proc/27809/statm: 164014 163743 64 8 0 163686 0
Current children cumulated CPU time (s) 6.22
Current children cumulated vsize (KiB) 656056



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+8.92476 s]
/proc/loadavg: 1.90 1.84 1.17 3/86 27810
/proc/meminfo: memFree=452448/2055920 swapFree=4160348/4192956
[pid=27809] ppid=27807 vsize=922564 CPUtime=8.88
/proc/27809/stat : 27809 (VALCSP) R 27807 27809 27753 0 -1 4194304 230382 0 0 0 795 93 0 0 25 0 1 0 246270038 944705536 230360 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528695 0 0 4096 0 0 0 0 17 1 0 0
/proc/27809/statm: 230641 230360 64 8 0 230313 0
Current children cumulated CPU time (s) 8.88
Current children cumulated vsize (KiB) 922564

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

Child ended because it received signal 15 (SIGTERM)
Real time (s): 9.07567
CPU time (s): 9.02063
CPU user time (s): 7.95179
CPU system time (s): 1.06884
CPU usage (%): 99.3935
Max. virtual memory (cumulated for all children) (KiB): 922564

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

runsolver used 0.011998 s user time and 0.042993 s system time

The end



Launcher Data (download as text)




Begin job on node12 on Tue Jan 16 20:19:10 UTC 2007


IDJOB= 268380
IDBENCH= 4004
IDSOLVER= 90
FILE ID= node12/268380-1168978750

PBS_JOBID= 3565970

Free space on /tmp= 66564 MiB

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

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  96861b95f17b67d8ffe8959ec5be8494

RANDOM SEED= 637835166

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.265
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.265
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:       1375928 kB
Buffers:         44612 kB
Cached:         146268 kB
SwapCached:       5164 kB
Active:         569700 kB
Inactive:        48044 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1375928 kB
SwapTotal:     4192956 kB
SwapFree:      4160348 kB
Dirty:             412 kB
Writeback:           0 kB
Mapped:         436976 kB
Slab:            46556 kB
Committed_AS:  7364640 kB
PageTables:       2796 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 node12 on Tue Jan 16 20:19:20 UTC 2007