Trace number 198882

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.3418 1.37833

DiagnosticValue
CHECKS31038100
NODES1938

General information on the benchmark

Namerlfap/rlfapScens11/
scen11-f12.xml
MD5SUMae037380847c5677dfcb746e767102e6
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.01784
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables680
Number of constraints4103
Maximum constraint arity2
Maximum domain size32
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.37	s UNSATISFIABLE
1.37	d CHECKS 3.10381e+07
1.37	d NODES 1938
1.37

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/node38/watcher-198882-1168131150 -o ROOT/results/node38/solver-198882-1168131150 -C 1800 -M 900 /tmp/evaluation/198882-1168131150/VALCSP /tmp/evaluation/198882-1168131150/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.86 0.95 0.99 2/68 32695
/proc/meminfo: memFree=1202440/2055920 swapFree=4192812/4192956
[pid=32694] ppid=32685 vsize=4504 CPUtime=0
/proc/32694/stat : 32694 (VALCSP) R 32685 32694 32584 0 -1 4194304 863 0 0 0 0 0 0 0 18 0 1 0 161514744 4612096 842 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 9041531 0 0 4096 0 0 0 0 17 0 0 0
/proc/32694/statm: 1126 849 62 8 0 798 0

[startup+0.102235 s]
/proc/loadavg: 0.86 0.95 0.99 2/68 32695
/proc/meminfo: memFree=1202440/2055920 swapFree=4192812/4192956
[pid=32694] ppid=32685 vsize=10896 CPUtime=0.09
/proc/32694/stat : 32694 (VALCSP) R 32685 32694 32584 0 -1 4194304 2466 0 0 0 9 0 0 0 18 0 1 0 161514744 11157504 2444 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 9041531 0 0 4096 0 0 0 0 17 0 0 0
/proc/32694/statm: 2724 2445 64 8 0 2396 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 10896

[startup+0.510315 s]
/proc/loadavg: 0.86 0.95 0.99 2/68 32695
/proc/meminfo: memFree=1202440/2055920 swapFree=4192812/4192956
[pid=32694] ppid=32685 vsize=24992 CPUtime=0.48
/proc/32694/stat : 32694 (VALCSP) R 32685 32694 32584 0 -1 4194304 5994 0 0 0 46 2 0 0 21 0 1 0 161514744 25591808 5972 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530234 0 0 4096 0 0 0 0 17 1 0 0
/proc/32694/statm: 6248 5972 64 8 0 5920 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 24992

[startup+1.33147 s]
/proc/loadavg: 0.86 0.95 0.99 3/84 32711
/proc/meminfo: memFree=1155080/2055920 swapFree=4192812/4192956
[pid=32694] ppid=32685 vsize=28292 CPUtime=1.28
/proc/32694/stat : 32694 (VALCSP) R 32685 32694 32584 0 -1 4194304 6820 0 0 0 126 2 0 0 25 0 1 0 161514744 28971008 6798 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134520605 0 0 4096 0 0 0 0 17 1 0 0
/proc/32694/statm: 7073 6798 66 8 0 6745 0
Current children cumulated CPU time (s) 1.28
Current children cumulated vsize (KiB) 28292

Child status: 0
Real time (s): 1.37833
CPU time (s): 1.3418
CPU user time (s): 1.3078
CPU system time (s): 0.033994
CPU usage (%): 97.3496
Max. virtual memory (cumulated for all children) (KiB): 28292

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

runsolver used 0.003999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node38 on Sun Jan  7 00:52:31 UTC 2007


IDJOB= 198882
IDBENCH= 3580
FILE ID= node38/198882-1168131150

PBS_JOBID= 3477912

Free space on /tmp= 66514 MiB

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

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  ae037380847c5677dfcb746e767102e6

RANDOM SEED= 168298805

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.267
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.267
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:       1202520 kB
Buffers:         46104 kB
Cached:         714204 kB
SwapCached:          0 kB
Active:         129004 kB
Inactive:       651628 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1202520 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3792 kB
Writeback:           0 kB
Mapped:          30692 kB
Slab:            58336 kB
Committed_AS:  3332708 kB
PageTables:       1792 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= 66514 MiB



End job on node38 on Sun Jan  7 00:52:34 UTC 2007