Trace number 237521

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.67174 1.68926

DiagnosticValue
CHECKS5255260
NODES784

General information on the benchmark

Namehaystacks/
haystacks_28.xml
MD5SUMd182319e3384c4b9a637e552d7b21712
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 benchmark77.5232
SatisfiableNO
(Un)Satisfiability was proved
Number of variables784
Number of constraints10611
Maximum constraint arity2
Maximum domain size28
Number of constraints which are defined in extension0
Number of constraints which are defined in intension10611
Global constraints used (with number of constraints)

Solver Data (download as text)

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

Verifier Data (download as text)

ERROR: constraint C714 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/node22/watcher-237521-1168349042 -o ROOT/results/node22/solver-237521-1168349042 -C 1800 -M 900 /tmp/evaluation/237521-1168349042/VALCSP /tmp/evaluation/237521-1168349042/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.92 1.98 1.93 3/87 6249
/proc/meminfo: memFree=1820472/2055920 swapFree=4157544/4192956
[pid=6248] ppid=6246 vsize=1600 CPUtime=0
/proc/6248/stat : 6248 (VALCSP) R 6246 6248 5227 0 -1 4194304 134 0 0 0 0 0 0 0 20 0 1 0 183298626 1638400 112 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 5113467 0 0 4096 0 0 0 0 17 1 0 0
/proc/6248/statm: 400 112 62 8 0 72 0

[startup+0.103878 s]
/proc/loadavg: 1.92 1.98 1.93 3/87 6249
/proc/meminfo: memFree=1820472/2055920 swapFree=4157544/4192956
[pid=6248] ppid=6246 vsize=12412 CPUtime=0.09
/proc/6248/stat : 6248 (VALCSP) R 6246 6248 5227 0 -1 4194304 2788 0 0 0 8 1 0 0 20 0 1 0 183298626 12709888 2766 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530286 0 0 4096 0 0 0 0 17 1 0 0
/proc/6248/statm: 3103 2766 65 8 0 2775 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 12412

[startup+0.511939 s]
/proc/loadavg: 1.92 1.98 1.93 3/87 6249
/proc/meminfo: memFree=1820472/2055920 swapFree=4157544/4192956
[pid=6248] ppid=6246 vsize=26348 CPUtime=0.5
/proc/6248/stat : 6248 (VALCSP) R 6246 6248 5227 0 -1 4194304 6307 0 0 0 48 2 0 0 24 0 1 0 183298626 26980352 6285 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530975 0 0 4096 0 0 0 0 17 1 0 0
/proc/6248/statm: 6587 6285 65 8 0 6259 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 26348

[startup+1.33507 s]
/proc/loadavg: 1.92 1.98 1.93 3/87 6249
/proc/meminfo: memFree=1774776/2055920 swapFree=4157544/4192956
[pid=6248] ppid=6246 vsize=56296 CPUtime=1.31
/proc/6248/stat : 6248 (VALCSP) R 6246 6248 5227 0 -1 4194304 13837 0 0 0 125 6 0 0 25 0 1 0 183298626 57647104 13815 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134520516 0 0 4096 0 0 0 0 17 1 0 0
/proc/6248/statm: 14074 13815 67 8 0 13746 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 56296

Child status: 0
Real time (s): 1.68926
CPU time (s): 1.67174
CPU user time (s): 1.59476
CPU system time (s): 0.076988
CPU usage (%): 98.9629
Max. virtual memory (cumulated for all children) (KiB): 56296

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

runsolver used 0.003999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node22 on Tue Jan  9 13:24:02 UTC 2007


IDJOB= 237521
IDBENCH= 6946
FILE ID= node22/237521-1168349042

PBS_JOBID= 3503613

Free space on /tmp= 66552 MiB

BENCH NAME= HOME/pub/bench/CPAI06/haystacks/haystacks_28.xml
COMMAND LINE= /tmp/evaluation/237521-1168349042/VALCSP /tmp/evaluation/237521-1168349042/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node22/watcher-237521-1168349042 -o ROOT/results/node22/solver-237521-1168349042 -C 1800 -M 900  /tmp/evaluation/237521-1168349042/VALCSP /tmp/evaluation/237521-1168349042/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  d182319e3384c4b9a637e552d7b21712

RANDOM SEED= 958837651

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.279
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.279
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:       1821016 kB
Buffers:         12392 kB
Cached:         112180 kB
SwapCached:      11224 kB
Active:         126356 kB
Inactive:        54140 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1821016 kB
SwapTotal:     4192956 kB
SwapFree:      4157544 kB
Dirty:            1424 kB
Writeback:           0 kB
Mapped:          74756 kB
Slab:            39216 kB
Committed_AS:  3560864 kB
PageTables:       2288 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= 66552 MiB



End job on node22 on Tue Jan  9 13:24:04 UTC 2007