Trace number 226490

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 20.3169 20.4034

DiagnosticValue
CHECKS820483000
NODES60564

General information on the benchmark

Nametightness/tightness0.65/
rand-2-40-40-135-650-31_ext.xml
MD5SUM8cfb7f062f28b0701b26adee3b2be2b4
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark16.7964
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables40
Number of constraints135
Maximum constraint arity2
Maximum domain size40
Number of constraints which are defined in extension135
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

20.40	s UNSATISFIABLE
20.40	d CHECKS 8.20483e+08
20.40	d NODES 60564
20.40

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/node51/watcher-226490-1168275574 -o ROOT/results/node51/solver-226490-1168275574 -C 1800 -M 900 /tmp/evaluation/226490-1168275574/VALCSP /tmp/evaluation/226490-1168275574/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: 2.72 2.71 2.63 5/82 31105
/proc/meminfo: memFree=1229328/2055920 swapFree=4192812/4192956
[pid=31104] ppid=31102 vsize=1468 CPUtime=0
/proc/31104/stat : 31104 (VALCSP) R 31102 31104 30351 0 -1 4194304 116 0 0 0 0 0 0 0 20 0 1 0 175955945 1503232 94 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 3079454 0 0 4096 0 0 0 0 17 1 0 0
/proc/31104/statm: 367 94 62 8 0 39 0

[startup+0.105897 s]
/proc/loadavg: 2.72 2.71 2.63 5/82 31105
/proc/meminfo: memFree=1229328/2055920 swapFree=4192812/4192956
[pid=31104] ppid=31102 vsize=1996 CPUtime=0.09
/proc/31104/stat : 31104 (VALCSP) R 31102 31104 30351 0 -1 4194304 230 0 0 0 9 0 0 0 20 0 1 0 175955945 2043904 208 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 3061162 0 0 4096 0 0 0 0 17 1 0 0
/proc/31104/statm: 499 208 62 8 0 171 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1996

[startup+0.51397 s]
/proc/loadavg: 2.72 2.71 2.63 5/82 31105
/proc/meminfo: memFree=1229328/2055920 swapFree=4192812/4192956
[pid=31104] ppid=31102 vsize=4372 CPUtime=0.5
/proc/31104/stat : 31104 (VALCSP) R 31102 31104 30351 0 -1 4194304 852 0 0 0 50 0 0 0 23 0 1 0 175955945 4476928 830 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134539328 0 0 4096 0 0 0 0 17 1 0 0
/proc/31104/statm: 1093 830 63 8 0 765 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 4372

[startup+1.3361 s]
/proc/loadavg: 2.72 2.71 2.63 3/82 31105
/proc/meminfo: memFree=1225808/2055920 swapFree=4192812/4192956
[pid=31104] ppid=31102 vsize=4768 CPUtime=1.32
/proc/31104/stat : 31104 (VALCSP) R 31102 31104 30351 0 -1 4194304 949 0 0 0 132 0 0 0 25 0 1 0 175955945 4882432 927 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134520905 0 0 4096 0 0 0 0 17 1 0 0
/proc/31104/statm: 1192 927 65 8 0 864 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 4768

[startup+2.97538 s]
/proc/loadavg: 2.72 2.71 2.63 3/82 31105
/proc/meminfo: memFree=1225808/2055920 swapFree=4192812/4192956
[pid=31104] ppid=31102 vsize=4768 CPUtime=2.95
/proc/31104/stat : 31104 (VALCSP) R 31102 31104 30351 0 -1 4194304 949 0 0 0 295 0 0 0 25 0 1 0 175955945 4882432 927 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134524799 0 0 4096 0 0 0 0 17 1 0 0
/proc/31104/statm: 1192 927 65 8 0 864 0
Current children cumulated CPU time (s) 2.95
Current children cumulated vsize (KiB) 4768

[startup+6.25494 s]
/proc/loadavg: 2.67 2.70 2.62 3/82 31105
/proc/meminfo: memFree=1225808/2055920 swapFree=4192812/4192956
[pid=31104] ppid=31102 vsize=4768 CPUtime=6.22
/proc/31104/stat : 31104 (VALCSP) R 31102 31104 30351 0 -1 4194304 949 0 0 0 622 0 0 0 25 0 1 0 175955945 4882432 927 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134524623 0 0 4096 0 0 0 0 17 1 0 0
/proc/31104/statm: 1192 927 65 8 0 864 0
Current children cumulated CPU time (s) 6.22
Current children cumulated vsize (KiB) 4768

[startup+12.719 s]
/proc/loadavg: 2.61 2.69 2.62 3/82 31105
/proc/meminfo: memFree=1225808/2055920 swapFree=4192812/4192956
[pid=31104] ppid=31102 vsize=4768 CPUtime=12.66
/proc/31104/stat : 31104 (VALCSP) R 31102 31104 30351 0 -1 4194304 949 0 0 0 1266 0 0 0 25 0 1 0 175955945 4882432 927 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134524708 0 0 4096 0 0 0 0 17 1 0 0
/proc/31104/statm: 1192 927 65 8 0 864 0
Current children cumulated CPU time (s) 12.66
Current children cumulated vsize (KiB) 4768

Child status: 0
Real time (s): 20.4034
CPU time (s): 20.3169
CPU user time (s): 20.3119
CPU system time (s): 0.004999
CPU usage (%): 99.5759
Max. virtual memory (cumulated for all children) (KiB): 4768

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

runsolver used 0.021996 s user time and 0.057991 s system time

The end

Launcher Data (download as text)

Begin job on node51 on Mon Jan  8 16:59:34 UTC 2007


IDJOB= 226490
IDBENCH= 5976
FILE ID= node51/226490-1168275574

PBS_JOBID= 3483208

Free space on /tmp= 66559 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.65/rand-2-40-40-135-650-31_ext.xml
COMMAND LINE= /tmp/evaluation/226490-1168275574/VALCSP /tmp/evaluation/226490-1168275574/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node51/watcher-226490-1168275574 -o ROOT/results/node51/solver-226490-1168275574 -C 1800 -M 900  /tmp/evaluation/226490-1168275574/VALCSP /tmp/evaluation/226490-1168275574/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  8cfb7f062f28b0701b26adee3b2be2b4

RANDOM SEED= 368800439

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.277
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.277
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:       1229808 kB
Buffers:         52424 kB
Cached:         483552 kB
SwapCached:          0 kB
Active:         399876 kB
Inactive:       371884 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1229808 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             488 kB
Writeback:           0 kB
Mapped:         254908 kB
Slab:            39252 kB
Committed_AS:  4701472 kB
PageTables:       2288 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= 66559 MiB



End job on node51 on Mon Jan  8 16:59:55 UTC 2007