Trace number 2075782

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.089986 0.095508

General information on the benchmark

Namecsp/jobShop-enddr1/
normalized-enddr1-10-by-5-10.xml
MD5SUM32d5c6e0f1983e695c4d23bb63a1ba6e
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.037993
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size125
Number of constraints which are defined in extension0
Number of constraints which are defined in intension265
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-2075782-1247362076)
0.00/0.07	c Converted in 27 ms
0.00/0.08	c solving(HOME/instance-2075782-1247362076,1800000)
0.00/0.08	c solving(HOME/instance-2075782-1247362076,1800000)
0.00/0.09	c (ff_inout)
0.00/0.09	s SATISFIABLE
0.00/0.09	v 0 3 7 43 59 7 22 48 63 69 0 14 22 32 43 26 37 125 137 145 43 53 111 125 130 0 10 101 111 116 4 20 71 86 90 37 43 86 101 105 11 20 63 79 90 0 4 32 52 59 
0.00/0.09	
0.00/0.09	c Time=13 ms Backtracks=0
0.00/0.09

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-2075782-1247362076/watcher-2075782-1247362076 -o /tmp/evaluation-result-2075782-1247362076/solver-2075782-1247362076 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2075782-1247362076 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.35 2.17 2.05 4/74 16009
/proc/meminfo: memFree=1843600/2055920 swapFree=4192812/4192956
[pid=16009] ppid=16007 vsize=18576 CPUtime=0
/proc/16009/stat : 16009 (runsolver) R 16007 16009 14704 0 -1 4194368 15 0 0 0 0 0 0 0 23 0 1 0 23273961 19021824 284 996147200 4194304 4302564 548682068528 18446744073709551615 238487661863 0 0 4096 24578 0 0 0 17 1 0 0
/proc/16009/statm: 4644 284 249 26 0 2626 0

[startup+0.0192689 s]
/proc/loadavg: 2.35 2.17 2.05 4/74 16009
/proc/meminfo: memFree=1843600/2055920 swapFree=4192812/4192956
[pid=16009] ppid=16007 vsize=62200 CPUtime=0
/proc/16009/stat : 16009 (bprolog) R 16007 16009 14704 0 -1 4194304 943 0 0 0 0 0 0 0 23 0 1 0 23273961 63692800 659 996147200 134512640 135105188 4294956096 18446744073709551615 2612340 0 0 4096 2 0 0 0 17 1 0 0
/proc/16009/statm: 15550 659 130 144 0 15034 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 62200

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

[startup+0.0192689 s]
/proc/loadavg: 2.35 2.17 2.05 4/74 16009
/proc/meminfo: memFree=1843600/2055920 swapFree=4192812/4192956
[pid=16009] ppid=16007 vsize=62200 CPUtime=0
/proc/16009/stat : 16009 (bprolog) R 16007 16009 14704 0 -1 4194304 943 0 0 0 0 0 0 0 23 0 1 0 23273961 63692800 659 996147200 134512640 135105188 4294956096 18446744073709551615 2612340 0 0 4096 2 0 0 0 17 1 0 0
/proc/16009/statm: 15550 659 130 144 0 15034 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 62200

Child status: 0
Real time (s): 0.095508
CPU time (s): 0.089986
CPU user time (s): 0.057991
CPU system time (s): 0.031995
CPU usage (%): 94.2183
Max. virtual memory (cumulated for all children) (KiB): 62200

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.057991
system time used= 0.031995
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1235
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= 3
involuntary context switches= 83

runsolver used 0.004999 second user time and 0.003999 second system time

The end

Launcher Data 

Begin job on node23 at 2009-07-12 03:27:56
IDJOB=2075782
IDBENCH=56344
IDSOLVER=770
FILE ID=node23/2075782-1247362076
PBS_JOBID= 9506976
Free space on /tmp= 66320 MiB

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

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

MD5SUM BENCH= 32d5c6e0f1983e695c4d23bb63a1ba6e
RANDOM SEED=1558785710

node23.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.277
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.277
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:       1844080 kB
Buffers:         23724 kB
Cached:         103028 kB
SwapCached:          0 kB
Active:         108344 kB
Inactive:        55020 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1844080 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1700 kB
Writeback:           0 kB
Mapped:          47784 kB
Slab:            33700 kB
Committed_AS:   173364 kB
PageTables:       1848 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= 66320 MiB
End job on node23 at 2009-07-12 03:27:56