Trace number 1079289

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
bpsolver 2008-06-27UNSAT 0.712891 0.726491

General information on the benchmark

Namecsp/lexVg/
normalized-crossword-m1c-lex-vg16-20_ext.xml
MD5SUMa584e692d54bf2a444392bd190de08b3
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.013997
Satisfiable
(Un)Satisfiability was proved
Number of variables320
Number of constraints36
Maximum constraint arity20
Maximum domain size26
Number of constraints which are defined in extension36
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.02	c bpsolver version 6.27.2008
0.00/0.02	c converting(HOME/instance-1079289-1215209547)
0.00/0.06	c Converted in 16 ms
0.00/0.06	c solving(HOME/instance-1079289-1215209547,1800000)
0.68/0.71	s UNSATISFIABLE
0.68/0.71	
0.68/0.71	
0.68/0.71	c Time=457 ms
0.68/0.71

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

runsolver version 3.2.5 (c) roussel@cril.univ-artois.fr

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1079289-1215209547/watcher-1079289-1215209547 -o /tmp/evaluation-result-1079289-1215209547/solver-1079289-1215209547 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1079289-1215209547 1800 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2200 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.06 2.02 2.00 4/74 11780
/proc/meminfo: memFree=1733840/2055920 swapFree=4192812/4192956
[pid=11780] ppid=11778 vsize=3376 CPUtime=0
/proc/11780/stat : 11780 (bprolog) R 11778 11780 9856 0 -1 4194304 293 0 0 0 0 0 0 0 20 0 1 0 148340030 3457024 24 996147200 134512640 134990860 4294956096 18446744073709551615 12591908 0 0 4096 0 0 0 0 17 1 0 0
/proc/11780/statm: 844 24 18 116 0 701 0

[startup+0.210085 s]
/proc/loadavg: 2.06 2.02 2.00 4/74 11780
/proc/meminfo: memFree=1733840/2055920 swapFree=4192812/4192956
[pid=11780] ppid=11778 vsize=64036 CPUtime=0.19
/proc/11780/stat : 11780 (bprolog) R 11778 11780 9856 0 -1 4194304 7300 0 0 0 14 5 0 0 21 0 1 0 148340030 65572864 7010 996147200 134512640 134990860 4294956096 18446744073709551615 134746353 0 0 4096 2 0 0 0 17 1 0 0
/proc/11780/statm: 16009 7010 186 116 0 15520 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 64036

[startup+0.301098 s]
/proc/loadavg: 2.06 2.02 2.00 4/74 11780
/proc/meminfo: memFree=1733840/2055920 swapFree=4192812/4192956
[pid=11780] ppid=11778 vsize=95628 CPUtime=0.28
/proc/11780/stat : 11780 (bprolog) R 11778 11780 9856 0 -1 4194304 14069 0 0 0 20 8 0 0 21 0 1 0 148340030 97923072 13503 996147200 134512640 134990860 4294956096 18446744073709551615 134956882 0 0 4096 2 0 0 0 17 1 0 0
/proc/11780/statm: 23907 13503 186 116 0 23418 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 95628

[startup+0.401107 s]
/proc/loadavg: 2.06 2.02 2.00 4/74 11780
/proc/meminfo: memFree=1733840/2055920 swapFree=4192812/4192956
[pid=11780] ppid=11778 vsize=165944 CPUtime=0.37
/proc/11780/stat : 11780 (bprolog) R 11778 11780 9856 0 -1 4194304 20193 0 0 0 27 10 0 0 22 0 1 0 148340030 169926656 19627 996147200 134512640 134990860 4294956096 18446744073709551615 134965458 0 0 4096 2 0 0 0 17 1 0 0
/proc/11780/statm: 41486 19627 186 116 0 40997 0
Current children cumulated CPU time (s) 0.37
Current children cumulated vsize (KiB) 165944

[startup+0.701142 s]
/proc/loadavg: 2.06 2.02 2.00 4/74 11780
/proc/meminfo: memFree=1733840/2055920 swapFree=4192812/4192956
[pid=11780] ppid=11778 vsize=162500 CPUtime=0.68
/proc/11780/stat : 11780 (bprolog) R 11778 11780 9856 0 -1 4194304 38017 0 0 0 48 20 0 0 25 0 1 0 148340030 166400000 20568 996147200 134512640 134990860 4294956096 18446744073709551615 134716955 0 0 4096 2 0 0 0 17 1 0 0
/proc/11780/statm: 40625 20568 186 116 0 40136 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 162500

Solver just ended. Dumping a history of the last processes samples

Child status: 0
Real time (s): 0.726491
CPU time (s): 0.712891
CPU user time (s): 0.489925
CPU system time (s): 0.222966
CPU usage (%): 98.128
Max. virtual memory (cumulated for all children) (KiB): 165944

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

runsolver used 0.001999 second user time and 0.010998 second system time

The end

Launcher Data (download as text)

Begin job on node28 at 2008-07-05 00:12:27
IDJOB=1079289
IDBENCH=56872
IDSOLVER=347
FILE ID=node28/1079289-1215209547
PBS_JOBID= 7881675
Free space on /tmp= 66480 MiB

SOLVER NAME= bpsolver 2008-06-27
BENCH NAME= CPAI08/csp/lexVg/normalized-crossword-m1c-lex-vg16-20_ext.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1079289-1215209547/watcher-1079289-1215209547 -o /tmp/evaluation-result-1079289-1215209547/solver-1079289-1215209547 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1079289-1215209547 1800

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= a584e692d54bf2a444392bd190de08b3
RANDOM SEED=746540206

node28.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.231
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.231
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:       1734320 kB
Buffers:         22496 kB
Cached:         152740 kB
SwapCached:          0 kB
Active:         209928 kB
Inactive:        60144 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1734320 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1820 kB
Writeback:           0 kB
Mapped:         105908 kB
Slab:            36368 kB
Committed_AS:   411896 kB
PageTables:       2000 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66480 MiB
End job on node28 at 2008-07-05 00:12:28