Trace number 1074161

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.12983 1.13636

DiagnosticValue
CHECKS27042

General information on the benchmark

Namecsp/modifiedRenault/
normalized-renault-mod-23_ext.xml
MD5SUMdb38f8bb6895261d628d599ea184adb2
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 benchmark0.726888
Satisfiable
(Un)Satisfiability was proved
Number of variables111
Number of constraints159
Maximum constraint arity10
Maximum domain size42
Number of constraints which are defined in extension159
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.00	c loading... 1.01 secs
1.00/1.01	c smallest 4
1.00/1.01	c largest 354
1.00/1.01	c average 48.2254
1.00/1.01	
1.09/1.13	s UNSATISFIABLE
1.09/1.13	d CHECKS 27042
1.09/1.13	c FAILS 579
1.09/1.13	c RESTARTS 1

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-1074161-1215178151/watcher-1074161-1215178151 -o /tmp/evaluation-result-1074161-1215178151/solver-1074161-1215178151 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1074161-1215178151.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: 3.31 3.20 2.65 4/80 28599
/proc/meminfo: memFree=1701524/2055920 swapFree=4146768/4192956
[pid=28599] ppid=28597 vsize=8820 CPUtime=0
/proc/28599/stat : 28599 (solver) R 28597 28599 25845 0 -1 4194304 416 0 0 0 0 0 0 0 18 0 1 0 673541728 9031680 383 996147200 134512640 134773262 4294956240 18446744073709551615 10696315 0 0 4096 0 0 0 0 17 0 0 0
/proc/28599/statm: 2205 385 334 63 0 1222 0

[startup+0.077321 s]
/proc/loadavg: 3.31 3.20 2.65 4/80 28599
/proc/meminfo: memFree=1701524/2055920 swapFree=4146768/4192956
[pid=28599] ppid=28597 vsize=9080 CPUtime=0.07
/proc/28599/stat : 28599 (solver) R 28597 28599 25845 0 -1 4194304 1521 0 0 0 7 0 0 0 18 0 1 0 673541728 9297920 1485 996147200 134512640 134773262 4294956240 18446744073709551615 10727127 0 0 4096 0 0 0 0 17 0 0 0
/proc/28599/statm: 2270 1485 338 63 0 1287 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 9080

[startup+0.101322 s]
/proc/loadavg: 3.31 3.20 2.65 4/80 28599
/proc/meminfo: memFree=1701524/2055920 swapFree=4146768/4192956
[pid=28599] ppid=28597 vsize=9300 CPUtime=0.09
/proc/28599/stat : 28599 (solver) R 28597 28599 25845 0 -1 4194304 1532 0 0 0 9 0 0 0 18 0 1 0 673541728 9523200 1496 996147200 134512640 134773262 4294956240 18446744073709551615 134534566 0 0 4096 0 0 0 0 17 0 0 0
/proc/28599/statm: 2325 1496 338 63 0 1342 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9300

[startup+0.301342 s]
/proc/loadavg: 3.31 3.20 2.65 4/80 28599
/proc/meminfo: memFree=1701524/2055920 swapFree=4146768/4192956
[pid=28599] ppid=28597 vsize=9408 CPUtime=0.29
/proc/28599/stat : 28599 (solver) R 28597 28599 25845 0 -1 4194304 1607 0 0 0 29 0 0 0 19 0 1 0 673541728 9633792 1571 996147200 134512640 134773262 4294956240 18446744073709551615 10727127 0 0 4096 0 0 0 0 17 0 0 0
/proc/28599/statm: 2352 1571 338 63 0 1369 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 9408

[startup+0.701384 s]
/proc/loadavg: 3.31 3.20 2.65 4/80 28599
/proc/meminfo: memFree=1701524/2055920 swapFree=4146768/4192956
[pid=28599] ppid=28597 vsize=9640 CPUtime=0.69
/proc/28599/stat : 28599 (solver) R 28597 28599 25845 0 -1 4194304 1627 0 0 0 69 0 0 0 23 0 1 0 673541728 9871360 1591 996147200 134512640 134773262 4294956240 18446744073709551615 134604271 0 0 4096 0 0 0 0 17 0 0 0
/proc/28599/statm: 2410 1591 338 63 0 1427 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 9640

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

[startup+1.10643 s]
/proc/loadavg: 3.31 3.20 2.65 3/81 28600
/proc/meminfo: memFree=1695820/2055920 swapFree=4146768/4192956
[pid=28599] ppid=28597 vsize=5540 CPUtime=1.09
/proc/28599/stat : 28599 (solver) R 28597 28599 25845 0 -1 4194304 1811 0 0 0 108 1 0 0 25 0 1 0 673541728 5672960 748 996147200 134512640 134773262 4294956240 18446744073709551615 134530008 0 0 4096 0 0 0 0 17 0 0 0
/proc/28599/statm: 1385 748 363 63 0 402 0
Current children cumulated CPU time (s) 1.09
Current children cumulated vsize (KiB) 5540

Child status: 0
Real time (s): 1.13636
CPU time (s): 1.12983
CPU user time (s): 1.11583
CPU system time (s): 0.013997
CPU usage (%): 99.4248
Max. virtual memory (cumulated for all children) (KiB): 10228

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

runsolver used 0.003999 second user time and 0.010998 second system time

The end

Launcher Data (download as text)

Begin job on node90 at 2008-07-04 15:29:12
IDJOB=1074161
IDBENCH=56391
IDSOLVER=311
FILE ID=node90/1074161-1215178151
PBS_JOBID= 7881430
Free space on /tmp= 66548 MiB

SOLVER NAME= mddc-solv 2008-06-09
BENCH NAME= CPAI08/csp/modifiedRenault/normalized-renault-mod-23_ext.xml
COMMAND LINE= HOME/solver BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1074161-1215178151/watcher-1074161-1215178151 -o /tmp/evaluation-result-1074161-1215178151/solver-1074161-1215178151 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1074161-1215178151.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= db38f8bb6895261d628d599ea184adb2
RANDOM SEED=751234138

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:       1701940 kB
Buffers:         28164 kB
Cached:         120772 kB
SwapCached:      37656 kB
Active:         253180 kB
Inactive:        42596 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1701940 kB
SwapTotal:     4192956 kB
SwapFree:      4146768 kB
Dirty:            3480 kB
Writeback:           0 kB
Mapped:         152800 kB
Slab:            42612 kB
Committed_AS:  1076720 kB
PageTables:       2632 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= 66548 MiB
End job on node90 at 2008-07-04 15:29:13