Trace number 1110517

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 NameAnswerNumber of falsified constraintsCPU timeWall clock time
toulbar2/BTD 2008-06-27? (exit code) 0.039993 0.046524

General information on the benchmark

Namecsp/wordsVg/
normalized-crossword-m1c-words-vg12-16_ext.xml
MD5SUMd5a5b46f918ed24babfe0cb73c479416
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkMSAT TO
Best Number of falsified constraints14
Best CPU time to get the best result obtained on this benchmark3600.01
Satisfiable
(Un)Satisfiability was proved
Number of variables192
Number of constraints28
Maximum constraint arity16
Maximum domain size26
Number of constraints which are defined in extension28
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.02	*** glibc detected *** free(): invalid next size (fast): 0x083a2498 ***
0.00/0.02	HOME/solverBTD.sh: line 5: 15090 Aborted                 (core dumped) ./toulbar2 $1 z
0.00/0.03	Nom de fichier incorrect
0.00/0.04	*** glibc detected *** free(): invalid next size (fast): 0x083a24a8 ***
0.00/0.04	HOME/solverBTD.sh: line 7: 15092 Aborted                 (core dumped) ./toulbar2 $1 B2 Oorder r4

Verifier Data (download as text)

ERROR: no interpretation found !

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-1110517-1215827285/watcher-1110517-1215827285 -o /tmp/evaluation-result-1110517-1215827285/solver-1110517-1215827285 -C 3600 -W 4000 -M 900 --output-limit 1,15 HOME/solverBTD.sh HOME/instance-1110517-1215827285.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 3630 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 4000 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.03 2.09 2.08 4/81 15085
/proc/meminfo: memFree=1915336/2055920 swapFree=4180652/4192956
[pid=15085] ppid=15083 vsize=5356 CPUtime=0
/proc/15085/stat : 15085 (solverBTD.sh) R 15083 15085 14414 0 -1 4194304 262 0 0 0 0 0 0 0 20 0 1 0 39432029 5484544 230 996147200 4194304 4889804 548682068832 18446744073709551615 259353275039 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/15085/statm: 1339 230 191 169 0 50 0
[pid=15086] ppid=15085 vsize=5356 CPUtime=0
/proc/15086/stat : 15086 (solverBTD.sh) R 15085 15085 14414 0 -1 4194368 0 0 0 0 0 0 0 0 20 0 1 0 39432029 5484544 230 996147200 4194304 4889804 548682068832 18446744073709551615 259353275039 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/15086/statm: 1339 230 191 169 0 50 0

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

Child status: 134
Real time (s): 0.046524
CPU time (s): 0.039993
CPU user time (s): 0.022996
CPU system time (s): 0.016997
CPU usage (%): 85.9621
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node1 at 2008-07-12 03:48:05
IDJOB=1110517
IDBENCH=61115
IDSOLVER=370
FILE ID=node1/1110517-1215827285
PBS_JOBID= 7903322
Free space on /tmp= 66524 MiB

SOLVER NAME= toulbar2/BTD 2008-06-27
BENCH NAME= CPAI08/csp/wordsVg/normalized-crossword-m1c-words-vg12-16_ext.xml
COMMAND LINE= HOME/solverBTD.sh BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1110517-1215827285/watcher-1110517-1215827285 -o /tmp/evaluation-result-1110517-1215827285/solver-1110517-1215827285 -C 3600 -W 4000 -M 900 --output-limit 1,15  HOME/solverBTD.sh HOME/instance-1110517-1215827285.xml 

TIME LIMIT= 3600 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= d5a5b46f918ed24babfe0cb73c479416
RANDOM SEED=1850001270

node1.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.244
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.244
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:       1915816 kB
Buffers:         11064 kB
Cached:          60716 kB
SwapCached:       6352 kB
Active:          67284 kB
Inactive:        30620 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1915816 kB
SwapTotal:     4192956 kB
SwapFree:      4180652 kB
Dirty:            9060 kB
Writeback:           0 kB
Mapped:          41912 kB
Slab:            27436 kB
Committed_AS:   173268 kB
PageTables:       1928 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= 66512 MiB
End job on node1 at 2008-07-12 03:48:05