Trace number 237537

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.0Wrong Cert. 1.15982 1.17757

DiagnosticValue
CHECKS3677420
NODES676

General information on the benchmark

Namehaystacks/
haystacks_26.xml
MD5SUMb92463ea8cbb51f9a3234236cd8f2202
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark31.5232
SatisfiableNO
(Un)Satisfiability was proved
Number of variables676
Number of constraints8475
Maximum constraint arity2
Maximum domain size26
Number of constraints which are defined in extension0
Number of constraints which are defined in intension8475
Global constraints used (with number of constraints)

Solver Data (download as text)

1.16	s SATISFIABLE
1.16	v 0 0 0 0 0 0 0 1 0 0 0 0 2 0 0 3 0 0 1 0 0 1 1 0 1 1 1 1 1 1 0 1 0 0 0 2 6 1 1 2 2 0 2 1 1 2 1 2 3 3 3 0 4 16 1 3 2 2 1 2 2 1 1 2 1 4 2 4 2 3 1 2 5 3 0 3 2 2 3 4 2 2 4 4 3 2 3 3 20 4 1 4 4 3 5 7 4 5 2 2 3 5 6 7 3 5 4 6 4 5 5 1 5 8 3 3 7 6 6 8 6 5 5 2 3 6 6 7 4 5 2 9 3 3 7 4 4 1 8 6 3 9 5 5 7 7 7 4 10 4 8 6 5 7 2 24 8 3 8 6 6 5 5 5 4 6 9 4 6 4 3 4 6 6 7 11 10 5 6 7 7 4 7 7 5 17 3 7 3 8 9 8 8 8 9 6 8 8 4 4 5 5 8 6 10 12 9 9 5 7 7 19 6 7 8 9 10 6 10 8 8 7 5 8 7 9 6 6 10 12 9 10 10 9 11 8 9 9 9 7 8 13 14 10 10 9 15 7 10 9 13 8 9 11 16 11 4 9 10 11 12 10 11 6 11 11 8 9 10 10 11 21 11 12 13 12 11 11 13 11 12 12 10 5 9 12 10 11 13 14 13 13 17 15 6 9 14 14 12 7 7 14 3 15 14 5 7 16 9 12 11 10 11 8 10 13 16 12 12 13 11 14 12 15 12 17 13 13 14 16 25 13 13 8 10 6 14 15 9 0 10 11 14 17 17 7 14 19 12 18 14 15 15 11 16 8 9 16 8 11 12 10 9 18 20 10 8 15 13 10 15 15 11 16 17 18 9 12 1 12 12 13 14 19 15 16 18 15 10 2 13 15 16 11 16 17 10 4 18 17 14 12 16 12 11 15 11 18 13 17 20 12 16 14 12 19 13 5 19 13 13 14 12 14 20 21 16 13 16 17 21 14 11 14 15 15 18 19 17 16 17 14 18 15 17 20 16 19 12 14 17 15 19 18 17 18 12 15 13 21 13 14 23 14 16 13 14 15 21 19 20 13 17 18 16 18 15 20 13 17 15 14 18 18 19 20 18 18 15 16 20 19 19 21 16 19 16 17 15 19 20 21 18 21 15 22 20 22 17 17 16 22 19 20 23 21 17 20 19 19 16 22 19 23 17 17 18 23 22 18 22 21 18 15 20 23 22 21 16 19 17 18 24 23 18 20 16 22 19 17 19 18 21 21 17 22 20 22 18 24 20 22 20 11 21 24 18 19 22 20 23 20 25 18 19 21 21 19 20 19 20 21 21 21 22 25 23 23 21 19 23 23 22 21 22 20 21 20 22 22 21 22 22 25 21 24 23 24 23 23 24 23 21 22 23 24 23 24 23 25 23 24 25 22 24 23 22 24 23 25 20 24 25 23 23 25 22 24 23 25 24 24 20 22 25 24 24 25 14 22 24 24 25 25 25 21 23 22 24 25 23 25 24 24 24 25 25 25 24 24 25 25 25 25 25 25 
1.16	d CHECKS 3.67742e+06
1.16	d NODES 676
1.16

