Trace number 191906

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
Diarmuid-rndi 2006-12-21UNSAT 0.817875 0.826238

DiagnosticValue
CHECKS357366
NODES724

General information on the benchmark

Namecomposed/composed-75-1-25/
composed-75-1-25-0_ext.xml
MD5SUMfdb5c9889e89d8d24ec4dbb44e8d8cb3
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.05899
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables83
Number of constraints647
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension647
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.82	s UNSATISFIABLE
0.82	d NODES 724
0.82	d CHECKS 357366
c 
c 
c 
c conversion script
c 
c

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/node26/watcher-191906-1168096349 -o ROOT/results/node26/solver-191906-1168096349 -C 1800 -M 900 /tmp/evaluation/191906-1168096349/solver 

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.02 0.39 1.11 6/87 25307
/proc/meminfo: memFree=1302368/2055920 swapFree=4192812/4192956
[pid=25306] ppid=25300 vsize=5352 CPUtime=0
/proc/25306/stat : 25306 (solver) S 25300 25306 24400 0 -1 4194304 280 0 0 0 0 0 0 0 18 0 1 0 158030729 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 269028483908 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/25306/statm: 1338 229 192 169 0 49 0
[pid=25308] ppid=25306 vsize=5352 CPUtime=0
/proc/25308/stat : 25308 (solver) R 25306 25306 24400 0 -1 4194368 18 0 0 0 0 0 0 0 20 0 1 0 158030729 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 269028486439 0 0 4096 0 0 0 0 17 1 0 0
/proc/25308/statm: 1338 229 192 169 0 49 0

[startup+0.107321 s]
/proc/loadavg: 0.02 0.39 1.11 6/87 25307
/proc/meminfo: memFree=1302368/2055920 swapFree=4192812/4192956
[pid=25306] ppid=25300 vsize=5352 CPUtime=0
/proc/25306/stat : 25306 (solver) S 25300 25306 24400 0 -1 4194304 313 174 0 0 0 0 0 0 16 0 1 0 158030729 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 269028483908 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/25306/statm: 1338 229 192 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

[startup+0.515353 s]
/proc/loadavg: 0.02 0.39 1.11 6/87 25307
/proc/meminfo: memFree=1302368/2055920 swapFree=4192812/4192956
[pid=25306] ppid=25300 vsize=5352 CPUtime=0
/proc/25306/stat : 25306 (solver) S 25300 25306 24400 0 -1 4194304 313 174 0 0 0 0 0 0 16 0 1 0 158030729 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 269028483908 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/25306/statm: 1338 229 192 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.826238
CPU time (s): 0.817875
CPU user time (s): 0.804877
CPU system time (s): 0.012998
CPU usage (%): 98.9878
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.804877
system time used= 0.012998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1764
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= 41
involuntary context switches= 11

runsolver used 0.004999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node26 on Sat Jan  6 15:12:32 UTC 2007


IDJOB= 191906
IDBENCH= 3079
FILE ID= node26/191906-1168096349

PBS_JOBID= 3476734

Free space on /tmp= 66538 MiB

BENCH NAME= HOME/pub/bench/CPAI06/composed/composed-75-1-25/composed-75-1-25-0_ext.xml
COMMAND LINE= /tmp/evaluation/191906-1168096349/solver
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node26/convwatcher-191906-1168096349 -o ROOT/results/node26/conversion-191906-1168096349 -C 600 -M 900 /tmp/evaluation/191906-1168096349/conversion /tmp/evaluation/191906-1168096349/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node26/watcher-191906-1168096349 -o ROOT/results/node26/solver-191906-1168096349 -C 1800 -M 900  /tmp/evaluation/191906-1168096349/solver

META MD5SUM SOLVER= b57068d1450403a75f014042200261c5
MD5SUM BENCH=  fdb5c9889e89d8d24ec4dbb44e8d8cb3

RANDOM SEED= 663891314

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:       1303464 kB
Buffers:         44616 kB
Cached:         568064 kB
SwapCached:          0 kB
Active:         141568 kB
Inactive:       535452 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1303464 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1632 kB
Writeback:           0 kB
Mapped:          83312 kB
Slab:            60392 kB
Committed_AS:  2822988 kB
PageTables:       2132 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= 66538 MiB



End job on node26 on Sat Jan  6 15:12:54 UTC 2007