Trace number 1073886

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
spider 2008-06-14UNSAT 1.57276 1.592

DiagnosticValue
ASSIGNMENTS242
CHECKS202317

General information on the benchmark

Namecsp/modifiedRenault/
normalized-renault-mod-37_ext.xml
MD5SUM08598072886ba97176539d03f5f4ce66
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.678896
Satisfiable
(Un)Satisfiability was proved
Number of variables111
Number of constraints154
Maximum constraint arity10
Maximum domain size42
Number of constraints which are defined in extension154
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

1.47/1.59	s UNSATISFIABLE
1.47/1.59	d CHECKS 202317
1.47/1.59	d ASSIGNMENTS 242

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-1073886-1215177770/watcher-1073886-1215177770 -o /tmp/evaluation-result-1073886-1215177770/solver-1073886-1215177770 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/run -c HOME/instance-1073886-1215177770.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.10 2.10 2.03 4/81 27125
/proc/meminfo: memFree=1642336/2055920 swapFree=4179736/4192956
[pid=27125] ppid=27123 vsize=18572 CPUtime=0
/proc/27125/stat : 27125 (runsolver) R 27123 27125 23978 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 1996745939 19017728 292 996147200 4194304 4296836 548682068480 18446744073709551615 237947645223 0 0 4096 24578 0 0 0 17 1 0 0
/proc/27125/statm: 4643 292 257 25 0 2626 0

[startup+0.106484 s]
/proc/loadavg: 2.10 2.10 2.03 4/81 27125
/proc/meminfo: memFree=1642336/2055920 swapFree=4179736/4192956
[pid=27125] ppid=27123 vsize=4684 CPUtime=0.09
/proc/27125/stat : 27125 (ld-linux.so.2) R 27123 27125 23978 0 -1 4194304 763 0 0 0 9 0 0 0 18 0 1 0 1996745939 4796416 494 996147200 1448431616 1448550632 4294956272 18446744073709551615 134610514 0 0 4096 0 0 0 0 17 1 0 0
/proc/27125/statm: 1171 494 328 29 0 161 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4684

[startup+0.202498 s]
/proc/loadavg: 2.10 2.10 2.03 4/81 27125
/proc/meminfo: memFree=1642336/2055920 swapFree=4179736/4192956
[pid=27125] ppid=27123 vsize=5220 CPUtime=0.18
/proc/27125/stat : 27125 (ld-linux.so.2) R 27123 27125 23978 0 -1 4194304 872 0 0 0 18 0 0 0 18 0 1 0 1996745939 5345280 603 996147200 1448431616 1448550632 4294956272 18446744073709551615 134563737 0 0 4096 0 0 0 0 17 1 0 0
/proc/27125/statm: 1305 603 328 29 0 295 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 5220

[startup+0.302513 s]
/proc/loadavg: 2.10 2.10 2.03 4/81 27125
/proc/meminfo: memFree=1642336/2055920 swapFree=4179736/4192956
[pid=27125] ppid=27123 vsize=6852 CPUtime=0.28
/proc/27125/stat : 27125 (ld-linux.so.2) R 27123 27125 23978 0 -1 4194304 1028 0 0 0 28 0 0 0 19 0 1 0 1996745939 7016448 759 996147200 1448431616 1448550632 4294956272 18446744073709551615 134561244 0 0 4096 0 0 0 0 17 1 0 0
/proc/27125/statm: 1713 759 328 29 0 703 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 6852

[startup+0.701578 s]
/proc/loadavg: 2.10 2.10 2.03 4/81 27125
/proc/meminfo: memFree=1642336/2055920 swapFree=4179736/4192956
[pid=27125] ppid=27123 vsize=7732 CPUtime=0.68
/proc/27125/stat : 27125 (ld-linux.so.2) R 27123 27125 23978 0 -1 4194304 1450 0 0 0 67 1 0 0 23 0 1 0 1996745939 7917568 1181 996147200 1448431616 1448550632 4294956272 18446744073709551615 134618466 0 0 4096 0 0 0 0 17 1 0 0
/proc/27125/statm: 1933 1181 328 29 0 923 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 7732

[startup+1.50171 s]
/proc/loadavg: 2.10 2.10 2.03 3/82 27126
/proc/meminfo: memFree=1637080/2055920 swapFree=4179736/4192956
[pid=27125] ppid=27123 vsize=15900 CPUtime=1.47
/proc/27125/stat : 27125 (ld-linux.so.2) R 27123 27125 23978 0 -1 4194304 3593 0 0 0 146 1 0 0 25 0 1 0 1996745939 16281600 3324 996147200 1448431616 1448550632 4294956272 18446744073709551615 134534875 0 0 4096 0 0 0 0 17 1 0 0
/proc/27125/statm: 3975 3324 343 29 0 2965 0
Current children cumulated CPU time (s) 1.47
Current children cumulated vsize (KiB) 15900

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

[startup+1.50171 s]
/proc/loadavg: 2.10 2.10 2.03 3/82 27126
/proc/meminfo: memFree=1637080/2055920 swapFree=4179736/4192956
[pid=27125] ppid=27123 vsize=15900 CPUtime=1.47
/proc/27125/stat : 27125 (ld-linux.so.2) R 27123 27125 23978 0 -1 4194304 3593 0 0 0 146 1 0 0 25 0 1 0 1996745939 16281600 3324 996147200 1448431616 1448550632 4294956272 18446744073709551615 134534875 0 0 4096 0 0 0 0 17 1 0 0
/proc/27125/statm: 3975 3324 343 29 0 2965 0
Current children cumulated CPU time (s) 1.47
Current children cumulated vsize (KiB) 15900

Child status: 0
Real time (s): 1.592
CPU time (s): 1.57276
CPU user time (s): 1.55076
CPU system time (s): 0.021996
CPU usage (%): 98.7916
Max. virtual memory (cumulated for all children) (KiB): 15900

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

runsolver used 0.003999 second user time and 0.008998 second system time

The end

Launcher Data (download as text)

Begin job on node69 at 2008-07-04 15:22:51
IDJOB=1073886
IDBENCH=56378
IDSOLVER=328
FILE ID=node69/1073886-1215177770
PBS_JOBID= 7881469
Free space on /tmp= 66548 MiB

SOLVER NAME= spider 2008-06-14
BENCH NAME= CPAI08/csp/modifiedRenault/normalized-renault-mod-37_ext.xml
COMMAND LINE= HOME/run -c BENCHNAME
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1073886-1215177770/watcher-1073886-1215177770 -o /tmp/evaluation-result-1073886-1215177770/solver-1073886-1215177770 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/run -c HOME/instance-1073886-1215177770.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 08598072886ba97176539d03f5f4ce66
RANDOM SEED=1304796418

node69.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.259
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.259
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:       1642880 kB
Buffers:         41820 kB
Cached:         128976 kB
SwapCached:       7092 kB
Active:         294040 kB
Inactive:        58872 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1642880 kB
SwapTotal:     4192956 kB
SwapFree:      4179736 kB
Dirty:            4420 kB
Writeback:           0 kB
Mapped:         198156 kB
Slab:            44844 kB
Committed_AS:  4192444 kB
PageTables:       2304 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 node69 at 2008-07-04 15:22:52