Verifier Data (download as text)

ERROR: constraint C3210 is unsatisfied
Predicate is 
((parm[0]!=parm[1])&&((parm[0]+parm[1])>=2))
parm[0]=0
parm[1]=1

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node34/watcher-237537-1168349118 -o ROOT/results/node34/solver-237537-1168349118 -C 1800 -M 900 /tmp/evaluation/237537-1168349118/VALCSP /tmp/evaluation/237537-1168349118/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: 2.02 2.05 2.00 3/74 8187
/proc/meminfo: memFree=1725936/2055920 swapFree=4192812/4192956
[pid=8186] ppid=8184 vsize=1600 CPUtime=0
/proc/8186/stat : 8186 (VALCSP) R 8184 8186 6035 0 -1 4194304 149 0 0 0 0 0 0 0 20 0 1 0 183305585 1638400 127 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 8156795 0 0 4096 0 0 0 0 17 1 0 0
/proc/8186/statm: 400 127 62 8 0 72 0

[startup+0.103958 s]
/proc/loadavg: 2.02 2.05 2.00 3/74 8187
/proc/meminfo: memFree=1725936/2055920 swapFree=4192812/4192956
[pid=8186] ppid=8184 vsize=10644 CPUtime=0.09
/proc/8186/stat : 8186 (VALCSP) R 8184 8186 6035 0 -1 4194304 2350 0 0 0 8 1 0 0 20 0 1 0 183305585 10899456 2328 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530278 0 0 4096 0 0 0 0 17 1 0 0
/proc/8186/statm: 2661 2328 65 8 0 2333 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 10644

[startup+0.515991 s]
/proc/loadavg: 2.02 2.05 2.00 3/74 8187
/proc/meminfo: memFree=1725936/2055920 swapFree=4192812/4192956
[pid=8186] ppid=8184 vsize=25020 CPUtime=0.5
/proc/8186/stat : 8186 (VALCSP) R 8184 8186 6035 0 -1 4194304 5989 0 0 0 47 3 0 0 24 0 1 0 183305585 25620480 5967 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530305 0 0 4096 0 0 0 0 17 1 0 0
/proc/8186/statm: 6255 5967 65 8 0 5927 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 25020

Child status: 0
Real time (s): 1.17757
CPU time (s): 1.15982
CPU user time (s): 1.09983
CPU system time (s): 0.05999
CPU usage (%): 98.4929
Max. virtual memory (cumulated for all children) (KiB): 40904

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.09983
system time used= 0.05999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 10013
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= 8
involuntary context switches= 27

runsolver used 0.001999 s user time and 0.013997 s system time

The end

Launcher Data (download as text)

Begin job on node34 on Tue Jan  9 13:25:18 UTC 2007


IDJOB= 237537
IDBENCH= 6947
FILE ID= node34/237537-1168349118

PBS_JOBID= 3503463

Free space on /tmp= 66492 MiB

BENCH NAME= HOME/pub/bench/CPAI06/haystacks/haystacks_26.xml
COMMAND LINE= /tmp/evaluation/237537-1168349118/VALCSP /tmp/evaluation/237537-1168349118/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node34/watcher-237537-1168349118 -o ROOT/results/node34/solver-237537-1168349118 -C 1800 -M 900  /tmp/evaluation/237537-1168349118/VALCSP /tmp/evaluation/237537-1168349118/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  b92463ea8cbb51f9a3234236cd8f2202

RANDOM SEED= 255637403

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.227
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.227
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:       1726544 kB
Buffers:         13048 kB
Cached:         158040 kB
SwapCached:          0 kB
Active:         225620 kB
Inactive:        48440 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1726544 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1072 kB
Writeback:           0 kB
Mapped:         114280 kB
Slab:            40652 kB
Committed_AS:  3466076 kB
PageTables:       1940 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= 66492 MiB



End job on node34 on Tue Jan  9 13:25:20 UTC 2007