Trace number 198804

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.0UNSAT 1.66975 1.67175

DiagnosticValue
CHECKS46352700
NODES2178

General information on the benchmark

Namerlfap/rlfapScens11/
scen11-f10.xml
MD5SUMd7f7cf5b131886a3ab2e0dc3439adef6
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 benchmark1.67974
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables680
Number of constraints4103
Maximum constraint arity2
Maximum domain size34
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)

1.66	s UNSATISFIABLE
1.66	d CHECKS 4.63527e+07
1.66	d NODES 2178
1.66	

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/node40/watcher-198804-1168130941 -o ROOT/results/node40/solver-198804-1168130941 -C 1800 -M 900 /tmp/evaluation/198804-1168130941/VALCSP /tmp/evaluation/198804-1168130941/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: 1.00 1.00 0.93 2/65 10053
/proc/meminfo: memFree=1701600/2055920 swapFree=4192812/4192956
[pid=10052] ppid=10050 vsize=3844 CPUtime=0
/proc/10052/stat : 10052 (VALCSP) R 10050 10052 9500 0 -1 4194304 714 0 0 0 0 0 0 0 18 0 1 0 161493445 3936256 692 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 7345787 0 0 4096 0 0 0 0 17 1 0 0
/proc/10052/statm: 994 699 62 8 0 666 0

[startup+0.102486 s]
/proc/loadavg: 1.00 1.00 0.93 2/65 10053
/proc/meminfo: memFree=1701600/2055920 swapFree=4192812/4192956
[pid=10052] ppid=10050 vsize=10644 CPUtime=0.09
/proc/10052/stat : 10052 (VALCSP) R 10050 10052 9500 0 -1 4194304 2405 0 0 0 9 0 0 0 18 0 1 0 161493445 10899456 2383 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 7345787 0 0 4096 0 0 0 0 17 1 0 0
/proc/10052/statm: 2661 2383 64 8 0 2333 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 10644

[startup+0.510537 s]
/proc/loadavg: 1.00 1.00 0.93 2/65 10053
/proc/meminfo: memFree=1701600/2055920 swapFree=4192812/4192956
[pid=10052] ppid=10050 vsize=25228 CPUtime=0.5
/proc/10052/stat : 10052 (VALCSP) R 10050 10052 9500 0 -1 4194304 6050 0 0 0 47 3 0 0 21 0 1 0 161493445 25833472 6028 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 7349197 0 0 4096 0 0 0 0 17 1 0 0
/proc/10052/statm: 6307 6028 64 8 0 5979 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 25228

[startup+1.33064 s]
/proc/loadavg: 1.00 1.00 0.93 2/65 10053
/proc/meminfo: memFree=1673504/2055920 swapFree=4192812/4192956
[pid=10052] ppid=10050 vsize=29356 CPUtime=1.31
/proc/10052/stat : 10052 (VALCSP) R 10050 10052 9500 0 -1 4194304 7099 0 0 0 128 3 0 0 25 0 1 0 161493445 30060544 7077 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134520567 0 0 4096 0 0 0 0 17 1 0 0
/proc/10052/statm: 7339 7077 66 8 0 7011 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 29356

Child status: 0
Real time (s): 1.67175
CPU time (s): 1.66975
CPU user time (s): 1.62475
CPU system time (s): 0.044993
CPU usage (%): 99.8799
Max. virtual memory (cumulated for all children) (KiB): 29356

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

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node40 on Sun Jan  7 00:49:01 UTC 2007


IDJOB= 198804
IDBENCH= 3576
FILE ID= node40/198804-1168130941

PBS_JOBID= 3477676

Free space on /tmp= 66546 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScens11/scen11-f10.xml
COMMAND LINE= /tmp/evaluation/198804-1168130941/VALCSP /tmp/evaluation/198804-1168130941/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node40/watcher-198804-1168130941 -o ROOT/results/node40/solver-198804-1168130941 -C 1800 -M 900  /tmp/evaluation/198804-1168130941/VALCSP /tmp/evaluation/198804-1168130941/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  d7f7cf5b131886a3ab2e0dc3439adef6

RANDOM SEED= 886508522

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.239
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.239
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:       1702080 kB
Buffers:         41728 kB
Cached:         238160 kB
SwapCached:          0 kB
Active:          82224 kB
Inactive:       213680 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1702080 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             576 kB
Writeback:           0 kB
Mapped:          26216 kB
Slab:            44028 kB
Committed_AS:  3150524 kB
PageTables:       1412 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= 66546 MiB



End job on node40 on Sun Jan  7 00:49:03 UTC 2007