Trace number 1077335

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
choco2_impwdeg 2008-06-26SAT 0.893863 0.93723

DiagnosticValue
ASSIGNMENTS9

General information on the benchmark

Namecsp/primes-15/
normalized-primes-15-80-3-1.xml
MD5SUMc089ecbd43cbff7c337b278f449f7836
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.024995
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints80
Maximum constraint arity4
Maximum domain size46
Number of constraints which are defined in extension0
Number of constraints which are defined in intension80
Global constraints used (with number of constraints)

Solver Data (download as text)

0.79/0.88	s SATISFIABLE
0.79/0.88	v 2 42 41 31 23 31 3 41 29 3 5 19 2 11 23 3 2 17 19 3 37 23 32 29 5 13 5 2 19 31 47 41 41 7 47 2 43 3 3 19 29 7 17 47 47 19 23 47 13 2 23 3 3 13 37 7 5 13 3 3 2 2 2 41 37 13 3 29 43 5 29 2 2 2 47 41 47 47 7 13 19 7 17 23 23 29 7 37 47 11 41 2 37 7 11 19 3 17 29 47 
0.79/0.88	d ASSIGNMENTS 9
0.79/0.88	c SAT 800 TIME      9 NDS    299 PARSTIME      302 BUILDPB       199 RES       true RESTART       1 HEURISTIC

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1077335-1215192341/watcher-1077335-1215192341 -o /tmp/evaluation-result-1077335-1215192341/solver-1077335-1215192341 -C 1800 -W 2200 -M 900 --output-limit 1,15 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar choco2impWdeg.jar HOME/instance-1077335-1215192341.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2200 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.04 2.01 1.98 3/72 26375
/proc/meminfo: memFree=1682632/2055920 swapFree=4180448/4192956
[pid=26375] ppid=26373 vsize=152 CPUtime=0
/proc/26375/stat : 26375 (java) R 26373 26375 23826 0 -1 0 223 0 0 0 0 0 0 0 18 0 1 0 1998208639 155648 26 996147200 134512640 134550740 4294956016 18446744073709551615 2605355 0 0 4096 0 0 0 0 17 0 0 0
/proc/26375/statm: 38 26 19 9 0 4 0

[startup+0.0211281 s]
/proc/loadavg: 2.04 2.01 1.98 3/72 26375
/proc/meminfo: memFree=1682632/2055920 swapFree=4180448/4192956
[pid=26375] ppid=26373 vsize=860896 CPUtime=0.01
/proc/26375/stat : 26375 (java) S 26373 26375 23826 0 -1 0 1630 0 1 0 0 1 0 0 18 0 2 0 1998208639 881557504 1326 996147200 134512640 134550740 4294956016 18446744073709551615 4294960144 0 0 0 16784584 18446744073709551615 0 0 17 0 0 0
/proc/26375/statm: 215224 1331 525 9 0 210203 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 860896

[startup+0.101136 s]
/proc/loadavg: 2.04 2.01 1.98 3/72 26375
/proc/meminfo: memFree=1682632/2055920 swapFree=4180448/4192956
[pid=26375] ppid=26373 vsize=866524 CPUtime=0.09
/proc/26375/stat : 26375 (java) S 26373 26375 23826 0 -1 0 3877 0 1 0 7 2 0 0 18 0 9 0 1998208639 887320576 3338 996147200 134512640 134550740 4294956016 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/26375/statm: 216631 3338 1777 9 0 211103 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 866524

[startup+0.301155 s]
/proc/loadavg: 2.04 2.01 1.98 3/72 26375
/proc/meminfo: memFree=1682632/2055920 swapFree=4180448/4192956
[pid=26375] ppid=26373 vsize=867296 CPUtime=0.29
/proc/26375/stat : 26375 (java) S 26373 26375 23826 0 -1 0 4907 0 1 0 27 2 0 0 18 0 9 0 1998208639 888111104 4349 996147200 134512640 134550740 4294956016 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/26375/statm: 216824 4349 1888 9 0 211296 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 867296

[startup+0.701197 s]
/proc/loadavg: 2.04 2.01 1.98 3/72 26375
/proc/meminfo: memFree=1682632/2055920 swapFree=4180448/4192956
[pid=26375] ppid=26373 vsize=867544 CPUtime=0.69
/proc/26375/stat : 26375 (java) S 26373 26375 23826 0 -1 0 7987 0 1 0 66 3 0 0 18 0 9 0 1998208639 888365056 7389 996147200 134512640 134550740 4294956016 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/26375/statm: 216886 7389 1969 9 0 211358 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 867544

Solver just ended. Dumping a history of the last processes samples

[startup+0.901218 s]
/proc/loadavg: 2.04 2.01 1.98 3/72 26375
/proc/meminfo: memFree=1682632/2055920 swapFree=4180448/4192956
[pid=26375] ppid=26373 vsize=867868 CPUtime=0.88
/proc/26375/stat : 26375 (java) S 26373 26375 23826 0 -1 0 8313 0 1 0 84 4 0 0 18 0 9 0 1998208639 888696832 7714 996147200 134512640 134550740 4294956016 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/26375/statm: 216967 7714 1972 9 0 211439 0
Current children cumulated CPU time (s) 0.88
Current children cumulated vsize (KiB) 867868

Child status: 0
Real time (s): 0.93723
CPU time (s): 0.893863
CPU user time (s): 0.843871
CPU system time (s): 0.049992
CPU usage (%): 95.3729
Max. virtual memory (cumulated for all children) (KiB): 867868

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.843871
system time used= 0.049992
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8316
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 1091
involuntary context switches= 1061

runsolver used 0.001999 second user time and 0.012998 second system time

The end

Launcher Data (download as text)

Begin job on node24 at 2008-07-04 19:25:41
IDJOB=1077335
IDBENCH=56664
IDSOLVER=348
FILE ID=node24/1077335-1215192341
PBS_JOBID= 7881574
Free space on /tmp= 66456 MiB

SOLVER NAME= choco2_impwdeg 2008-06-26
BENCH NAME= CPAI08/csp/primes-15/normalized-primes-15-80-3-1.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar choco2impWdeg.jar BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1077335-1215192341/watcher-1077335-1215192341 -o /tmp/evaluation-result-1077335-1215192341/solver-1077335-1215192341 -C 1800 -W 2200 -M 900 --output-limit 1,15  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar choco2impWdeg.jar HOME/instance-1077335-1215192341.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= c089ecbd43cbff7c337b278f449f7836
RANDOM SEED=1724237984

node24.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.232
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.232
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:       1683112 kB
Buffers:         36740 kB
Cached:         250192 kB
SwapCached:       6556 kB
Active:         165028 kB
Inactive:       149428 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1683112 kB
SwapTotal:     4192956 kB
SwapFree:      4180448 kB
Dirty:            6416 kB
Writeback:           0 kB
Mapped:          35432 kB
Slab:            43052 kB
Committed_AS:  3596756 kB
PageTables:       2268 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= 66452 MiB
End job on node24 at 2008-07-04 19:25:42