Trace number 1091569

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.086986 0.0999709

General information on the benchmark

Namecsp/jobShop-e0ddr2/
normalized-e0ddr2-10-by-5-10.xml
MD5SUM2b46d5afef92305f7a6e417944434d2c
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.029995
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size134
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-1091569-1215275054)
0.00/0.08	c Converted in 26 ms
0.00/0.08	c solving(HOME/instance-1091569-1215275054,1800000)
0.00/0.09	c (ff_inout)
0.00/0.09	s SATISFIABLE
0.00/0.09	v 0 47 119 131 138 10 43 103 119 130 21 25 89 103 113 0 7 17 26 37 7 26 57 69 80 34 52 131 139 149 15 58 139 150 158 17 37 43 57 64 0 35 69 79 95 11 38 79 89 104 
0.00/0.09	
0.00/0.09	c Time=15 ms
0.00/0.09

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-1091569-1215275054/watcher-1091569-1215275054 -o /tmp/evaluation-result-1091569-1215275054/solver-1091569-1215275054 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1091569-1215275054 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.08 2.02 2.01 4/73 20804
/proc/meminfo: memFree=1720320/2055920 swapFree=4179828/4192956
[pid=20804] ppid=20802 vsize=4780 CPUtime=0
/proc/20804/stat : 20804 (bprolog) R 20802 20804 19008 0 -1 4194304 402 0 0 0 0 0 0 0 20 0 1 0 2006478939 4894720 120 996147200 134512640 134990860 4294956096 18446744073709551615 134530848 0 0 4096 0 0 0 0 17 1 0 0
/proc/20804/statm: 1195 120 72 116 0 706 0

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

Child status: 0
Real time (s): 0.0999709
CPU time (s): 0.086986
CPU user time (s): 0.054991
CPU system time (s): 0.031995
CPU usage (%): 87.0113
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.054991
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= 1246
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= 79

runsolver used 0.003999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node34 at 2008-07-05 18:24:15
IDJOB=1091569
IDBENCH=58564
IDSOLVER=347
FILE ID=node34/1091569-1215275054
PBS_JOBID= 7882190
Free space on /tmp= 66476 MiB

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

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 2b46d5afef92305f7a6e417944434d2c
RANDOM SEED=695000544

node34.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.259
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.259
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:       1720800 kB
Buffers:         43600 kB
Cached:         228336 kB
SwapCached:       7272 kB
Active:         179460 kB
Inactive:       103860 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1720800 kB
SwapTotal:     4192956 kB
SwapFree:      4179828 kB
Dirty:            1400 kB
Writeback:           0 kB
Mapped:          18360 kB
Slab:            36968 kB
Committed_AS:  3557428 kB
PageTables:       1860 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= 66476 MiB
End job on node34 at 2008-07-05 18:24:15