Trace number 1067387

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
cpHydra k_40SAT 0.023996 0.0329069

DiagnosticValue
ASSIGNMENTS66
CHECKS5560

General information on the benchmark

Namecsp/bqwh-15-106_glb/
normalized-bqwh-15-106-33_glb.xml
MD5SUM90297af4c0739b9e027e2a5912c70307
Bench CategoryGLOBAL (global constraints)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.011997
Satisfiable
(Un)Satisfiability was proved
Number of variables106
Number of constraints30
Maximum constraint arity8
Maximum domain size6
Number of constraints which are defined in extension0
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)alldifferent(30)

Solver Data (download as text)

0.00/0.00	c cpHydra_k_40 version 0.0
0.00/0.03	c mistral-prime version 1.313
0.00/0.03	s SATISFIABLE
0.00/0.03	v 8 1 4 6 12 13 3 9 5 1 2 3 6 13 8 4 5 11 3 9 13 4 6 12 9 11 0 2 2 7 11 8 1 12 4 7 8 14 13 4 3 5 3 0 12 4 13 11 10 3 14 9 8 5 7 11 3 2 11 5 8 12 0 1 12 2 8 7 5 9 1 10 12 11 2 9 14 7 10 4 1 11 7 13 12 4 6 13 3 14 11 12 5 14 2 7 10 12 8 0 10 9 7 1 11 14
0.00/0.03	d CHECKS 5560
0.00/0.03	d ASSIGNMENTS 66

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-1067387-1215150079/watcher-1067387-1215150079 -o /tmp/evaluation-result-1067387-1215150079/solver-1067387-1215150079 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/cpHydra_k_40/hydra HOME/instance-1067387-1215150079.xml 

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: 1.80 2.12 2.07 4/82 24363
/proc/meminfo: memFree=1723488/2055920 swapFree=4097880/4192956
[pid=24363] ppid=24361 vsize=5360 CPUtime=0
/proc/24363/stat : 24363 (hydra) S 24361 24363 21615 0 -1 4194304 306 124 0 0 0 0 0 0 21 0 1 0 1544680127 5488640 236 996147200 4194304 4889804 548682068816 18446744073709551615 268213740356 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/24363/statm: 1340 236 195 169 0 51 0
[pid=24365] ppid=24363 vsize=2536 CPUtime=0
/proc/24365/stat : 24365 (rm) R 24363 24363 21615 0 -1 4194304 105 0 0 0 0 0 0 0 24 0 1 0 1544680128 2596864 76 996147200 4194304 4227748 548682069024 18446744073709551615 268213934858 0 0 4096 0 0 0 0 17 1 0 0
/proc/24365/statm: 634 76 62 8 0 42 0

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

Child status: 0
Real time (s): 0.0329069
CPU time (s): 0.023996
CPU user time (s): 0.012998
CPU system time (s): 0.010998
CPU usage (%): 72.9208
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.012998
system time used= 0.010998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1688
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= 27
involuntary context switches= 12

runsolver used 0.005999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node32 at 2008-07-04 07:41:19
IDJOB=1067387
IDBENCH=55301
IDSOLVER=366
FILE ID=node32/1067387-1215150079
PBS_JOBID= 7877334
Free space on /tmp= 66552 MiB

SOLVER NAME= cpHydra k_40
BENCH NAME= CPAI08/csp/bqwh-15-106_glb/normalized-bqwh-15-106-33_glb.xml
COMMAND LINE= HOME/cpHydra_k_40/hydra BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1067387-1215150079/watcher-1067387-1215150079 -o /tmp/evaluation-result-1067387-1215150079/solver-1067387-1215150079 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/cpHydra_k_40/hydra HOME/instance-1067387-1215150079.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 90297af4c0739b9e027e2a5912c70307
RANDOM SEED=1559869655

node32.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:       1723968 kB
Buffers:         14520 kB
Cached:         125372 kB
SwapCached:      88316 kB
Active:         243632 kB
Inactive:        35800 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1723968 kB
SwapTotal:     4192956 kB
SwapFree:      4097880 kB
Dirty:           24348 kB
Writeback:           0 kB
Mapped:         155244 kB
Slab:            37084 kB
Committed_AS:  3279628 kB
PageTables:       2216 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= 66528 MiB
End job on node32 at 2008-07-04 07:41:19