Trace number 1055300

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.084986 0.0847971

General information on the benchmark

Namecsp/jobShop-e0ddr1/
normalized-e0ddr1-10-by-5-2.xml
MD5SUM4eb8f99621b454ba27d9f51e4d6a63a3
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.021995
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size118
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.08	c bpsolver version 6.27.2008
0.00/0.08	c converting(HOME/instance-1055300-1215059370)
0.00/0.08	c Converted in 18 ms
0.00/0.08	c solving(HOME/instance-1055300-1215059370,1800000)
0.00/0.08	c (ff_inout)
0.00/0.08	s SATISFIABLE
0.00/0.08	v 35 41 110 121 131 21 41 102 110 121 31 48 75 89 100 49 58 130 140 143 0 11 21 37 41 0 3 37 57 65 3 11 52 64 72 6 11 89 102 112 22 25 64 78 87 9 25 118 130 143 
0.00/0.08	
0.00/0.08	c Time=16 ms
0.00/0.08

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-1055300-1215059370/watcher-1055300-1215059370 -o /tmp/evaluation-result-1055300-1215059370/solver-1055300-1215059370 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1055300-1215059370 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.01 2.00 4/80 24586
/proc/meminfo: memFree=1608928/2055920 swapFree=4191676/4192956
[pid=24586] ppid=24584 vsize=56080 CPUtime=0.04
/proc/24586/stat : 24586 (bprolog) R 24584 24586 24063 0 -1 4194304 1098 0 0 0 2 2 0 0 18 0 1 0 117932307 57425920 811 996147200 134512640 134990860 4294956112 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 0 0 0
/proc/24586/statm: 14020 811 178 116 0 13531 0

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

Child status: 0
Real time (s): 0.0847971
CPU time (s): 0.084986
CPU user time (s): 0.048992
CPU system time (s): 0.035994
CPU usage (%): 100.223
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.048992
system time used= 0.035994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1247
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= 2

runsolver used 0.002999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node63 at 2008-07-03 06:29:30
IDJOB=1055300
IDBENCH=56813
IDSOLVER=347
FILE ID=node63/1055300-1215059370
PBS_JOBID= 7875191
Free space on /tmp= 66508 MiB

SOLVER NAME= bpsolver 2008-06-27
BENCH NAME= CPAI08/csp/jobShop-e0ddr1/normalized-e0ddr1-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-1055300-1215059370/watcher-1055300-1215059370 -o /tmp/evaluation-result-1055300-1215059370/solver-1055300-1215059370 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1055300-1215059370 1800

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 4eb8f99621b454ba27d9f51e4d6a63a3
RANDOM SEED=763617503

node63.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.256
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.256
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1609344 kB
Buffers:          8636 kB
Cached:         136080 kB
SwapCached:        260 kB
Active:         350332 kB
Inactive:        40680 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1609344 kB
SwapTotal:     4192956 kB
SwapFree:      4191676 kB
Dirty:            1444 kB
Writeback:           0 kB
Mapped:         267648 kB
Slab:            40528 kB
Committed_AS:  1073032 kB
PageTables:       2104 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66508 MiB
End job on node63 at 2008-07-03 06:29:30