Trace number 268371

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.28859 9.38263

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/node1/watcher-268371-1168978729 -o ROOT/results/node1/solver-268371-1168978729 -C 1800 -M 900 /tmp/evaluation/268371-1168978729/VALCSP /tmp/evaluation/268371-1168978729/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.88 1.68 1.02 5/86 31850
/proc/meminfo: memFree=1616152/2055920 swapFree=4165612/4192956
[pid=31849] ppid=31847 vsize=2128 CPUtime=0
/proc/31849/stat : 31849 (VALCSP) R 31847 31849 31678 0 -1 4194304 264 0 0 0 0 0 0 0 20 0 1 0 246268671 2179072 242 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134533506 0 0 4096 0 0 0 0 17 1 0 0
/proc/31849/statm: 532 242 64 8 0 204 0

[startup+0.104939 s]
/proc/loadavg: 1.88 1.68 1.02 5/86 31850
/proc/meminfo: memFree=1616152/2055920 swapFree=4165612/4192956
[pid=31849] ppid=31847 vsize=30112 CPUtime=0.09
/proc/31849/stat : 31849 (VALCSP) R 31847 31849 31678 0 -1 4194304 7277 0 0 0 7 2 0 0 20 0 1 0 246268671 30834688 7255 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529177 0 0 4096 0 0 0 0 17 1 0 0
/proc/31849/statm: 7528 7255 64 8 0 7200 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 30112

[startup+0.512985 s]
/proc/loadavg: 1.88 1.68 1.02 5/86 31850
/proc/meminfo: memFree=1616152/2055920 swapFree=4165612/4192956
[pid=31849] ppid=31847 vsize=70504 CPUtime=0.5
/proc/31849/stat : 31849 (VALCSP) R 31847 31849 31678 0 -1 4194304 17354 0 0 0 43 7 0 0 24 0 1 0 246268671 72196096 17332 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528607 0 0 4096 0 0 0 0 17 1 0 0
/proc/31849/statm: 17626 17332 64 8 0 17298 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 70504

[startup+1.33408 s]
/proc/loadavg: 1.88 1.68 1.02 3/86 31850
/proc/meminfo: memFree=1486808/2055920 swapFree=4165612/4192956
[pid=31849] ppid=31847 vsize=151024 CPUtime=1.31
/proc/31849/stat : 31849 (VALCSP) R 31847 31849 31678 0 -1 4194304 37508 0 0 0 115 16 0 0 25 0 1 0 246268671 154648576 37486 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528582 0 0 4096 0 0 0 0 17 1 0 0
/proc/31849/statm: 37756 37486 64 8 0 37428 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 151024

[startup+2.97127 s]
/proc/loadavg: 1.88 1.68 1.02 3/86 31850
/proc/meminfo: memFree=1375512/2055920 swapFree=4165612/4192956
[pid=31849] ppid=31847 vsize=311272 CPUtime=2.93
/proc/31849/stat : 31849 (VALCSP) R 31847 31849 31678 0 -1 4194304 77570 0 0 0 261 32 0 0 25 0 1 0 246268671 318742528 77548 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134529232 0 0 4096 0 0 0 0 17 1 0 0
/proc/31849/statm: 77818 77548 64 8 0 77490 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 311272

[startup+6.25966 s]
/proc/loadavg: 1.89 1.69 1.02 3/86 31850
/proc/meminfo: memFree=1042200/2055920 swapFree=4165612/4192956
[pid=31849] ppid=31847 vsize=634672 CPUtime=6.19
/proc/31849/stat : 31849 (VALCSP) R 31847 31849 31678 0 -1 4194304 158431 0 0 0 553 66 0 0 25 0 1 0 246268671 649904128 158409 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528766 0 0 4096 0 0 0 0 17 1 0 0
/proc/31849/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.23301 s]
/proc/loadavg: 1.90 1.69 1.02 3/86 31850
/proc/meminfo: memFree=686936/2055920 swapFree=4165612/4192956
[pid=31849] ppid=31847 vsize=928636 CPUtime=9.14
/proc/31849/stat : 31849 (VALCSP) R 31847 31849 31678 0 -1 4194304 231919 0 0 0 816 98 0 0 25 0 1 0 246268671 950923264 231897 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528639 0 0 4096 0 0 0 0 17 1 0 0
/proc/31849/statm: 232159 231897 64 8 0 231831 0
Current children cumulated CPU time (s) 9.14
Current children cumulated vsize (KiB) 928636

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

Child ended because it received signal 15 (SIGTERM)
Real time (s): 9.38263
CPU time (s): 9.28859
CPU user time (s): 8.16476
CPU system time (s): 1.12383
CPU usage (%): 98.9977
Max. virtual memory (cumulated for all children) (KiB): 928636

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

runsolver used 0.020996 s user time and 0.030995 s system time

The end



Launcher Data (download as text)




Begin job on node1 on Tue Jan 16 20:18:49 UTC 2007


IDJOB= 268371
IDBENCH= 3995
IDSOLVER= 90
FILE ID= node1/268371-1168978729

PBS_JOBID= 3565964

Free space on /tmp= 66564 MiB

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

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  cf4c14e973e5eac4065be1e42f44f4a4

RANDOM SEED= 714368112

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.234
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.234
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:       1616632 kB
Buffers:         48372 kB
Cached:         272220 kB
SwapCached:       3768 kB
Active:         183160 kB
Inactive:       182608 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1616632 kB
SwapTotal:     4192956 kB
SwapFree:      4165612 kB
Dirty:             236 kB
Writeback:           0 kB
Mapped:          55804 kB
Slab:            58416 kB
Committed_AS:  7165664 kB
PageTables:       2300 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 node1 on Tue Jan 16 20:18:59 UTC 2007