Trace number 2078763

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.086985 0.101601

General information on the benchmark

Namecsp/jobShop-e0ddr1/
normalized-e0ddr1-10-by-5-10.xml
MD5SUMb10ff76d89f0aa1b94e437a7f1e524d7
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.030994
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size119
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.03	c bpsolver version 6.29.2009
0.00/0.03	c converting(HOME/instance-2078763-1247367476)
0.00/0.08	c Converted in 26 ms
0.00/0.09	c solving(HOME/instance-2078763-1247367476,1800000)
0.00/0.09	c solving(HOME/instance-2078763-1247367476,1800000)
0.00/0.09	c (ff_inout)
0.00/0.09	s SATISFIABLE
0.00/0.09	v 0 3 7 35 46 7 14 37 52 58 0 35 74 90 101 24 35 99 111 119 18 24 60 78 83 0 7 111 121 126 29 35 84 99 110 43 49 121 136 140 11 20 52 68 78 0 4 21 39 59 
0.00/0.10	
0.00/0.10	c Time=12 ms Backtracks=0
0.00/0.10

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-2078763-1247367476/watcher-2078763-1247367476 -o /tmp/evaluation-result-2078763-1247367476/solver-2078763-1247367476 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2078763-1247367476 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.26 2.53 2.44 4/81 28244
/proc/meminfo: memFree=1457880/2055920 swapFree=4192812/4192956
[pid=28244] ppid=28242 vsize=5596 CPUtime=0
/proc/28244/stat : 28244 (bprolog) R 28242 28244 23701 0 -1 4194304 293 0 0 0 0 0 0 0 20 0 1 0 23815086 5730304 24 996147200 134512640 135105188 4294956096 18446744073709551615 7893291 0 0 4096 0 0 0 0 17 1 0 0
/proc/28244/statm: 1399 24 18 144 0 1229 0

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

Child status: 0
Real time (s): 0.101601
CPU time (s): 0.086985
CPU user time (s): 0.053991
CPU system time (s): 0.032994
CPU usage (%): 85.6143
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.053991
system time used= 0.032994
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= 4
involuntary context switches= 83

runsolver used 0.004999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node5 at 2009-07-12 04:57:56
IDJOB=2078763
IDBENCH=56810
IDSOLVER=770
FILE ID=node5/2078763-1247367476
PBS_JOBID= 9507038
Free space on /tmp= 66432 MiB

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

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

MD5SUM BENCH= b10ff76d89f0aa1b94e437a7f1e524d7
RANDOM SEED=63518341

node5.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.258
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.258
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:       1458296 kB
Buffers:          8176 kB
Cached:          75056 kB
SwapCached:          0 kB
Active:         525644 kB
Inactive:        20612 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1458296 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2152 kB
Writeback:           0 kB
Mapped:         483516 kB
Slab:            35620 kB
Committed_AS:   671608 kB
PageTables:       2712 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= 66428 MiB
End job on node5 at 2009-07-12 04:57:56