Trace number 224869

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 2.40663 2.43442

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.43	s UNSATISFIABLE
2.43	d CHECKS 4.12185e+07
2.43	d NODES 335
2.43

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/node12/watcher-224869-1168270107 -o ROOT/results/node12/solver-224869-1168270107 -C 1800 -M 900 /tmp/evaluation/224869-1168270107/VALCSP /tmp/evaluation/224869-1168270107/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.84 1.89 1.94 5/86 31427
/proc/meminfo: memFree=1777112/2055920 swapFree=4160348/4192956
[pid=31426] ppid=31424 vsize=1468 CPUtime=0
/proc/31426/stat : 31426 (VALCSP) R 31424 31426 30469 0 -1 4194304 124 0 0 0 0 0 0 0 21 0 1 0 175405748 1503232 102 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 10155088 0 0 4096 0 0 0 0 17 1 0 0
/proc/31426/statm: 367 102 62 8 0 39 0

[startup+0.106474 s]
/proc/loadavg: 1.84 1.89 1.94 5/86 31427
/proc/meminfo: memFree=1777112/2055920 swapFree=4160348/4192956
[pid=31426] ppid=31424 vsize=1732 CPUtime=0.09
/proc/31426/stat : 31426 (VALCSP) R 31424 31426 30469 0 -1 4194304 182 0 0 0 9 0 0 0 21 0 1 0 175405748 1773568 160 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 10157232 0 0 4096 0 0 0 0 17 1 0 0
/proc/31426/statm: 433 160 62 8 0 105 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1732

[startup+0.514547 s]
/proc/loadavg: 1.84 1.89 1.94 5/86 31427
/proc/meminfo: memFree=1777112/2055920 swapFree=4160348/4192956
[pid=31426] ppid=31424 vsize=2656 CPUtime=0.5
/proc/31426/stat : 31426 (VALCSP) R 31424 31426 30469 0 -1 4194304 413 0 0 0 50 0 0 0 25 0 1 0 175405748 2719744 391 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 10155118 0 0 4096 0 0 0 0 17 1 0 0
/proc/31426/statm: 664 391 62 8 0 336 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 2656

[startup+1.33569 s]
/proc/loadavg: 1.84 1.89 1.94 3/86 31427
/proc/meminfo: memFree=1778904/2055920 swapFree=4160348/4192956
[pid=31426] ppid=31424 vsize=4504 CPUtime=1.31
/proc/31426/stat : 31426 (VALCSP) R 31424 31426 30469 0 -1 4194304 881 0 0 0 131 0 0 0 25 0 1 0 175405748 4612096 859 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 10157290 0 0 4096 0 0 0 0 17 1 0 0
/proc/31426/statm: 1126 859 62 8 0 798 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 4504

Child status: 0
Real time (s): 2.43442
CPU time (s): 2.40663
CPU user time (s): 2.39164
CPU system time (s): 0.014997
CPU usage (%): 98.8586
Max. virtual memory (cumulated for all children) (KiB): 8332

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

runsolver used 0.005999 s user time and 0.013997 s system time

The end

Launcher Data (download as text)

Begin job on node12 on Mon Jan  8 15:28:27 UTC 2007


IDJOB= 224869
IDBENCH= 5798
FILE ID= node12/224869-1168270107

PBS_JOBID= 3482982

Free space on /tmp= 66327 MiB

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

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  2655fa3a8729f18aaa03c51fe9718813

RANDOM SEED= 574480803

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.265
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.265
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:       1777656 kB
Buffers:         52132 kB
Cached:         132660 kB
SwapCached:       5132 kB
Active:         141500 kB
Inactive:        86160 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1777656 kB
SwapTotal:     4192956 kB
SwapFree:      4160348 kB
Dirty:             932 kB
Writeback:           0 kB
Mapped:          52784 kB
Slab:            35520 kB
Committed_AS:  5062540 kB
PageTables:       2124 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= 66327 MiB



End job on node12 on Mon Jan  8 15:28:30 UTC 2007