Trace number 2082591

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
bpsolver 09SAT 0.285955 0.298546

General information on the benchmark

Namecsp/super-jobShop/
super-jobShop-enddr1/normalized-super-jobShop-enddr1-8.xml
MD5SUM31da94f2e356bf95fd869137b551c4a1
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.285955
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints845
Maximum constraint arity2
Maximum domain size127
Number of constraints which are defined in extension0
Number of constraints which are defined in intension845
Global constraints used (with number of constraints)

Solver Data 

0.00/0.02	c bpsolver version 6.29.2009
0.00/0.02	c converting(HOME/instance-2082591-1247375381)
0.12/0.17	c Converted in 71 ms
0.12/0.20	c solving(HOME/instance-2082591-1247375381,1800000)
0.12/0.20	c solving(HOME/instance-2082591-1247375381,1800000)
0.18/0.29	c (ff_inout)
0.18/0.29	s SATISFIABLE
0.18/0.29	v 0 1 37 20 46 45 59 58 84 83 23 22 45 32 122 123 135 134 139 138 31 20 40 37 111 110 122 136 143 129 0 1 53 20 60 59 75 76 98 83 0 1 11 10 23 22 35 36 71 42 11 10 59 20 75 76 86 85 91 89 0 20 31 26 86 85 99 100 106 107 11 10 68 20 99 100 111 110 129 130 11 12 21 20 35 36 46 45 57 58 43 26 82 47 135 134 148 149 154 153 
0.18/0.29	
0.18/0.29	c Time=111 ms Backtracks=22
0.18/0.29

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2082591-1247375381/watcher-2082591-1247375381 -o /tmp/evaluation-result-2082591-1247375381/solver-2082591-1247375381 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2082591-1247375381 1800 

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): 2000 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


[startup+0 s]
/proc/loadavg: 2.18 2.14 2.06 4/82 23159
/proc/meminfo: memFree=1602528/2055920 swapFree=4192812/4192956
[pid=23159] ppid=23157 vsize=7000 CPUtime=0
/proc/23159/stat : 23159 (bprolog) R 23157 23159 22161 0 -1 4194304 608 0 0 0 0 0 0 0 20 0 1 0 24604355 7168000 326 996147200 134512640 135105188 4294956096 18446744073709551615 134530912 0 0 4096 0 0 0 0 17 0 0 0
/proc/23159/statm: 1750 326 72 144 0 1234 0

[startup+0.134748 s]
/proc/loadavg: 2.18 2.14 2.06 4/82 23159
/proc/meminfo: memFree=1602528/2055920 swapFree=4192812/4192956
[pid=23159] ppid=23157 vsize=62208 CPUtime=0.12
/proc/23159/stat : 23159 (bprolog) R 23157 23159 22161 0 -1 4194304 1109 0 0 0 6 6 0 0 21 0 1 0 24604355 63700992 822 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 0 0 0
/proc/23159/statm: 15552 822 177 144 0 15036 0
Current children cumulated CPU time (s) 0.12
Current children cumulated vsize (KiB) 62208

[startup+0.20176 s]
/proc/loadavg: 2.18 2.14 2.06 4/82 23159
/proc/meminfo: memFree=1602528/2055920 swapFree=4192812/4192956
[pid=23159] ppid=23157 vsize=62200 CPUtime=0.18
/proc/23159/stat : 23159 (bprolog) R 23157 23159 22161 0 -1 4194304 1304 0 0 0 10 8 0 0 21 0 1 0 24604355 63692800 1014 996147200 134512640 135105188 4294956096 18446744073709551615 134669780 0 0 4096 2 0 0 0 17 0 0 0
/proc/23159/statm: 15550 1014 187 144 0 15034 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 62200

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

Child status: 0
Real time (s): 0.298546
CPU time (s): 0.285955
CPU user time (s): 0.197969
CPU system time (s): 0.087986
CPU usage (%): 95.7825
Max. virtual memory (cumulated for all children) (KiB): 62208

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.197969
system time used= 0.087986
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1715
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= 4
involuntary context switches= 144

runsolver used 0.002999 second user time and 0.010998 second system time

The end

Launcher Data 

Begin job on node27 at 2009-07-12 07:09:41
IDJOB=2082591
IDBENCH=57604
IDSOLVER=770
FILE ID=node27/2082591-1247375381
PBS_JOBID= 9507124
Free space on /tmp= 66320 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/super-jobShop/super-jobShop-enddr1/normalized-super-jobShop-enddr1-8.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2082591-1247375381/watcher-2082591-1247375381 -o /tmp/evaluation-result-2082591-1247375381/solver-2082591-1247375381 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2082591-1247375381 1800

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 31da94f2e356bf95fd869137b551c4a1
RANDOM SEED=1063949992

node27.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		: 2800.239
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	: 5521.40
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		: 2800.239
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:       1602944 kB
Buffers:         63132 kB
Cached:         179356 kB
SwapCached:          0 kB
Active:         296760 kB
Inactive:        91884 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1602944 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1520 kB
Writeback:           0 kB
Mapped:         166504 kB
Slab:            49168 kB
Committed_AS:   386820 kB
PageTables:       2064 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264948 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66320 MiB
End job on node27 at 2009-07-12 07:09:41