Trace number 2079983

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 1.545UNSAT 0.037993 0.0379641

DiagnosticValue
ASSIGNMENTS0
CHECKS3839
NODES0

General information on the benchmark

Namecsp/radar-8-24-3-2/
normalized-radar-8-24-3-2-47.xml
MD5SUM9f2b1f2a813a54b58c5f088befccb806
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.037993
Satisfiable
(Un)Satisfiability was proved
Number of variables144
Number of constraints64
Maximum constraint arity17
Maximum domain size4
Number of constraints which are defined in extension0
Number of constraints which are defined in intension64
Global constraints used (with number of constraints)

Solver Data 

0.00/0.00	c mistral version 1.545
0.01/0.03	s UNSATISFIABLE
0.01/0.03	d CHECKS 3839
0.01/0.03	d ASSIGNMENTS 0
0.01/0.03	d NODES 0 BACKTRACKS 0 FAILURES 1 RUNTIME -4.1674e-19 TOTALTIME 0.02 NODES/s -0 CHECKS/s -9.21197e+21

Verifier Data 

No possible verification on an UNSAT instance

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2079983-1247369144/watcher-2079983-1247369144 -o /tmp/evaluation-result-2079983-1247369144/solver-2079983-1247369144 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2079983-1247369144.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): 2000 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


[startup+0 s]
/proc/loadavg: 1.94 1.99 1.99 4/83 22991
/proc/meminfo: memFree=1352720/2055920 swapFree=4192812/4192956
[pid=22991] ppid=22989 vsize=4804 CPUtime=0
/proc/22991/stat : 22991 (ld-linux.so.2) R 22989 22991 19160 0 -1 4194304 243 0 0 0 0 0 0 0 18 0 1 0 23978352 4919296 223 996147200 1448431616 1448550632 4294956208 18446744073709551615 4159096976 0 0 4096 0 0 0 0 17 0 0 0
/proc/22991/statm: 1201 229 197 29 0 16 0

[startup+0.020296 s]
/proc/loadavg: 1.94 1.99 1.99 4/83 22991
/proc/meminfo: memFree=1352720/2055920 swapFree=4192812/4192956
[pid=22991] ppid=22989 vsize=5080 CPUtime=0.01
/proc/22991/stat : 22991 (ld-linux.so.2) R 22989 22991 19160 0 -1 4194304 478 0 0 0 1 0 0 0 18 0 1 0 23978352 5201920 457 996147200 1448431616 1448550632 4294956208 18446744073709551615 134568162 0 0 4096 0 0 0 0 17 0 0 0
/proc/22991/statm: 1270 458 362 29 0 85 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 5080

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

[startup+0.020296 s]
/proc/loadavg: 1.94 1.99 1.99 4/83 22991
/proc/meminfo: memFree=1352720/2055920 swapFree=4192812/4192956
[pid=22991] ppid=22989 vsize=5080 CPUtime=0.01
/proc/22991/stat : 22991 (ld-linux.so.2) R 22989 22991 19160 0 -1 4194304 478 0 0 0 1 0 0 0 18 0 1 0 23978352 5201920 457 996147200 1448431616 1448550632 4294956208 18446744073709551615 134568162 0 0 4096 0 0 0 0 17 0 0 0
/proc/22991/statm: 1270 458 362 29 0 85 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 5080

Child status: 0
Real time (s): 0.0379641
CPU time (s): 0.037993
CPU user time (s): 0.029995
CPU system time (s): 0.007998
CPU usage (%): 100.076
Max. virtual memory (cumulated for all children) (KiB): 5080

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node42 at 2009-07-12 05:25:44
IDJOB=2079983
IDBENCH=56977
IDSOLVER=769
FILE ID=node42/2079983-1247369144
PBS_JOBID= 9507073
Free space on /tmp= 66308 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/radar-8-24-3-2/normalized-radar-8-24-3-2-47.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2079983-1247369144/watcher-2079983-1247369144 -o /tmp/evaluation-result-2079983-1247369144/solver-2079983-1247369144 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2079983-1247369144.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 9f2b1f2a813a54b58c5f088befccb806
RANDOM SEED=659318935

node42.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.283
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.283
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:       1353136 kB
Buffers:         37940 kB
Cached:         157152 kB
SwapCached:          0 kB
Active:         576812 kB
Inactive:        72544 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1353136 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1596 kB
Writeback:           0 kB
Mapped:         469872 kB
Slab:            37868 kB
Committed_AS:   882820 kB
PageTables:       2624 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= 66308 MiB
End job on node42 at 2009-07-12 05:25:44