Trace number 276403

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_MaxSat 2007-01-19? (exit code) 0.677896 0.694875

General information on the benchmark

Nametightness/tightness0.8/
rand-2-40-80-103-800-2_ext.xml
MD5SUM86e6d96c8cf9e85b2a2d82a25fe308a3
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints102
Best CPU time to get the best result obtained on this benchmark636.562
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables40
Number of constraints103
Maximum constraint arity2
Maximum domain size80
Number of constraints which are defined in extension103
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/276403-1169236728/unknown.xml to /tmp/evaluation/276403-1169236728/unknown.wcsp

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node25/watcher-276403-1169236728 -o ROOT/results/node25/solver-276403-1169236728 -C 2400 -M 900 /tmp/evaluation/276403-1169236728/solver.sh /tmp/evaluation/276403-1169236728/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: 0.75 0.95 0.98 4/88 12523
/proc/meminfo: memFree=1471512/2055920 swapFree=4170284/4192956
[pid=12522] ppid=12520 vsize=8564 CPUtime=0
/proc/12522/stat : 12522 (solver.sh) R 12520 12522 12368 0 -1 4194304 317 0 0 0 0 0 0 0 19 0 1 0 272065390 8769536 261 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 215781965778 0 2 4096 8192 0 0 0 17 0 0 0
/proc/12522/statm: 2141 261 201 79 0 134 0

[startup+0.106749 s]
/proc/loadavg: 0.75 0.95 0.98 4/88 12523
/proc/meminfo: memFree=1471512/2055920 swapFree=4170284/4192956
[pid=12522] ppid=12520 vsize=47548 CPUtime=0.01
/proc/12522/stat : 12522 (solver.sh) S 12520 12522 12368 0 -1 4194304 871 2241 0 0 0 0 0 1 19 0 1 0 272065390 48689152 360 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 215781403482 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/12522/statm: 11887 360 244 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47548

[startup+0.514815 s]
/proc/loadavg: 0.75 0.95 0.98 4/88 12523
/proc/meminfo: memFree=1471512/2055920 swapFree=4170284/4192956
[pid=12522] ppid=12520 vsize=47548 CPUtime=0.01
/proc/12522/stat : 12522 (solver.sh) S 12520 12522 12368 0 -1 4194304 871 2241 0 0 0 0 0 1 19 0 1 0 272065390 48689152 360 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 215781403482 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/12522/statm: 11887 360 244 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47548

Child status: 1
Real time (s): 0.694875
CPU time (s): 0.677896
CPU user time (s): 0.568913
CPU system time (s): 0.108983
CPU usage (%): 97.5566
Max. virtual memory (cumulated for all children) (KiB): 47548

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.568913
system time used= 0.108983
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6242
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= 90
involuntary context switches= 40

runsolver used 0.001999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node25 on Fri Jan 19 19:58:49 UTC 2007


IDJOB= 276403
IDBENCH= 5748
IDSOLVER= 71
FILE ID= node25/276403-1169236728

PBS_JOBID= 3589315

Free space on /tmp= 66559 MiB

SOLVER NAME= Toolbar_MaxSat 2007-01-19
BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.8/rand-2-40-80-103-800-2_ext.xml
COMMAND LINE= /tmp/evaluation/276403-1169236728/solver.sh /tmp/evaluation/276403-1169236728/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node25/convwatcher-276403-1169236728 -o ROOT/results/node25/conversion-276403-1169236728 -C 600 -M 900 /tmp/evaluation/276403-1169236728/translate /tmp/evaluation/276403-1169236728/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node25/watcher-276403-1169236728 -o ROOT/results/node25/solver-276403-1169236728 -C 2400 -M 900  /tmp/evaluation/276403-1169236728/solver.sh /tmp/evaluation/276403-1169236728/unknown

META MD5SUM SOLVER= f843f34905a307bcc0c6a322bc802c9d
MD5SUM BENCH=  86e6d96c8cf9e85b2a2d82a25fe308a3

RANDOM SEED= 938217310

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.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:       1472312 kB
Buffers:         41720 kB
Cached:         437020 kB
SwapCached:       2768 kB
Active:         169012 kB
Inactive:       342036 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1472312 kB
SwapTotal:     4192956 kB
SwapFree:      4170284 kB
Dirty:            8164 kB
Writeback:           0 kB
Mapped:          43492 kB
Slab:            57184 kB
Committed_AS:  4848936 kB
PageTables:       2336 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= 66557 MiB



End job on node25 on Fri Jan 19 19:58:51 UTC 2007