Trace number 1046395

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
cpHydra k_40UNSAT 0.034994 0.0416271

DiagnosticValue
ASSIGNMENTS12
CHECKS10492

General information on the benchmark

Namecsp/allsquaresUnsat/
normalized-squaresUnsat-9-9.xml
MD5SUMd26f3aa56691dd2bd9c9203c0b4a510e
Bench CategoryGLOBAL (global constraints)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.024995
Satisfiable
(Un)Satisfiability was proved
Number of variables162
Number of constraints183
Maximum constraint arity9
Maximum domain size17
Number of constraints which are defined in extension0
Number of constraints which are defined in intension145
Global constraints used (with number of constraints)cumulative(2),weightedsum(36)

Solver Data (download as text)

0.00/0.00	c cpHydra_k_40 version 0.0
0.00/0.04	c mistral-prime version 1.313
0.00/0.04	s UNSATISFIABLE
0.00/0.04	d CHECKS 10492
0.00/0.04	d ASSIGNMENTS 12

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-1046395-1215026560/watcher-1046395-1215026560 -o /tmp/evaluation-result-1046395-1215026560/solver-1046395-1215026560 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/cpHydra_k_40/hydra HOME/instance-1046395-1215026560.xml 

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: 1.94 1.98 1.93 4/84 9951
/proc/meminfo: memFree=1354968/2055920 swapFree=4179760/4192956
[pid=9951] ppid=9949 vsize=5360 CPUtime=0
/proc/9951/stat : 9951 (hydra) S 9949 9951 8868 0 -1 4194304 306 124 0 0 0 0 0 0 20 0 1 0 1981629286 5488640 236 996147200 4194304 4889804 548682068816 18446744073709551615 213116314436 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/9951/statm: 1340 236 195 169 0 51 0
[pid=9953] ppid=9951 vsize=0 CPUtime=0
/proc/9953/stat : 9953 (hydra) R 9951 9951 8868 0 -1 4194368 21 0 0 0 0 0 0 0 23 0 1 0 1981629287 0 0 996147200 0 0 0 18446744073709551615 213116316967 0 0 4096 0 0 0 0 17 1 0 0
/proc/9953/statm: 0 0 0 0 0 0 0

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

Child status: 0
Real time (s): 0.0416271
CPU time (s): 0.034994
CPU user time (s): 0.021996
CPU system time (s): 0.012998
CPU usage (%): 84.0654
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.021996
system time used= 0.012998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1860
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= 27
involuntary context switches= 12

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node37 at 2008-07-02 21:22:40
IDJOB=1046395
IDBENCH=53776
IDSOLVER=366
FILE ID=node37/1046395-1215026560
PBS_JOBID= 7874396
Free space on /tmp= 66524 MiB

SOLVER NAME= cpHydra k_40
BENCH NAME= CPAI08/csp/allsquaresUnsat/normalized-squaresUnsat-9-9.xml
COMMAND LINE= HOME/cpHydra_k_40/hydra BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1046395-1215026560/watcher-1046395-1215026560 -o /tmp/evaluation-result-1046395-1215026560/solver-1046395-1215026560 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/cpHydra_k_40/hydra HOME/instance-1046395-1215026560.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= d26f3aa56691dd2bd9c9203c0b4a510e
RANDOM SEED=46381669

node37.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.236
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.236
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:       1355448 kB
Buffers:         71488 kB
Cached:         500140 kB
SwapCached:       7460 kB
Active:         251188 kB
Inactive:       373672 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1355448 kB
SwapTotal:     4192956 kB
SwapFree:      4179760 kB
Dirty:           24832 kB
Writeback:           0 kB
Mapped:          69940 kB
Slab:            60760 kB
Committed_AS:  3434832 kB
PageTables:       2004 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264884 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66500 MiB
End job on node37 at 2008-07-02 21:22:40