Trace number 1040955

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
Mistral-prime 1.313UNSAT 0.050992 0.0527341

DiagnosticValue
ASSIGNMENTS26
CHECKS22403

General information on the benchmark

Namecsp/allsquaresUnsat/
normalized-squaresUnsat-14-14.xml
MD5SUMd2f26082a61c7c2d09b652b9c7d6c012
Bench CategoryGLOBAL (global constraints)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.050992
Satisfiable
(Un)Satisfiability was proved
Number of variables392
Number of constraints458
Maximum constraint arity14
Maximum domain size32
Number of constraints which are defined in extension0
Number of constraints which are defined in intension365
Global constraints used (with number of constraints)cumulative(2),weightedsum(91)

Solver Data (download as text)

0.00/0.00	c mistral-prime version 1.313
0.02/0.05	s UNSATISFIABLE
0.02/0.05	d CHECKS 22403
0.02/0.05	d ASSIGNMENTS 26

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-1040955-1214999012/watcher-1040955-1214999012 -o /tmp/evaluation-result-1040955-1214999012/solver-1040955-1214999012 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1040955-1214999012.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.99 1.97 1.69 3/73 19502
/proc/meminfo: memFree=1381392/2055920 swapFree=4179560/4192956
[pid=19502] ppid=19500 vsize=4580 CPUtime=0
/proc/19502/stat : 19502 (xsolve) R 19500 19502 19188 0 -1 4194304 327 0 0 0 0 0 0 0 18 0 1 0 1978876291 4689920 295 996147200 134512640 135237403 4294956256 18446744073709551615 3767419 0 0 4096 0 0 0 0 17 1 0 0
/proc/19502/statm: 1145 302 257 176 0 49 0

[startup+0.025624 s]
/proc/loadavg: 1.99 1.97 1.69 3/73 19502
/proc/meminfo: memFree=1381392/2055920 swapFree=4179560/4192956
[pid=19502] ppid=19500 vsize=5112 CPUtime=0.02
/proc/19502/stat : 19502 (xsolve) R 19500 19502 19188 0 -1 4194304 597 0 0 0 2 0 0 0 18 0 1 0 1978876291 5234688 563 996147200 134512640 135237403 4294956256 18446744073709551615 4159729091 0 0 4096 0 0 0 0 17 1 0 0
/proc/19502/statm: 1278 563 377 176 0 182 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 5112

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

[startup+0.025624 s]
/proc/loadavg: 1.99 1.97 1.69 3/73 19502
/proc/meminfo: memFree=1381392/2055920 swapFree=4179560/4192956
[pid=19502] ppid=19500 vsize=5112 CPUtime=0.02
/proc/19502/stat : 19502 (xsolve) R 19500 19502 19188 0 -1 4194304 597 0 0 0 2 0 0 0 18 0 1 0 1978876291 5234688 563 996147200 134512640 135237403 4294956256 18446744073709551615 4159729091 0 0 4096 0 0 0 0 17 1 0 0
/proc/19502/statm: 1278 563 377 176 0 182 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 5112

Child status: 0
Real time (s): 0.0527341
CPU time (s): 0.050992
CPU user time (s): 0.044993
CPU system time (s): 0.005999
CPU usage (%): 96.6965
Max. virtual memory (cumulated for all children) (KiB): 5112

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

runsolver used 0.004999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node8 at 2008-07-02 13:43:32
IDJOB=1040955
IDBENCH=53757
IDSOLVER=358
FILE ID=node8/1040955-1214999012
PBS_JOBID= 7870907
Free space on /tmp= 66552 MiB

SOLVER NAME= Mistral-prime 1.313
BENCH NAME= CPAI08/csp/allsquaresUnsat/normalized-squaresUnsat-14-14.xml
COMMAND LINE= HOME/xsolve BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1040955-1214999012/watcher-1040955-1214999012 -o /tmp/evaluation-result-1040955-1214999012/solver-1040955-1214999012 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1040955-1214999012.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= d2f26082a61c7c2d09b652b9c7d6c012
RANDOM SEED=188636067

node8.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.222
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.222
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1381808 kB
Buffers:         61760 kB
Cached:         511660 kB
SwapCached:       6756 kB
Active:         140288 kB
Inactive:       453808 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1381808 kB
SwapTotal:     4192956 kB
SwapFree:      4179560 kB
Dirty:            1028 kB
Writeback:           0 kB
Mapped:          28240 kB
Slab:            65224 kB
Committed_AS:  3197196 kB
PageTables:       1704 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= 66552 MiB
End job on node8 at 2008-07-02 13:43:33