Trace number 267991

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, and are wall clock time (not CPU 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
VALCSP 3.1UNSAT 1.44178 1.45427

DiagnosticValue
CHECKS25069900
NODES8408

General information on the benchmark

Namerlfap/rlfapGraphsMod/
graph14-f28.xml
MD5SUM20f9358485fb6b663286405b27294657
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 benchmark2.93755
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables916
Number of constraints4638
Maximum constraint arity2
Maximum domain size18
Number of constraints which are defined in extension0
Number of constraints which are defined in intension4638
Global constraints used (with number of constraints)

Solver Data (download as text)

1.44	s UNSATISFIABLE
1.44	d CHECKS 2.50699e+07
1.44	d NODES 8408

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node10/watcher-267991-1168977862 -o ROOT/results/node10/solver-267991-1168977862 -C 1800 -M 900 /tmp/evaluation/267991-1168977862/VALCSP /tmp/evaluation/267991-1168977862/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 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

/proc/loadavg: 0.42 0.10 0.03 3/86 12112
/proc/meminfo: memFree=1625272/2055920 swapFree=4178232/4192956
[pid=12111] ppid=12109 vsize=1336 CPUtime=0
/proc/12111/stat : 12111 (VALCSP) R 12109 12111 11750 0 -1 4194304 77 0 0 0 0 0 0 0 20 0 1 0 246182053 1368064 55 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 9367632 0 0 4096 0 0 0 0 17 1 0 0
/proc/12111/statm: 334 55 42 8 0 6 0

[startup+0.103589 s]
/proc/loadavg: 0.42 0.10 0.03 3/86 12112
/proc/meminfo: memFree=1625272/2055920 swapFree=4178232/4192956
[pid=12111] ppid=12109 vsize=14804 CPUtime=0.09
/proc/12111/stat : 12111 (VALCSP) R 12109 12111 11750 0 -1 4194304 3446 0 0 0 8 1 0 0 20 0 1 0 246182053 15159296 3424 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134528624 0 0 4096 0 0 0 0 17 1 0 0
/proc/12111/statm: 3701 3424 64 8 0 3373 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 14804

[startup+0.511647 s]
/proc/loadavg: 0.42 0.10 0.03 3/86 12112
/proc/meminfo: memFree=1625272/2055920 swapFree=4178232/4192956
[pid=12111] ppid=12109 vsize=25768 CPUtime=0.5
/proc/12111/stat : 12111 (VALCSP) R 12109 12111 11750 0 -1 4194304 6199 0 0 0 48 2 0 0 24 0 1 0 246182053 26386432 6177 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134524970 0 0 4096 0 0 0 0 17 1 0 0
/proc/12111/statm: 6442 6177 66 8 0 6114 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 25768

[startup+1.33576 s]
/proc/loadavg: 0.42 0.10 0.03 3/86 12112
/proc/meminfo: memFree=1600760/2055920 swapFree=4178232/4192956
[pid=12111] ppid=12109 vsize=25768 CPUtime=1.32
/proc/12111/stat : 12111 (VALCSP) R 12109 12111 11750 0 -1 4194304 6199 0 0 0 130 2 0 0 25 0 1 0 246182053 26386432 6177 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134524875 0 0 4096 0 0 0 0 17 1 0 0
/proc/12111/statm: 6442 6177 66 8 0 6114 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 25768

Child status: 0
Real time (s): 1.45427
CPU time (s): 1.44178
CPU user time (s): 1.41279
CPU system time (s): 0.028995
CPU usage (%): 99.1413
Max. virtual memory (cumulated for all children) (KiB): 25768

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

runsolver used 0.004999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Tue Jan 16 20:04:29 UTC 2007


IDJOB= 267991
IDBENCH= 3264
IDSOLVER= 90
FILE ID= node10/267991-1168977862

PBS_JOBID= 3565932

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapGraphsMod/graph14-f28.xml
COMMAND LINE= /tmp/evaluation/267991-1168977862/VALCSP /tmp/evaluation/267991-1168977862/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-267991-1168977862 -o ROOT/results/node10/solver-267991-1168977862 -C 1800 -M 900  /tmp/evaluation/267991-1168977862/VALCSP /tmp/evaluation/267991-1168977862/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  20f9358485fb6b663286405b27294657

RANDOM SEED= 712258768

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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.232
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.232
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:       1625688 kB
Buffers:         42716 kB
Cached:         276836 kB
SwapCached:       2360 kB
Active:         178732 kB
Inactive:       179384 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1625688 kB
SwapTotal:     4192956 kB
SwapFree:      4178232 kB
Dirty:             780 kB
Writeback:           0 kB
Mapped:          48768 kB
Slab:            57064 kB
Committed_AS:  6719876 kB
PageTables:       2172 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= 66564 MiB



End job on node10 on Tue Jan 16 20:04:35 UTC 2007