Trace number 209312

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
BPrologCSPSolver70a 2006-12-13UNSAT 6.16106 6.19297

General information on the benchmark

Namefapp/fapp01-05/fapp03/
fapp03-0300-0.xml
MD5SUM2d0f7dc038a7281558606599f52dab97
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.3258
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables300
Number of constraints4377
Maximum constraint arity2
Maximum domain size250
Number of constraints which are defined in extension0
Number of constraints which are defined in intension4377
Global constraints used (with number of constraints)

Solver Data (download as text)

6.18	
6.19	Time: 6129
6.19	
c 
c 
c 
c solution file
c 
c 

UNSAT
c 
c 
c 
c conversion script
c 
c 

converting(/tmp/evaluation/209312-1168192303/unknown)

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/node4/watcher-209312-1168192303 -o ROOT/results/node4/solver-209312-1168192303 -C 1800 -M 900 /tmp/evaluation/209312-1168192303/Complete/Ordinary/solver /tmp/evaluation/209312-1168192303/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: 2.00 2.14 2.25 5/87 25141
/proc/meminfo: memFree=1624936/2055920 swapFree=4182144/4192956
[pid=25140] ppid=25138 vsize=18540 CPUtime=0
/proc/25140/stat : 25140 (runsolver) R 25138 25140 24644 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 167626176 18984960 279 18446744073709551615 4194304 4267372 548682069056 18446744073709551615 259913215271 0 0 4096 24578 0 0 0 17 1 0 0
/proc/25140/statm: 4635 279 244 17 0 2626 0

[startup+0.107661 s]
/proc/loadavg: 2.00 2.14 2.25 5/87 25141
/proc/meminfo: memFree=1624936/2055920 swapFree=4182144/4192956
[pid=25140] ppid=25138 vsize=53824 CPUtime=0.1
/proc/25140/stat : 25140 (bprolog) R 25138 25140 24644 0 -1 4194304 1937 0 0 0 9 1 0 0 20 0 1 0 167626176 55115776 1653 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134555972 0 0 4096 2 0 0 0 17 1 0 0
/proc/25140/statm: 13456 1653 157 90 0 12994 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 53824

[startup+0.515696 s]
/proc/loadavg: 2.00 2.14 2.25 5/87 25141
/proc/meminfo: memFree=1624936/2055920 swapFree=4182144/4192956
[pid=25140] ppid=25138 vsize=62076 CPUtime=0.5
/proc/25140/stat : 25140 (bprolog) R 25138 25140 24644 0 -1 4194304 2669 0 0 0 49 1 0 0 23 0 1 0 167626176 63565824 2384 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134663819 0 0 4096 2 0 0 0 17 1 0 0
/proc/25140/statm: 15519 2384 176 90 0 15057 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 62076

[startup+1.33678 s]
/proc/loadavg: 2.00 2.14 2.25 3/87 25141
/proc/meminfo: memFree=1614376/2055920 swapFree=4182144/4192956
[pid=25140] ppid=25138 vsize=62076 CPUtime=1.32
/proc/25140/stat : 25140 (bprolog) R 25138 25140 24644 0 -1 4194304 3507 0 0 0 131 1 0 0 25 0 1 0 167626176 63565824 3222 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134664651 0 0 4096 2 0 0 0 17 1 0 0
/proc/25140/statm: 15519 3222 176 90 0 15057 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 62076

[startup+2.97393 s]
/proc/loadavg: 2.00 2.14 2.25 3/88 25142
/proc/meminfo: memFree=1609952/2055920 swapFree=4182144/4192956
[pid=25140] ppid=25138 vsize=72320 CPUtime=2.95
/proc/25140/stat : 25140 (bprolog) R 25138 25140 24644 0 -1 4194304 4185 0 0 0 294 1 0 0 25 0 2 0 167626176 74055680 3900 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134662622 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/25140/statm: 18080 3900 180 90 0 17618 0
[pid=25140/tid=25142] ppid=25138 vsize=72320 CPUtime=0
/proc/25140/task/25142/stat : 25142 (bprolog) S 25138 25140 24644 0 -1 4194368 2 0 0 0 0 0 0 0 25 0 2 0 167626339 74055680 3900 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 4294960144 0 0 4096 2 0 0 0 -1 1 0 0
Current children cumulated CPU time (s) 2.95
Current children cumulated vsize (KiB) 72320

Child status: 0
Real time (s): 6.19297
CPU time (s): 6.16106
CPU user time (s): 6.14107
CPU system time (s): 0.019996
CPU usage (%): 99.4848
Max. virtual memory (cumulated for all children) (KiB): 72320

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 6.14107
system time used= 0.019996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4198
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= 10
involuntary context switches= 209

runsolver used 0.005999 s user time and 0.025996 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Sun Jan  7 17:51:43 UTC 2007


IDJOB= 209312
IDBENCH= 4509
FILE ID= node4/209312-1168192303

PBS_JOBID= 3479361

Free space on /tmp= 66306 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp01-05/fapp03/fapp03-0300-0.xml
COMMAND LINE= /tmp/evaluation/209312-1168192303/Complete/Ordinary/solver /tmp/evaluation/209312-1168192303/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node4/convwatcher-209312-1168192303 -o ROOT/results/node4/conversion-209312-1168192303 -C 600 -M 900 /tmp/evaluation/209312-1168192303/Complete/Ordinary/conversion /tmp/evaluation/209312-1168192303/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-209312-1168192303 -o ROOT/results/node4/solver-209312-1168192303 -C 1800 -M 900  /tmp/evaluation/209312-1168192303/Complete/Ordinary/solver /tmp/evaluation/209312-1168192303/unknown 1800

META MD5SUM SOLVER= b53ab06f245aa5e62684a7a0a4388ade
MD5SUM BENCH=  2d0f7dc038a7281558606599f52dab97

RANDOM SEED= 708699469

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.223
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.223
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:       1625416 kB
Buffers:         55612 kB
Cached:         263168 kB
SwapCached:       2520 kB
Active:         163212 kB
Inactive:       213348 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1625416 kB
SwapTotal:     4192956 kB
SwapFree:      4182144 kB
Dirty:            2412 kB
Writeback:           0 kB
Mapped:          68548 kB
Slab:            38512 kB
Committed_AS:  4449268 kB
PageTables:       2408 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= 66306 MiB



End job on node4 on Sun Jan  7 17:51:53 UTC 2007