Trace number 268994

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 2.36164 2.37189

DiagnosticValue
CHECKS41218500
NODES335

General information on the benchmark

Nametightness/tightness0.8/
rand-2-40-80-103-800-3_ext.xml
MD5SUM2655fa3a8729f18aaa03c51fe9718813
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 benchmark1.9477
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables40
Number of constraints103
Maximum constraint arity2
Maximum domain size80
Number of constraints which are defined in extension103
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

2.36	s UNSATISFIABLE
2.36	d CHECKS 4.12185e+07
2.36	d NODES 335

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-268994-1168980103 -o ROOT/results/node38/solver-268994-1168980103 -C 1800 -M 900 /tmp/evaluation/268994-1168980103/VALCSP /tmp/evaluation/268994-1168980103/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.02 0.44 0.64 2/68 9063
/proc/meminfo: memFree=1646992/2055920 swapFree=4192812/4192956
[pid=9062] ppid=9060 vsize=1468 CPUtime=0
/proc/9062/stat : 9062 (VALCSP) R 9060 9062 8822 0 -1 4194304 127 0 0 0 0 0 0 0 18 0 1 0 246411677 1503232 105 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 9070510 0 0 4096 0 0 0 0 17 1 0 0
/proc/9062/statm: 367 105 64 8 0 39 0

[startup+0.101665 s]
/proc/loadavg: 0.02 0.44 0.64 2/68 9063
/proc/meminfo: memFree=1646992/2055920 swapFree=4192812/4192956
[pid=9062] ppid=9060 vsize=1732 CPUtime=0.09
/proc/9062/stat : 9062 (VALCSP) R 9060 9062 8822 0 -1 4194304 185 0 0 0 9 0 0 0 18 0 1 0 246411677 1773568 163 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 9045525 0 0 4096 0 0 0 0 17 1 0 0
/proc/9062/statm: 433 163 64 8 0 105 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1732

[startup+0.509742 s]
/proc/loadavg: 0.02 0.44 0.64 2/68 9063
/proc/meminfo: memFree=1646992/2055920 swapFree=4192812/4192956
[pid=9062] ppid=9060 vsize=2656 CPUtime=0.5
/proc/9062/stat : 9062 (VALCSP) R 9060 9062 8822 0 -1 4194304 416 0 0 0 50 0 0 0 21 0 1 0 246411677 2719744 394 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 9045525 0 0 4096 0 0 0 0 17 1 0 0
/proc/9062/statm: 664 394 64 8 0 336 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 2656

[startup+1.3299 s]
/proc/loadavg: 0.02 0.44 0.64 2/68 9063
/proc/meminfo: memFree=1644240/2055920 swapFree=4192812/4192956
[pid=9062] ppid=9060 vsize=4636 CPUtime=1.32
/proc/9062/stat : 9062 (VALCSP) R 9060 9062 8822 0 -1 4194304 893 0 0 0 132 0 0 0 25 0 1 0 246411677 4747264 871 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 9045525 0 0 4096 0 0 0 0 17 1 0 0
/proc/9062/statm: 1159 871 64 8 0 831 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 4636

Child status: 0
Real time (s): 2.37189
CPU time (s): 2.36164
CPU user time (s): 2.35164
CPU system time (s): 0.009998
CPU usage (%): 99.5679
Max. virtual memory (cumulated for all children) (KiB): 8332

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

runsolver used 0.003999 s user time and 0.011998 s system time

The end

Launcher Data (download as text)

Begin job on node38 on Tue Jan 16 20:41:49 UTC 2007


IDJOB= 268994
IDBENCH= 5798
IDSOLVER= 90
FILE ID= node38/268994-1168980103

PBS_JOBID= 3566286

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.8/rand-2-40-80-103-800-3_ext.xml
COMMAND LINE= /tmp/evaluation/268994-1168980103/VALCSP /tmp/evaluation/268994-1168980103/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node38/watcher-268994-1168980103 -o ROOT/results/node38/solver-268994-1168980103 -C 1800 -M 900  /tmp/evaluation/268994-1168980103/VALCSP /tmp/evaluation/268994-1168980103/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  2655fa3a8729f18aaa03c51fe9718813

RANDOM SEED= 248136881

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:       1647472 kB
Buffers:         46080 kB
Cached:         270120 kB
SwapCached:          0 kB
Active:         153492 kB
Inactive:       182860 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1647472 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             888 kB
Writeback:           0 kB
Mapped:          30388 kB
Slab:            57804 kB
Committed_AS:  4932812 kB
PageTables:       1692 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 node38 on Tue Jan 16 20:42:11 UTC 2007