Trace number 277968

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
Toulbar2 2007-01-12SAT 0.146977 0.173079

General information on the benchmark

NameMaxCSP/cnf/3-80-100-1000/
cnf-3-80-300-186941_ext.xml
MD5SUM4714e1e3c53070fca28610038ec4677a
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best Number of satisfied constraints300
Best CPU time to get the best result obtained on this benchmark0.139978
SatisfiableYES
(Un)Satisfiability was proved
Number of variables80
Number of constraints300
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension300
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 1 0 1 1 1 1 0 1 1 1 1 0 1 0 1 0 1 1 0 0 1 1 0 1 1 1 0 0 0 1 1 1 0 1 1 1 0 0 1 0 0 1 0 1 1 1 1 0 0 0 1 1 0 0 1 1 0 0 0 1 1 1 1 1 1 1 1 1 1 0 1 1 0 0 0 0 0 1 1 1 
OPTIMUM
c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/277968-1169273203/unknown.xml to /tmp/evaluation/277968-1169273203/unknown.wcsp

Verifier Data (download as text)

0 unsatisfied constraints, 300 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/node14/watcher-277968-1169273203 -o ROOT/results/node14/solver-277968-1169273203 -C 2400 -M 900 /tmp/evaluation/277968-1169273203/solver.sh /tmp/evaluation/277968-1169273203/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: 1.84 1.95 1.98 4/94 25441
/proc/meminfo: memFree=1284504/2055920 swapFree=4158792/4192956
[pid=25440] ppid=25438 vsize=8652 CPUtime=0
/proc/25440/stat : 25440 (solver.sh) S 25438 25440 24881 0 -1 4194304 347 0 0 0 0 0 0 0 17 0 1 0 275715313 8859648 280 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 212234070874 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/25440/statm: 2163 280 208 79 0 156 0
[pid=25442] ppid=25440 vsize=8688 CPUtime=0
/proc/25442/stat : 25442 (solver.sh) S 25440 25440 24881 0 -1 4194368 60 244 0 0 0 0 0 0 18 0 1 0 275715314 8896512 288 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 212234633298 0 0 4096 73728 18446744071563648864 0 0 17 0 0 0
/proc/25442/statm: 2172 288 210 79 0 165 0
[pid=25444] ppid=25442 vsize=6864 CPUtime=0
/proc/25444/stat : 25444 (id) S 25442 25440 24881 0 -1 4194304 241 0 0 0 0 0 0 0 16 0 1 0 275715314 7028736 183 18446744073709551615 4194304 4211724 548682069312 18446744073709551615 212234651535 0 0 3674112 0 0 0 0 17 1 0 0
/proc/25444/statm: 1716 183 154 4 0 46 0

[startup+0.106729 s]
/proc/loadavg: 1.84 1.95 1.98 4/94 25441
/proc/meminfo: memFree=1284504/2055920 swapFree=4158792/4192956
[pid=25440] ppid=25438 vsize=47548 CPUtime=0.01
/proc/25440/stat : 25440 (solver.sh) S 25438 25440 24881 0 -1 4194304 845 2110 0 0 0 0 0 1 20 0 1 0 275715313 48689152 361 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 212234070874 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/25440/statm: 11887 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47548

Child status: 0
Real time (s): 0.173079
CPU time (s): 0.146977
CPU user time (s): 0.101984
CPU system time (s): 0.044993
CPU usage (%): 84.9191
Max. virtual memory (cumulated for all children) (KiB): 47548

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

runsolver used 0.001999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node14 on Sat Jan 20 06:06:44 UTC 2007


IDJOB= 277968
IDBENCH= 7873
IDSOLVER= 70
FILE ID= node14/277968-1169273203

PBS_JOBID= 3607446

Free space on /tmp= 66562 MiB

SOLVER NAME= Toulbar2 2007-01-12
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/cnf/3-80-100-1000/cnf-3-80-300-186941_ext.xml
COMMAND LINE= /tmp/evaluation/277968-1169273203/solver.sh /tmp/evaluation/277968-1169273203/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node14/convwatcher-277968-1169273203 -o ROOT/results/node14/conversion-277968-1169273203 -C 600 -M 900 /tmp/evaluation/277968-1169273203/translate /tmp/evaluation/277968-1169273203/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node14/watcher-277968-1169273203 -o ROOT/results/node14/solver-277968-1169273203 -C 2400 -M 900  /tmp/evaluation/277968-1169273203/solver.sh /tmp/evaluation/277968-1169273203/unknown

META MD5SUM SOLVER= fe7e38206dd9591eb05752f9e2c48642
MD5SUM BENCH=  4714e1e3c53070fca28610038ec4677a

RANDOM SEED= 342100505

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.227
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.227
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:       1285112 kB
Buffers:         52348 kB
Cached:         596680 kB
SwapCached:       9076 kB
Active:         205940 kB
Inactive:       487700 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1285112 kB
SwapTotal:     4192956 kB
SwapFree:      4158792 kB
Dirty:            2588 kB
Writeback:           0 kB
Mapped:          59944 kB
Slab:            61892 kB
Committed_AS:  8931880 kB
PageTables:       2276 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= 66562 MiB



End job on node14 on Sat Jan 20 06:06:44 UTC 2007