Trace number 1088173

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-prime 1.313UNSAT 0.648901 0.658792

DiagnosticValue
ASSIGNMENTS470
CHECKS162458

General information on the benchmark

Namecsp/rlfapScens11/
normalized-scen11-f12.xml
MD5SUM923ef4c26cd9096899ec03d5df91c70b
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.648901
Satisfiable
(Un)Satisfiability was proved
Number of variables680
Number of constraints4103
Maximum constraint arity2
Maximum domain size32
Number of constraints which are defined in extension0
Number of constraints which are defined in intension4103
Global constraints used (with number of constraints)

Solver Data (download as text)

0.18/0.20	c mistral-prime version 1.313
0.58/0.64	s UNSATISFIABLE
0.58/0.64	d CHECKS 162458
0.58/0.64	d ASSIGNMENTS 470

Verifier Data (download as text)

No possible verification on an UNSAT instance

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-1088173-1215245842/watcher-1088173-1215245842 -o /tmp/evaluation-result-1088173-1215245842/solver-1088173-1215245842 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1088173-1215245842.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

[startup+0 s]
/proc/loadavg: 3.44 2.86 2.61 3/79 5066
/proc/meminfo: memFree=1500876/2055920 swapFree=4147308/4192956
[pid=5066] ppid=5064 vsize=18572 CPUtime=0
/proc/5066/stat : 5066 (runsolver) R 5064 1466 1466 0 -1 4194368 12 0 0 0 0 0 0 0 20 0 1 0 680310917 19017728 290 996147200 4194304 4296836 548682068496 18446744073709551615 256365024695 0 0 4096 24578 0 0 0 17 1 0 0
/proc/5066/statm: 4643 290 255 25 0 2626 0
Current StackSize limit: 10240 KiB


[startup+0.063328 s]
/proc/loadavg: 3.44 2.86 2.61 3/79 5066
/proc/meminfo: memFree=1500876/2055920 swapFree=4147308/4192956
[pid=5066] ppid=5064 vsize=5360 CPUtime=0.05
/proc/5066/stat : 5066 (xsolve) R 5064 5066 1466 0 -1 4194304 675 0 0 0 5 0 0 0 18 0 1 0 680310917 5488640 641 996147200 134512640 135237403 4294956240 18446744073709551615 10694317 0 0 4096 0 0 0 0 17 1 0 0
/proc/5066/statm: 1340 641 377 176 0 244 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 5360

[startup+0.101332 s]
/proc/loadavg: 3.44 2.86 2.61 3/79 5066
/proc/meminfo: memFree=1500876/2055920 swapFree=4147308/4192956
[pid=5066] ppid=5064 vsize=5920 CPUtime=0.09
/proc/5066/stat : 5066 (xsolve) R 5064 5066 1466 0 -1 4194304 802 0 0 0 9 0 0 0 18 0 1 0 680310917 6062080 768 996147200 134512640 135237403 4294956240 18446744073709551615 134614936 0 0 4096 0 0 0 0 17 1 0 0
/proc/5066/statm: 1480 768 377 176 0 384 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5920

[startup+0.301356 s]
/proc/loadavg: 3.44 2.86 2.61 3/79 5066
/proc/meminfo: memFree=1500876/2055920 swapFree=4147308/4192956
[pid=5066] ppid=5064 vsize=10300 CPUtime=0.28
/proc/5066/stat : 5066 (xsolve) R 5064 5066 1466 0 -1 4194304 1904 0 0 0 28 0 0 0 19 0 1 0 680310917 10547200 1870 996147200 134512640 135237403 4294956240 18446744073709551615 134538933 0 0 4096 0 0 0 0 17 1 0 0
/proc/5066/statm: 2575 1870 400 176 0 1479 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 10300

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

[startup+0.501366 s]
/proc/loadavg: 3.44 2.86 2.61 3/79 5066
/proc/meminfo: memFree=1500876/2055920 swapFree=4147308/4192956
[pid=5066] ppid=5064 vsize=10304 CPUtime=0.48
/proc/5066/stat : 5066 (xsolve) R 5064 5066 1466 0 -1 4194304 1906 0 0 0 48 0 0 0 21 0 1 0 680310917 10551296 1872 996147200 134512640 135237403 4294956240 18446744073709551615 134818690 0 0 4096 0 0 0 0 17 1 0 0
/proc/5066/statm: 2576 1872 400 176 0 1480 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 10304

[startup+0.601378 s]
/proc/loadavg: 3.44 2.86 2.61 3/79 5066
/proc/meminfo: memFree=1500876/2055920 swapFree=4147308/4192956
[pid=5066] ppid=5064 vsize=10304 CPUtime=0.58
/proc/5066/stat : 5066 (xsolve) R 5064 5066 1466 0 -1 4194304 1906 0 0 0 58 0 0 0 22 0 1 0 680310917 10551296 1872 996147200 134512640 135237403 4294956240 18446744073709551615 135094721 0 0 4096 0 0 0 0 17 1 0 0
/proc/5066/statm: 2576 1872 400 176 0 1480 0
Current children cumulated CPU time (s) 0.58
Current children cumulated vsize (KiB) 10304

Child status: 0
Real time (s): 0.658792
CPU time (s): 0.648901
CPU user time (s): 0.637903
CPU system time (s): 0.010998
CPU usage (%): 98.4986
Max. virtual memory (cumulated for all children) (KiB): 10304

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.637903
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= 1922
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= 6
involuntary context switches= 19

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node90 at 2008-07-05 10:17:23
IDJOB=1088173
IDBENCH=58069
IDSOLVER=358
FILE ID=node90/1088173-1215245842
PBS_JOBID= 7881833
Free space on /tmp= 66556 MiB

SOLVER NAME= Mistral-prime 1.313
BENCH NAME= CPAI08/csp/rlfapScens11/normalized-scen11-f12.xml
COMMAND LINE= HOME/xsolve BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1088173-1215245842/watcher-1088173-1215245842 -o /tmp/evaluation-result-1088173-1215245842/solver-1088173-1215245842 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1088173-1215245842.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 923ef4c26cd9096899ec03d5df91c70b
RANDOM SEED=601213062

node90.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.236
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.236
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:       1501364 kB
Buffers:         14988 kB
Cached:         127304 kB
SwapCached:      37024 kB
Active:         475560 kB
Inactive:        23568 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1501364 kB
SwapTotal:     4192956 kB
SwapFree:      4147308 kB
Dirty:            2136 kB
Writeback:           0 kB
Mapped:         364872 kB
Slab:            39596 kB
Committed_AS:  1355664 kB
PageTables:       2948 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= 66556 MiB
End job on node90 at 2008-07-05 10:17:24