Trace number 226028

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 14.9627 15.1071

DiagnosticValue
CHECKS247747000
NODES690

General information on the benchmark

Nametightness/tightness0.9/
rand-2-40-180-84-900-75_ext.xml
MD5SUMb7c1c41dbc3e9546e44459527f1aa21c
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.9494
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)

15.10	s UNSATISFIABLE
15.10	d CHECKS 2.47747e+08
15.10	d NODES 690
15.10

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/node24/watcher-226028-1168274277 -o ROOT/results/node24/solver-226028-1168274277 -C 1800 -M 900 /tmp/evaluation/226028-1168274277/VALCSP /tmp/evaluation/226028-1168274277/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.57 1.17 1.25 5/94 23989
/proc/meminfo: memFree=497832/2055920 swapFree=4192812/4192956
[pid=23988] ppid=23986 vsize=1600 CPUtime=0
/proc/23988/stat : 23988 (VALCSP) R 23986 23988 23499 0 -1 4194304 143 0 0 0 0 0 0 0 20 0 1 0 175822979 1638400 121 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 3043985 0 0 4096 0 0 0 0 17 1 0 0
/proc/23988/statm: 400 121 62 8 0 72 0

[startup+0.105204 s]
/proc/loadavg: 1.57 1.17 1.25 5/94 23989
/proc/meminfo: memFree=497832/2055920 swapFree=4192812/4192956
[pid=23988] ppid=23986 vsize=1600 CPUtime=0.09
/proc/23988/stat : 23988 (VALCSP) R 23986 23988 23499 0 -1 4194304 152 0 0 0 9 0 0 0 20 0 1 0 175822979 1638400 130 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 3064908 0 0 4096 0 0 0 0 17 1 0 0
/proc/23988/statm: 400 130 62 8 0 72 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1600

[startup+0.513248 s]
/proc/loadavg: 1.57 1.17 1.25 5/94 23989
/proc/meminfo: memFree=497832/2055920 swapFree=4192812/4192956
[pid=23988] ppid=23986 vsize=1996 CPUtime=0.5
/proc/23988/stat : 23988 (VALCSP) R 23986 23988 23499 0 -1 4194304 255 0 0 0 50 0 0 0 24 0 1 0 175822979 2043904 233 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 3067073 0 0 4096 0 0 0 0 17 1 0 0
/proc/23988/statm: 499 233 62 8 0 171 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 1996

[startup+1.33434 s]
/proc/loadavg: 1.57 1.17 1.25 3/94 23989
/proc/meminfo: memFree=496552/2055920 swapFree=4192812/4192956
[pid=23988] ppid=23986 vsize=2656 CPUtime=1.31
/proc/23988/stat : 23988 (VALCSP) R 23986 23988 23499 0 -1 4194304 417 0 0 0 131 0 0 0 25 0 1 0 175822979 2719744 395 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 3067045 0 0 4096 0 0 0 0 17 1 0 0
/proc/23988/statm: 664 395 62 8 0 336 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 2656

[startup+2.97151 s]
/proc/loadavg: 1.61 1.19 1.25 3/94 23989
/proc/meminfo: memFree=495592/2055920 swapFree=4192812/4192956
[pid=23988] ppid=23986 vsize=4120 CPUtime=2.93
/proc/23988/stat : 23988 (VALCSP) R 23986 23988 23499 0 -1 4194304 787 0 0 0 293 0 0 0 25 0 1 0 175822979 4218880 765 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 3067123 0 0 4096 0 0 0 0 17 1 0 0
/proc/23988/statm: 1030 765 62 8 0 702 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 4120

[startup+6.25587 s]
/proc/loadavg: 1.61 1.19 1.25 3/94 23989
/proc/meminfo: memFree=492648/2055920 swapFree=4192812/4192956
[pid=23988] ppid=23986 vsize=6900 CPUtime=6.19
/proc/23988/stat : 23988 (VALCSP) R 23986 23988 23499 0 -1 4194304 1484 0 0 0 619 0 0 0 25 0 1 0 175822979 7065600 1462 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 3064929 0 0 4096 0 0 0 0 17 1 0 0
/proc/23988/statm: 1725 1462 62 8 0 1397 0
Current children cumulated CPU time (s) 6.19
Current children cumulated vsize (KiB) 6900

[startup+12.7236 s]
/proc/loadavg: 1.67 1.21 1.26 3/94 23989
/proc/meminfo: memFree=477608/2055920 swapFree=4192812/4192956
[pid=23988] ppid=23986 vsize=21432 CPUtime=12.6
/proc/23988/stat : 23988 (VALCSP) R 23986 23988 23499 0 -1 4194304 5104 0 0 0 1258 2 0 0 25 0 1 0 175822979 21946368 5082 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134524787 0 0 4096 0 0 0 0 17 1 0 0
/proc/23988/statm: 5358 5082 65 8 0 5030 0
Current children cumulated CPU time (s) 12.6
Current children cumulated vsize (KiB) 21432

Child status: 0
Real time (s): 15.1071
CPU time (s): 14.9627
CPU user time (s): 14.9347
CPU system time (s): 0.027995
CPU usage (%): 99.0444
Max. virtual memory (cumulated for all children) (KiB): 21432

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

runsolver used 0.021996 s user time and 0.047992 s system time

The end

Launcher Data (download as text)

Begin job on node24 on Mon Jan  8 16:37:57 UTC 2007


IDJOB= 226028
IDBENCH= 5924
FILE ID= node24/226028-1168274277

PBS_JOBID= 3483271

Free space on /tmp= 66475 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.9/rand-2-40-180-84-900-75_ext.xml
COMMAND LINE= /tmp/evaluation/226028-1168274277/VALCSP /tmp/evaluation/226028-1168274277/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node24/watcher-226028-1168274277 -o ROOT/results/node24/solver-226028-1168274277 -C 1800 -M 900  /tmp/evaluation/226028-1168274277/VALCSP /tmp/evaluation/226028-1168274277/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  b7c1c41dbc3e9546e44459527f1aa21c

RANDOM SEED= 705163062

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.234
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.234
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:        498248 kB
Buffers:         15680 kB
Cached:        1405112 kB
SwapCached:          0 kB
Active:         867924 kB
Inactive:       637616 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        498248 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            4024 kB
Writeback:           0 kB
Mapped:         111352 kB
Slab:            36660 kB
Committed_AS:  3818452 kB
PageTables:       2488 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= 66475 MiB



End job on node24 on Mon Jan  8 16:38:12 UTC 2007