Trace number 238033

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. 0.409937 0.420673

DiagnosticValue
CHECKS1320240
NODES441

General information on the benchmark

Namehaystacks/
haystacks_21.xml
MD5SUMf7604e5d4a195ac07a94a60497bb2137
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 benchmark7.44587
SatisfiableNO
(Un)Satisfiability was proved
Number of variables441
Number of constraints4430
Maximum constraint arity2
Maximum domain size21
Number of constraints which are defined in extension0
Number of constraints which are defined in intension4430
Global constraints used (with number of constraints)

Solver Data (download as text)

0.41	s SATISFIABLE
0.41	v 0 0 1 0 1 0 0 0 0 2 0 0 0 1 0 0 0 14 0 2 2 1 2 3 0 1 1 3 3 1 1 15 4 4 0 1 1 2 1 1 2 1 0 5 0 1 2 0 2 2 2 2 3 3 0 1 2 2 5 6 3 4 2 1 3 3 1 3 12 4 5 3 4 4 4 7 2 5 1 2 3 5 3 3 4 2 5 4 16 5 2 1 2 4 6 5 1 5 6 7 2 3 4 4 5 2 4 3 4 3 5 5 6 7 8 4 9 10 3 6 6 6 6 7 8 4 3 7 4 5 17 5 11 7 5 7 6 9 8 4 11 5 3 10 11 5 8 8 6 4 6 5 5 8 4 6 7 9 7 6 6 6 9 3 9 7 4 7 9 7 5 7 12 5 9 8 10 8 8 6 7 9 10 12 6 7 10 13 8 11 6 12 13 9 8 6 10 7 8 6 7 7 8 10 7 14 11 9 9 7 9 8 11 8 11 8 8 9 12 9 9 10 10 11 12 10 7 10 11 19 11 13 10 14 11 12 0 3 13 10 12 9 12 10 13 12 10 13 8 14 11 9 13 11 10 15 11 10 14 9 12 11 13 14 8 12 16 14 12 13 11 11 17 8 12 1 18 11 14 13 12 13 9 14 15 12 14 10 10 12 11 13 14 11 12 15 15 16 12 12 12 13 9 16 16 14 15 13 13 13 15 13 13 15 14 14 13 14 15 14 10 16 19 16 14 15 14 15 17 15 15 15 11 16 18 13 15 16 14 14 15 17 15 15 17 16 16 14 18 9 16 16 16 15 16 17 16 17 15 17 18 17 17 19 10 18 17 17 17 18 17 17 17 16 20 18 16 16 18 18 18 19 15 18 16 18 16 18 17 20 17 19 17 19 18 20 18 19 18 17 19 6 19 19 19 18 20 20 19 18 17 20 19 18 13 8 19 18 20 19 20 19 19 20 20 19 18 19 20 20 20 20 19 20 19 20 20 20 20 20 20 
0.41	d CHECKS 1.32024e+06
0.41	d NODES 441
0.41

Verifier Data (download as text)

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

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node15/watcher-238033-1168352924 -o ROOT/results/node15/solver-238033-1168352924 -C 1800 -M 900 /tmp/evaluation/238033-1168352924/VALCSP /tmp/evaluation/238033-1168352924/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.00 2.00 2.00 5/89 14517
/proc/meminfo: memFree=1782664/2055920 swapFree=4174172/4192956
[pid=14516] ppid=14514 vsize=2920 CPUtime=0
/proc/14516/stat : 14516 (VALCSP) R 14514 14516 13572 0 -1 4194304 461 0 0 0 0 0 0 0 20 0 1 0 183687228 2990080 439 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 7947899 0 0 4096 0 0 0 0 17 1 0 0
/proc/14516/statm: 730 439 62 8 0 402 0

[startup+0.107407 s]
/proc/loadavg: 2.00 2.00 2.00 5/89 14517
/proc/meminfo: memFree=1782664/2055920 swapFree=4174172/4192956
[pid=14516] ppid=14514 vsize=7472 CPUtime=0.09
/proc/14516/stat : 14516 (VALCSP) R 14514 14516 13572 0 -1 4194304 1584 0 0 0 9 0 0 0 20 0 1 0 183687228 7651328 1562 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530925 0 0 4096 0 0 0 0 17 1 0 0
/proc/14516/statm: 1868 1562 64 8 0 1540 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7472

Child status: 0
Real time (s): 0.420673
CPU time (s): 0.409937
CPU user time (s): 0.39394
CPU system time (s): 0.015997
CPU usage (%): 97.4479
Max. virtual memory (cumulated for all children) (KiB): 16592

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

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node15 on Tue Jan  9 14:28:44 UTC 2007


IDJOB= 238033
IDBENCH= 6978
FILE ID= node15/238033-1168352924

PBS_JOBID= 3503683

Free space on /tmp= 66560 MiB

BENCH NAME= HOME/pub/bench/CPAI06/haystacks/haystacks_21.xml
COMMAND LINE= /tmp/evaluation/238033-1168352924/VALCSP /tmp/evaluation/238033-1168352924/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node15/watcher-238033-1168352924 -o ROOT/results/node15/solver-238033-1168352924 -C 1800 -M 900  /tmp/evaluation/238033-1168352924/VALCSP /tmp/evaluation/238033-1168352924/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  f7604e5d4a195ac07a94a60497bb2137

RANDOM SEED= 910837642

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.276
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.276
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:       1783144 kB
Buffers:         40668 kB
Cached:         118036 kB
SwapCached:       6400 kB
Active:         139840 kB
Inactive:        77512 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1783144 kB
SwapTotal:     4192956 kB
SwapFree:      4174172 kB
Dirty:             600 kB
Writeback:           0 kB
Mapped:          69224 kB
Slab:            40104 kB
Committed_AS:  5843944 kB
PageTables:       2424 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= 66560 MiB



End job on node15 on Tue Jan  9 14:28:44 UTC 2007