Trace number 237876

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
buggy_2_5_s 2007-01-08UNSAT 1.60676 1.66704

General information on the benchmark

Namehaystacks/
haystacks_17.xml
MD5SUM2218b17888bd2e948cc597d464c99a9e
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 benchmark1.48877
SatisfiableNO
(Un)Satisfiability was proved
Number of variables289
Number of constraints2328
Maximum constraint arity2
Maximum domain size17
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2328
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

UNSAT

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node60/watcher-237876-1168351694 -o ROOT/results/node60/solver-237876-1168351694 -C 1800 -M 900 /tmp/evaluation/237876-1168351694/solver2 /tmp/evaluation/237876-1168351694/unknown 1800 

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: 0.92 0.98 1.11 4/65 28411
/proc/meminfo: memFree=1861176/2055920 swapFree=4192812/4192956
[pid=28410] ppid=28408 vsize=5352 CPUtime=0
/proc/28410/stat : 28410 (solver2) S 28408 28410 25449 0 -1 4194304 295 0 0 0 0 0 0 0 18 0 1 0 183567433 5480448 232 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 271894242116 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/28410/statm: 1338 232 194 169 0 49 0

[startup+0.106115 s]
/proc/loadavg: 0.92 0.98 1.11 4/65 28411
/proc/meminfo: memFree=1861176/2055920 swapFree=4192812/4192956
[pid=28410] ppid=28408 vsize=5352 CPUtime=0.03
/proc/28410/stat : 28410 (solver2) S 28408 28410 25449 0 -1 4194304 376 2254 0 0 0 0 2 1 16 0 1 0 183567433 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 271894242116 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/28410/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5352

[startup+0.514153 s]
/proc/loadavg: 0.92 0.98 1.11 4/65 28411
/proc/meminfo: memFree=1861176/2055920 swapFree=4192812/4192956
[pid=28410] ppid=28408 vsize=5352 CPUtime=0.03
/proc/28410/stat : 28410 (solver2) S 28408 28410 25449 0 -1 4194304 376 2254 0 0 0 0 2 1 16 0 1 0 183567433 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 271894242116 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/28410/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5352

[startup+1.33423 s]
/proc/loadavg: 0.92 0.98 1.11 2/66 28424
/proc/meminfo: memFree=1856624/2055920 swapFree=4192812/4192956
[pid=28410] ppid=28408 vsize=5352 CPUtime=0.48
/proc/28410/stat : 28410 (solver2) S 28408 28410 25449 0 -1 4194304 397 4860 0 0 0 0 27 21 15 0 1 0 183567433 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 271894242116 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/28410/statm: 1338 242 203 169 0 49 0
[pid=28424] ppid=28410 vsize=5260 CPUtime=0.77
/proc/28424/stat : 28424 (standalone) R 28410 28410 25449 0 -1 4194304 821 0 0 0 73 4 0 0 24 0 1 0 183567488 5386240 758 18446744073709551615 134512640 134775488 4294956896 18446744073709551615 4159546493 0 0 4096 0 0 0 0 17 1 0 0
/proc/28424/statm: 1315 758 138 64 0 630 0
Current children cumulated CPU time (s) 1.25
Current children cumulated vsize (KiB) 10612

Child status: 0
Real time (s): 1.66704
CPU time (s): 1.60676
CPU user time (s): 1.3438
CPU system time (s): 0.26296
CPU usage (%): 96.3837
Max. virtual memory (cumulated for all children) (KiB): 10612

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.3438
system time used= 0.26296
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6095
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= 117
involuntary context switches= 33

runsolver used 0.001999 s user time and 0.009998 s system time

The end

Launcher Data (download as text)

Begin job on node60 on Tue Jan  9 14:08:15 UTC 2007


IDJOB= 237876
IDBENCH= 6968
FILE ID= node60/237876-1168351694

PBS_JOBID= 3503579

Free space on /tmp= 66554 MiB

BENCH NAME= HOME/pub/bench/CPAI06/haystacks/haystacks_17.xml
COMMAND LINE= /tmp/evaluation/237876-1168351694/solver2 /tmp/evaluation/237876-1168351694/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node60/watcher-237876-1168351694 -o ROOT/results/node60/solver-237876-1168351694 -C 1800 -M 900  /tmp/evaluation/237876-1168351694/solver2 /tmp/evaluation/237876-1168351694/unknown 1800

META MD5SUM SOLVER= 2182e29fee250f6e45b9a85a6429fa3a
MD5SUM BENCH=  2218b17888bd2e948cc597d464c99a9e

RANDOM SEED= 652324254

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.236
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.236
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:       1861592 kB
Buffers:         29136 kB
Cached:          97616 kB
SwapCached:          0 kB
Active:          58392 kB
Inactive:        84540 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1861592 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           10280 kB
Writeback:           0 kB
Mapped:          26348 kB
Slab:            37404 kB
Committed_AS:  4489540 kB
PageTables:       1468 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= 66553 MiB



End job on node60 on Tue Jan  9 14:08:17 UTC 2007