Trace number 269020

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 40.7638 40.9309

DiagnosticValue
CHECKS1707620000
NODES6991

General information on the benchmark

Nametightness/tightness0.9/
rand-2-40-180-84-900-35_ext.xml
MD5SUMfb4b4507e7f6489fee0b46aa958528d3
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 benchmark3.9644
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables40
Number of constraints84
Maximum constraint arity2
Maximum domain size180
Number of constraints which are defined in extension84
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

40.92	s UNSATISFIABLE
40.92	d CHECKS 1.70762e+09
40.92	d NODES 6991

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-269020-1168980134 -o ROOT/results/node10/solver-269020-1168980134 -C 1800 -M 900 /tmp/evaluation/269020-1168980134/VALCSP /tmp/evaluation/269020-1168980134/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.36 0.83 1.18 4/81 13371
/proc/meminfo: memFree=1589840/2055920 swapFree=4178232/4192956
[pid=13370] ppid=13368 vsize=1600 CPUtime=0
/proc/13370/stat : 13370 (VALCSP) R 13368 13370 13045 0 -1 4194304 150 0 0 0 0 0 0 0 18 0 1 0 246409813 1638400 128 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 9364590 0 0 4096 0 0 0 0 17 1 0 0
/proc/13370/statm: 400 128 64 8 0 72 0

[startup+0.107672 s]
/proc/loadavg: 0.36 0.83 1.18 4/81 13371
/proc/meminfo: memFree=1589840/2055920 swapFree=4178232/4192956
[pid=13370] ppid=13368 vsize=1600 CPUtime=0.1
/proc/13370/stat : 13370 (VALCSP) R 13368 13370 13045 0 -1 4194304 154 0 0 0 10 0 0 0 18 0 1 0 246409813 1638400 132 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 9366746 0 0 4096 0 0 0 0 17 1 0 0
/proc/13370/statm: 400 132 64 8 0 72 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 1600

[startup+0.515726 s]
/proc/loadavg: 0.36 0.83 1.18 4/81 13371
/proc/meminfo: memFree=1589840/2055920 swapFree=4178232/4192956
[pid=13370] ppid=13368 vsize=1996 CPUtime=0.51
/proc/13370/stat : 13370 (VALCSP) R 13368 13370 13045 0 -1 4194304 258 0 0 0 51 0 0 0 21 0 1 0 246409813 2043904 236 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 9364566 0 0 4096 0 0 0 0 17 1 0 0
/proc/13370/statm: 499 236 64 8 0 171 0
Current children cumulated CPU time (s) 0.51
Current children cumulated vsize (KiB) 1996

[startup+1.33684 s]
/proc/loadavg: 0.36 0.83 1.18 2/81 13371
/proc/meminfo: memFree=1588560/2055920 swapFree=4178232/4192956
[pid=13370] ppid=13368 vsize=2660 CPUtime=1.33
/proc/13370/stat : 13370 (VALCSP) R 13368 13370 13045 0 -1 4194304 422 0 0 0 133 0 0 0 25 0 1 0 246409813 2723840 400 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 9366780 0 0 4096 0 0 0 0 17 1 0 0
/proc/13370/statm: 665 400 64 8 0 337 0
Current children cumulated CPU time (s) 1.33
Current children cumulated vsize (KiB) 2660

[startup+2.97906 s]
/proc/loadavg: 0.41 0.83 1.18 2/81 13371
/proc/meminfo: memFree=1587600/2055920 swapFree=4178232/4192956
[pid=13370] ppid=13368 vsize=4120 CPUtime=2.97
/proc/13370/stat : 13370 (VALCSP) R 13368 13370 13045 0 -1 4194304 792 0 0 0 297 0 0 0 25 0 1 0 246409813 4218880 770 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 9364618 0 0 4096 0 0 0 0 17 1 0 0
/proc/13370/statm: 1030 770 64 8 0 702 0
Current children cumulated CPU time (s) 2.97
Current children cumulated vsize (KiB) 4120

[startup+6.2555 s]
/proc/loadavg: 0.41 0.83 1.18 2/81 13371
/proc/meminfo: memFree=1584592/2055920 swapFree=4178232/4192956
[pid=13370] ppid=13368 vsize=7032 CPUtime=6.24
/proc/13370/stat : 13370 (VALCSP) R 13368 13370 13045 0 -1 4194304 1514 0 0 0 624 0 0 0 25 0 1 0 246409813 7200768 1492 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 9364567 0 0 4096 0 0 0 0 17 1 0 0
/proc/13370/statm: 1758 1492 64 8 0 1430 0
Current children cumulated CPU time (s) 6.24
Current children cumulated vsize (KiB) 7032

[startup+12.7124 s]
/proc/loadavg: 0.50 0.83 1.18 2/81 13374
/proc/meminfo: memFree=1569872/2055920 swapFree=4178232/4192956
[pid=13370] ppid=13368 vsize=21444 CPUtime=12.7
/proc/13370/stat : 13370 (VALCSP) R 13368 13370 13045 0 -1 4194304 5100 0 0 0 1268 2 0 0 25 0 1 0 246409813 21958656 5078 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134524979 0 0 4096 0 0 0 0 17 1 0 0
/proc/13370/statm: 5361 5078 66 8 0 5033 0
Current children cumulated CPU time (s) 12.7
Current children cumulated vsize (KiB) 21444

[startup+25.5171 s]
/proc/loadavg: 0.58 0.84 1.18 3/86 13397
/proc/meminfo: memFree=1563944/2055920 swapFree=4178232/4192956
[pid=13370] ppid=13368 vsize=21444 CPUtime=25.47
/proc/13370/stat : 13370 (VALCSP) R 13368 13370 13045 0 -1 4194304 5100 0 0 0 2545 2 0 0 25 0 1 0 246409813 21958656 5078 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134522084 0 0 4096 0 0 0 0 17 0 0 0
/proc/13370/statm: 5361 5078 66 8 0 5033 0
Current children cumulated CPU time (s) 25.47
Current children cumulated vsize (KiB) 21444

Child status: 0
Real time (s): 40.9309
CPU time (s): 40.7638
CPU user time (s): 40.7388
CPU system time (s): 0.024996
CPU usage (%): 99.5917
Max. virtual memory (cumulated for all children) (KiB): 21444

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

runsolver used 0.049992 s user time and 0.102984 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Tue Jan 16 20:42:22 UTC 2007


IDJOB= 269020
IDBENCH= 5858
IDSOLVER= 90
FILE ID= node10/269020-1168980134

PBS_JOBID= 3565998

Free space on /tmp= 66563 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.9/rand-2-40-180-84-900-35_ext.xml
COMMAND LINE= /tmp/evaluation/269020-1168980134/VALCSP /tmp/evaluation/269020-1168980134/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-269020-1168980134 -o ROOT/results/node10/solver-269020-1168980134 -C 1800 -M 900  /tmp/evaluation/269020-1168980134/VALCSP /tmp/evaluation/269020-1168980134/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  fb4b4507e7f6489fee0b46aa958528d3

RANDOM SEED= 287020907

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:       1590320 kB
Buffers:         44672 kB
Cached:         314116 kB
SwapCached:       2360 kB
Active:         177228 kB
Inactive:       216044 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1590320 kB
SwapTotal:     4192956 kB
SwapFree:      4178232 kB
Dirty:            1964 kB
Writeback:           0 kB
Mapped:          43956 kB
Slab:            57444 kB
Committed_AS:  6695180 kB
PageTables:       2064 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= 66561 MiB



End job on node10 on Tue Jan 16 20:43:12 UTC 2007