Trace number 1043303

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
casper zaoUNSAT 0.010998 0.017768

DiagnosticValue
CHECKS213

General information on the benchmark

Namecsp/rcpspTighter/
normalized-rcpsptight20-09.xml
MD5SUMb5fe2ed04659f752fdf401e5d9f2c322
Bench CategoryGLOBAL (global constraints)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.008997
Satisfiable
(Un)Satisfiability was proved
Number of variables20
Number of constraints18
Maximum constraint arity20
Maximum domain size13
Number of constraints which are defined in extension0
Number of constraints which are defined in intension15
Global constraints used (with number of constraints)cumulative(3)

Solver Data (download as text)

0.00/0.01	c [ This is CaSPERzao (C) mvc@di.fct.unl.pt ]
0.00/0.01	c Parsing = 1
0.00/0.01	c Building = 1
0.00/0.01	c [ NumberOfVariables = 20 ]
0.00/0.01	c [ NumberOfConstraints = 18 ]
0.00/0.01	c [ SizeOfSearchSpace(log2) = 69.9869 ]
0.00/0.01	c SymmetrySearch = 1
0.00/0.01	c [ Found 1024 symmetries ]
0.00/0.01	c InitialPropagation = 0
0.00/0.01	s UNSATISFIABLE
0.00/0.01	d CHECKS 213
0.00/0.01	c [ TotalFails = 0 ]
0.00/0.01	c [ NumberOfRestarts = 0 ]
0.00/0.01	c [ TotalTime = 0.00289632 secs ]

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-1043303-1215027209/watcher-1043303-1215027209 -o /tmp/evaluation-result-1043303-1215027209/solver-1043303-1215027209 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/casperzao HOME/instance-1043303-1215027209.xml 1887877520 

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.02 2.05 2.01 4/72 23272
/proc/meminfo: memFree=1817696/2055920 swapFree=4180444/4192956
[pid=23272] ppid=23270 vsize=1056 CPUtime=0
/proc/23272/stat : 23272 (casperzao) R 23270 23272 21760 0 -1 4194304 40 0 0 0 0 0 0 0 19 0 1 0 1981690478 1081344 26 996147200 134512640 135477443 4294956224 18446744073709551615 6853412 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/23272/statm: 264 26 20 235 0 3 0

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

Child status: 0
Real time (s): 0.017768
CPU time (s): 0.010998
CPU user time (s): 0.005999
CPU system time (s): 0.004999
CPU usage (%): 61.8978
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node68 at 2008-07-02 21:33:29
IDJOB=1043303
IDBENCH=53829
IDSOLVER=361
FILE ID=node68/1043303-1215027209
PBS_JOBID= 7874334
Free space on /tmp= 66544 MiB

SOLVER NAME= casper zao
BENCH NAME= CPAI08/csp/rcpspTighter/normalized-rcpsptight20-09.xml
COMMAND LINE= HOME/casperzao BENCHNAME RANDOMSEED 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1043303-1215027209/watcher-1043303-1215027209 -o /tmp/evaluation-result-1043303-1215027209/solver-1043303-1215027209 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/casperzao HOME/instance-1043303-1215027209.xml 1887877520 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= b5fe2ed04659f752fdf401e5d9f2c322
RANDOM SEED=1887877520

node68.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.261
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.261
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:       1818176 kB
Buffers:         22608 kB
Cached:         132916 kB
SwapCached:       6520 kB
Active:         130228 kB
Inactive:        41524 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1818176 kB
SwapTotal:     4192956 kB
SwapFree:      4180444 kB
Dirty:            2912 kB
Writeback:           0 kB
Mapped:          24136 kB
Slab:            51564 kB
Committed_AS:  4179364 kB
PageTables:       1696 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= 66540 MiB
End job on node68 at 2008-07-02 21:33:29