Trace number 2081809

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
Mistral 1.545SAT 0.072988 0.079354

DiagnosticValue
ASSIGNMENTS103
CHECKS2307
NODES103

General information on the benchmark

Namecsp/rlfapScensMod/
normalized-scen6-w1.xml
MD5SUM5fcf1b567ccbc0fe4804b04f5a0a591b
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.072988
Satisfiable
(Un)Satisfiability was proved
Number of variables200
Number of constraints319
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension319
Global constraints used (with number of constraints)

Solver Data 

0.00/0.07	c mistral version 1.545
0.00/0.07	s SATISFIABLE
0.00/0.07	v 652 414 792 554 254 16 254 16 254 16 254 16 680 442 254 16 324 86 254 16 764 526 86 324 708 470 254 16 254 16 16 254 792 554 708 470 526 764 16 254 778 540 484 722 652 414 456 694 254 16 16 254 254 16 16 254 380 142 254 16 254 16 16 254 456 694 16 254 512 750 100 338 16 254 254 16 30 268 526 764 30 268 708 470 16 254 708 470 708 470 268 30 30 268 310 72 30 268 58 296 470 708 792 554 456 694 128 366 778 540 254 16 428 666 512 750 310 72 296 58 268 30 428 666 470 708 268 30 526 764 268 30 470 708 484 722 694 456 268 30 736 498 268 30 324 86 666 428 254 16 254 16 484 722 16 254 764 526 764 526 554 792 708 470 778 540 100 338 30 268 708 470 666 428 736 498 498 736 254 16 254 16 470 708 268 30 428 666 268 30 268 30 470 708 268 30 778 540 30 268
0.00/0.07	d CHECKS 2307
0.00/0.07	d ASSIGNMENTS 103
0.00/0.07	d NODES 103 BACKTRACKS 5 FAILURES 5 RUNTIME 0.05 TOTALTIME 0.06 NODES/s 2060 CHECKS/s 46140

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-2081809-1247374412/watcher-2081809-1247374412 -o /tmp/evaluation-result-2081809-1247374412/solver-2081809-1247374412 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2081809-1247374412.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): 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: 1.93 2.00 1.99 4/74 24097
/proc/meminfo: memFree=1203080/2055920 swapFree=4192812/4192956
[pid=24097] ppid=24095 vsize=18576 CPUtime=0
/proc/24097/stat : 24097 (runsolver) R 24095 24097 20092 0 -1 4194368 15 0 0 0 0 0 0 0 18 0 1 0 24507549 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 269028486439 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/24097/statm: 4644 284 249 26 0 2626 0

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

Child status: 0
Real time (s): 0.079354
CPU time (s): 0.072988
CPU user time (s): 0.068989
CPU system time (s): 0.003999
CPU usage (%): 91.9778
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.068989
system time used= 0.003999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 769
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= 14
involuntary context switches= 1

runsolver used 0.001999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node26 at 2009-07-12 06:53:32
IDJOB=2081809
IDBENCH=57499
IDSOLVER=769
FILE ID=node26/2081809-1247374412
PBS_JOBID= 9507081
Free space on /tmp= 66240 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/rlfapScensMod/normalized-scen6-w1.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2081809-1247374412/watcher-2081809-1247374412 -o /tmp/evaluation-result-2081809-1247374412/solver-2081809-1247374412 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2081809-1247374412.xml

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

MD5SUM BENCH= 5fcf1b567ccbc0fe4804b04f5a0a591b
RANDOM SEED=238954299

node26.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.281
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.281
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:       1203560 kB
Buffers:         50908 kB
Cached:         442432 kB
SwapCached:          0 kB
Active:         592476 kB
Inactive:       179680 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1203560 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1556 kB
Writeback:           0 kB
Mapped:         289988 kB
Slab:            64792 kB
Committed_AS:   445160 kB
PageTables:       2364 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= 66236 MiB
End job on node26 at 2009-07-12 06:53:32