Trace number 277547

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
Toolbar_BTD 2007-01-12OPTIMUM 1.2978 1.33172

General information on the benchmark

Namedimacs/pret/
pret-60-25_ext.xml
MD5SUM5ae51ce573f8e61d952141129607aff7
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints39
Best CPU time to get the best result obtained on this benchmark1.2978
SatisfiableNO
(Un)Satisfiability was proved
Number of variables60
Number of constraints40
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension40
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SOL 0 1 1 1 1 0 1 0 1 0 1 1 0 1 1 0 0 0 1 1 0 1 1 0 0 0 0 1 0 1 1 0 1 0 0 0 0 1 0 0 1 0 0 0 0 0 1 1 0 1 0 0 0 1 0 0 1 1 0 0 
OPTIMUM
c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/277547-1169268525/unknown.xml to /tmp/evaluation/277547-1169268525/unknown.wcsp

Verifier Data (download as text)

1 unsatisfied constraints, 39 satisfied constraints

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node65/watcher-277547-1169268525 -o ROOT/results/node65/solver-277547-1169268525 -C 2400 -M 900 /tmp/evaluation/277547-1169268525/solver.sh /tmp/evaluation/277547-1169268525/unknown 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 2430 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 1.94 5/80 29524
/proc/meminfo: memFree=1437700/2055920 swapFree=4191892/4192956
[pid=29523] ppid=29521 vsize=18540 CPUtime=0
/proc/29523/stat : 29523 (runsolver) R 29521 29523 29276 0 -1 4194368 16 0 0 0 0 0 0 0 21 0 1 0 74349840 18984960 279 18446744073709551615 4194304 4267372 548682069088 18446744073709551615 257203694887 0 0 4096 24578 0 0 0 17 1 0 0
/proc/29523/statm: 4635 279 244 17 0 2626 0

[startup+0.110088 s]
/proc/loadavg: 2.00 2.00 1.94 5/80 29524
/proc/meminfo: memFree=1437700/2055920 swapFree=4191892/4192956
[pid=29523] ppid=29521 vsize=47564 CPUtime=0.01
/proc/29523/stat : 29523 (solver.sh) S 29521 29523 29276 0 -1 4194304 845 2110 0 0 0 0 0 1 25 0 1 0 74349840 48705536 360 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 257203301210 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/29523/statm: 11891 360 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47564

[startup+0.518153 s]
/proc/loadavg: 2.00 2.00 1.94 5/80 29524
/proc/meminfo: memFree=1437700/2055920 swapFree=4191892/4192956
[pid=29523] ppid=29521 vsize=47564 CPUtime=0.01
/proc/29523/stat : 29523 (solver.sh) S 29521 29523 29276 0 -1 4194304 845 2110 0 0 0 0 0 1 25 0 1 0 74349840 48705536 360 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 257203301210 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/29523/statm: 11891 360 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47564

Child status: 0
Real time (s): 1.33172
CPU time (s): 1.2978
CPU user time (s): 1.20182
CPU system time (s): 0.095985
CPU usage (%): 97.4531
Max. virtual memory (cumulated for all children) (KiB): 97120

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.20182
system time used= 0.095985
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 17962
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= 92
involuntary context switches= 58

runsolver used 0.004999 s user time and 0.009998 s system time

The end

Launcher Data (download as text)

Begin job on node65 on Sat Jan 20 04:48:45 UTC 2007


IDJOB= 277547
IDBENCH= 7352
IDSOLVER= 72
FILE ID= node65/277547-1169268525

PBS_JOBID= 3607381

Free space on /tmp= 66560 MiB

SOLVER NAME= Toolbar_BTD 2007-01-12
BENCH NAME= HOME/pub/bench/CPAI06/dimacs/pret/pret-60-25_ext.xml
COMMAND LINE= /tmp/evaluation/277547-1169268525/solver.sh /tmp/evaluation/277547-1169268525/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node65/convwatcher-277547-1169268525 -o ROOT/results/node65/conversion-277547-1169268525 -C 600 -M 900 /tmp/evaluation/277547-1169268525/translate /tmp/evaluation/277547-1169268525/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node65/watcher-277547-1169268525 -o ROOT/results/node65/solver-277547-1169268525 -C 2400 -M 900  /tmp/evaluation/277547-1169268525/solver.sh /tmp/evaluation/277547-1169268525/unknown

META MD5SUM SOLVER= f75ee5e830002fa98429bd59d9dcbc78
MD5SUM BENCH=  5ae51ce573f8e61d952141129607aff7

RANDOM SEED= 833527839

TIME LIMIT= 2400 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.263
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.263
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:       1438180 kB
Buffers:         46824 kB
Cached:         454484 kB
SwapCached:        396 kB
Active:         122256 kB
Inactive:       426148 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1438180 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:            4604 kB
Writeback:           0 kB
Mapped:          65956 kB
Slab:            54664 kB
Committed_AS:  1478912 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= 66560 MiB



End job on node65 on Sat Jan 20 04:48:47 UTC 2007