Trace number 1087999

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 2008-06-27SAT 0.095984 0.103913

General information on the benchmark

Namecsp/jobShop-enddr2/
normalized-enddr2-10-by-5-2.xml
MD5SUMfea200bc532eadb4e0a8fa66a5351b7c
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.022995
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size139
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 (download as text)

0.00/0.02	c bpsolver version 6.27.2008
0.00/0.02	c converting(HOME/instance-1087999-1215245687)
0.00/0.07	c Converted in 33 ms
0.00/0.07	c solving(HOME/instance-1087999-1215245687,1800000)
0.00/0.10	c (ff_inout)
0.00/0.10	s SATISFIABLE
0.00/0.10	v 0 78 136 146 167 53 67 128 136 157 35 56 66 79 82 29 69 107 118 127 21 27 32 47 58 27 35 116 128 141 4 43 79 91 98 0 4 12 32 43 15 59 91 107 118 12 21 47 60 69 
0.00/0.10	
0.00/0.10	c Time=23 ms
0.00/0.10

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-1087999-1215245687/watcher-1087999-1215245687 -o /tmp/evaluation-result-1087999-1215245687/solver-1087999-1215245687 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1087999-1215245687 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): 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.00 2.02 2.01 4/81 13133
/proc/meminfo: memFree=1025416/2055920 swapFree=4117580/4192956
[pid=13133] ppid=13131 vsize=4780 CPUtime=0
/proc/13133/stat : 13133 (bprolog) R 13131 13133 12199 0 -1 4194304 373 0 0 0 0 0 0 0 20 0 1 0 2003542415 4894720 91 996147200 134512640 134990860 4294956096 18446744073709551615 134530848 0 0 4096 0 0 0 0 17 1 0 0
/proc/13133/statm: 1195 91 72 116 0 706 0

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

Child status: 0
Real time (s): 0.103913
CPU time (s): 0.095984
CPU user time (s): 0.074988
CPU system time (s): 0.020996
CPU usage (%): 92.3696
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.074988
system time used= 0.020996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1249
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= 5
involuntary context switches= 79

runsolver used 0.003999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node30 at 2008-07-05 10:14:47
IDJOB=1087999
IDBENCH=58060
IDSOLVER=347
FILE ID=node30/1087999-1215245687
PBS_JOBID= 7882003
Free space on /tmp= 66548 MiB

SOLVER NAME= bpsolver 2008-06-27
BENCH NAME= CPAI08/csp/jobShop-enddr2/normalized-enddr2-10-by-5-2.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1087999-1215245687/watcher-1087999-1215245687 -o /tmp/evaluation-result-1087999-1215245687/solver-1087999-1215245687 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1087999-1215245687 1800

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= fea200bc532eadb4e0a8fa66a5351b7c
RANDOM SEED=818598512

node30.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.218
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.218
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:       1025896 kB
Buffers:          6804 kB
Cached:         120236 kB
SwapCached:      69140 kB
Active:         913436 kB
Inactive:        60012 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1025896 kB
SwapTotal:     4192956 kB
SwapFree:      4117580 kB
Dirty:            1904 kB
Writeback:           0 kB
Mapped:         862916 kB
Slab:            40308 kB
Committed_AS:  4427160 kB
PageTables:       3408 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= 66548 MiB
End job on node30 at 2008-07-05 10:14:47