Trace number 1048199

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
mddc-solv 2008-06-09UNSAT 1.69674 1.71863

DiagnosticValue
CHECKS7595

General information on the benchmark

Namecsp/rand-10-20-10/
normalized-rand-10-20-10-5-10000-11_ext.xml
MD5SUMbf445b0edc5f252db310d539684109ce
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.69674
Satisfiable
(Un)Satisfiability was proved
Number of variables20
Number of constraints5
Maximum constraint arity10
Maximum domain size10
Number of constraints which are defined in extension5
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.08/0.13	c loading... 0.37 secs
0.28/0.38	c smallest 23990
0.28/0.38	c largest 24092
0.28/0.38	c average 24043.8
0.28/0.38	
1.67/1.71	s UNSATISFIABLE
1.67/1.71	d CHECKS 7595
1.67/1.71	c FAILS 745
1.67/1.71	c RESTARTS 4

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-1048199-1215042405/watcher-1048199-1215042405 -o /tmp/evaluation-result-1048199-1215042405/solver-1048199-1215042405 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1048199-1215042405.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: 2.13 2.03 1.91 4/81 13539
/proc/meminfo: memFree=1710456/2055920 swapFree=4097700/4192956
[pid=13539] ppid=13537 vsize=18572 CPUtime=0
/proc/13539/stat : 13539 (runsolver) R 13537 13539 12722 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 1533912689 19017728 292 996147200 4194304 4296836 548682068496 18446744073709551615 268213742887 0 0 4096 24578 0 0 0 17 1 0 0
/proc/13539/statm: 4643 292 257 25 0 2626 0

[startup+0.0641041 s]
/proc/loadavg: 2.13 2.03 1.91 4/81 13539
/proc/meminfo: memFree=1710456/2055920 swapFree=4097700/4192956
[pid=13539] ppid=13537 vsize=9544 CPUtime=0.04
/proc/13539/stat : 13539 (solver) R 13537 13539 12722 0 -1 4194304 2680 0 0 0 4 0 0 0 18 0 1 0 1533912689 9773056 1623 996147200 134512640 134773262 4294956256 18446744073709551615 134603725 0 0 4096 0 0 0 0 17 1 0 0
/proc/13539/statm: 2386 1623 336 63 0 1403 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 9544

[startup+0.102109 s]
/proc/loadavg: 2.13 2.03 1.91 4/81 13539
/proc/meminfo: memFree=1710456/2055920 swapFree=4097700/4192956
[pid=13539] ppid=13537 vsize=10036 CPUtime=0.08
/proc/13539/stat : 13539 (solver) R 13537 13539 12722 0 -1 4194304 2821 0 0 0 8 0 0 0 18 0 1 0 1533912689 10276864 1764 996147200 134512640 134773262 4294956256 18446744073709551615 134531177 0 0 4096 0 0 0 0 17 1 0 0
/proc/13539/statm: 2509 1764 338 63 0 1526 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 10036

[startup+0.301133 s]
/proc/loadavg: 2.13 2.03 1.91 4/81 13539
/proc/meminfo: memFree=1710456/2055920 swapFree=4097700/4192956
[pid=13539] ppid=13537 vsize=12472 CPUtime=0.28
/proc/13539/stat : 13539 (solver) R 13537 13539 12722 0 -1 4194304 3430 0 0 0 27 1 0 0 19 0 1 0 1533912689 12771328 2373 996147200 134512640 134773262 4294956256 18446744073709551615 9707099 0 0 4096 0 0 0 0 17 1 0 0
/proc/13539/statm: 3118 2373 338 63 0 2135 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 12472

[startup+0.701176 s]
/proc/loadavg: 2.13 2.03 1.91 4/81 13539
/proc/meminfo: memFree=1710456/2055920 swapFree=4097700/4192956
[pid=13539] ppid=13537 vsize=9856 CPUtime=0.68
/proc/13539/stat : 13539 (solver) R 13537 13539 12722 0 -1 4194304 3987 0 0 0 67 1 0 0 23 0 1 0 1533912689 10092544 1834 996147200 134512640 134773262 4294956256 18446744073709551615 134530129 0 0 4096 0 0 0 0 17 1 0 0
/proc/13539/statm: 2464 1834 364 63 0 1481 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 9856

[startup+1.50227 s]
/proc/loadavg: 2.13 2.03 1.91 3/82 13540
/proc/meminfo: memFree=1704432/2055920 swapFree=4097700/4192956
[pid=13539] ppid=13537 vsize=9856 CPUtime=1.47
/proc/13539/stat : 13539 (solver) R 13537 13539 12722 0 -1 4194304 3987 0 0 0 146 1 0 0 25 0 1 0 1533912689 10092544 1834 996147200 134512640 134773262 4294956256 18446744073709551615 134529931 0 0 4096 0 0 0 0 17 1 0 0
/proc/13539/statm: 2464 1834 364 63 0 1481 0
Current children cumulated CPU time (s) 1.47
Current children cumulated vsize (KiB) 9856

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

[startup+1.70229 s]
/proc/loadavg: 2.13 2.03 1.91 3/82 13540
/proc/meminfo: memFree=1704432/2055920 swapFree=4097700/4192956
[pid=13539] ppid=13537 vsize=9856 CPUtime=1.67
/proc/13539/stat : 13539 (solver) R 13537 13539 12722 0 -1 4194304 3987 0 0 0 166 1 0 0 25 0 1 0 1533912689 10092544 1834 996147200 134512640 134773262 4294956256 18446744073709551615 134529679 0 0 4096 0 0 0 0 17 1 0 0
/proc/13539/statm: 2464 1834 364 63 0 1481 0
Current children cumulated CPU time (s) 1.67
Current children cumulated vsize (KiB) 9856

Child status: 0
Real time (s): 1.71863
CPU time (s): 1.69674
CPU user time (s): 1.68074
CPU system time (s): 0.015997
CPU usage (%): 98.7264
Max. virtual memory (cumulated for all children) (KiB): 12472

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

runsolver used 0.005999 second user time and 0.008998 second system time

The end

Launcher Data (download as text)

Begin job on node32 at 2008-07-03 01:46:45
IDJOB=1048199
IDBENCH=54352
IDSOLVER=311
FILE ID=node32/1048199-1215042405
PBS_JOBID= 7875110
Free space on /tmp= 66540 MiB

SOLVER NAME= mddc-solv 2008-06-09
BENCH NAME= CPAI08/csp/rand-10-20-10/normalized-rand-10-20-10-5-10000-11_ext.xml
COMMAND LINE= HOME/solver BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1048199-1215042405/watcher-1048199-1215042405 -o /tmp/evaluation-result-1048199-1215042405/solver-1048199-1215042405 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1048199-1215042405.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= bf445b0edc5f252db310d539684109ce
RANDOM SEED=1832590915

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:       1710936 kB
Buffers:          5012 kB
Cached:          82836 kB
SwapCached:      88000 kB
Active:         276156 kB
Inactive:        12996 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1710936 kB
SwapTotal:     4192956 kB
SwapFree:      4097700 kB
Dirty:            2508 kB
Writeback:           0 kB
Mapped:         214996 kB
Slab:            40316 kB
Committed_AS:  3968648 kB
PageTables:       2292 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= 66540 MiB
End job on node32 at 2008-07-03 01:46:47