Trace number 1044632

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
Abscon 112v4 ACUNSAT 0.632903 0.677456

DiagnosticValue
CHECKS0
NODES0

General information on the benchmark

Namecsp/pigeons_glb/
normalized-pigeons-40_ext.xml
MD5SUM4d2f128f0883e3ccf59e5ad375805964
Bench CategoryGLOBAL (global constraints)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.005998
Satisfiable
(Un)Satisfiability was proved
Number of variables40
Number of constraints1
Maximum constraint arity40
Maximum domain size39
Number of constraints which are defined in extension0
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)alldifferent(1)

Solver Data (download as text)

0.00/0.08	
0.00/0.08	Abscon 112 (May, 2008)
0.18/0.24	
0.18/0.24	   configuration
0.18/0.24	     name=mac.xml
0.18/0.27	   
0.18/0.28	   instance
0.18/0.28	     name=HOME/instance-1044632-1215028246.xml
0.28/0.31	   
0.28/0.31	   domains being loaded...
0.28/0.32	   
0.28/0.32	   variables being loaded...
0.28/0.35	     nbVariables=40  nbDomainTypes=1  minDomainSize=39  maxDomainSize=39  nbTotalValues=1560
0.28/0.35	       =>  wckTime=0.104  cpuTime=0.08  mem=7M919
0.28/0.35	   
0.28/0.35	   constraints being loaded...
0.37/0.42	     nbConstraints=40  nbGlobalConstraints=40  nbSharedBinaryRepresentations=0  minDegree=2  maxDegree=3  minArity=2
0.37/0.42	     avgArity=2.95  maxArity=40  nbGenerators=39  nbFusions=0  symmetryWckTime=0.051  symmetryCpuTime=0.03
0.37/0.42	       =>  wckTime=0.173  cpuTime=0.13  mem=10M869
0.37/0.47	   
0.37/0.47	   solver IterativeSystematicSolver being built... 
0.48/0.54	   
0.48/0.54	   INFO : Forward propagation technique limited 
0.57/0.62	       =>  wckTime=0.376  cpuTime=0.24  mem=19M543
0.57/0.62	   
0.57/0.62	   preprocessing
0.57/0.62	     nbConstraintChecks=0  nbPropagations=1  nbRevisions=0  nbUselessRevisions=0  nbRemovedValues=0
0.57/0.63	     detectedInconsistency=yes
0.57/0.63	       =>  wckTime=0.0020  cpuTime=0.0  mem=19M543
0.57/0.63	   
0.57/0.63	   global
0.57/0.63	     nbConstraintChecks=0  nbPropagations=1  nbRestartNogoods=0  solvingWckTime=0.0050  solvingCpuTime=0.0
0.57/0.63	     expiredTime=no  totalExploration=yes  nbFoundSolutions=0  globalCpuTime=0.3
0.57/0.63	       =>  wckTime=0.384  cpuTime=0.25  mem=19M543
0.57/0.63	   
0.57/0.63	s UNSATISFIABLE
0.57/0.63	d NODES 0
0.57/0.63	d CHECKS 0
0.57/0.63	   
0.57/0.63	   totalWckTime=0.45  totalCpuTime=0.3

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-1044632-1215028246/watcher-1044632-1215028246 -o /tmp/evaluation-result-1044632-1215028246/solver-1044632-1215028246 -C 1800 -W 2200 -M 900 --output-limit 1,15 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -cp abscon112V4.jar abscon.Resolution mac.xml 1 XSax HOME/instance-1044632-1215028246.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: 2.23 2.07 2.02 4/72 28374
/proc/meminfo: memFree=1783776/2055920 swapFree=4192812/4192956
[pid=28374] ppid=28372 vsize=152 CPUtime=0
/proc/28374/stat : 28374 (java) R 28372 28374 27015 0 -1 0 205 0 0 0 0 0 0 0 18 0 1 0 130209909 155648 26 996147200 134512640 134550740 4294955984 18446744073709551615 12591908 0 0 4096 0 0 0 0 17 0 0 0
/proc/28374/statm: 38 26 19 9 0 4 0

[startup+0.0865379 s]
/proc/loadavg: 2.23 2.07 2.02 4/72 28374
/proc/meminfo: memFree=1783776/2055920 swapFree=4192812/4192956
[pid=28374] ppid=28372 vsize=865884 CPUtime=0.07
/proc/28374/stat : 28374 (java) S 28372 28374 27015 0 -1 0 3621 0 1 0 5 2 0 0 18 0 9 0 130209909 886665216 3109 996147200 134512640 134550740 4294955984 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/28374/statm: 216471 3109 1667 9 0 211026 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 865884

[startup+0.103071 s]
/proc/loadavg: 2.23 2.07 2.02 4/72 28374
/proc/meminfo: memFree=1783776/2055920 swapFree=4192812/4192956
[pid=28374] ppid=28372 vsize=865884 CPUtime=0.09
/proc/28374/stat : 28374 (java) S 28372 28374 27015 0 -1 0 3737 0 1 0 7 2 0 0 18 0 9 0 130209909 886665216 3200 996147200 134512640 134550740 4294955984 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/28374/statm: 216471 3200 1695 9 0 211026 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 865884

[startup+0.301095 s]
/proc/loadavg: 2.23 2.07 2.02 4/72 28374
/proc/meminfo: memFree=1783776/2055920 swapFree=4192812/4192956
[pid=28374] ppid=28372 vsize=866284 CPUtime=0.28
/proc/28374/stat : 28374 (java) S 28372 28374 27015 0 -1 0 5925 0 1 0 24 4 0 0 18 0 9 0 130209909 887074816 5299 996147200 134512640 134550740 4294955984 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/28374/statm: 216571 5300 1956 9 0 211099 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 866284

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

[startup+0.501119 s]
/proc/loadavg: 2.23 2.07 2.02 4/72 28374
/proc/meminfo: memFree=1783776/2055920 swapFree=4192812/4192956
[pid=28374] ppid=28372 vsize=866972 CPUtime=0.48
/proc/28374/stat : 28374 (java) S 28372 28374 27015 0 -1 0 10417 273 1 0 42 6 0 0 18 0 9 0 130209909 887779328 7339 996147200 134512640 134550740 4294955984 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/28374/statm: 216743 7339 2626 9 0 211249 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 866972

[startup+0.601131 s]
/proc/loadavg: 2.23 2.07 2.02 4/72 28374
/proc/meminfo: memFree=1783776/2055920 swapFree=4192812/4192956
[pid=28374] ppid=28372 vsize=866972 CPUtime=0.57
/proc/28374/stat : 28374 (java) S 28372 28374 27015 0 -1 0 12753 273 1 0 51 6 0 0 18 0 9 0 130209909 887779328 8352 996147200 134512640 134550740 4294955984 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/28374/statm: 216743 8352 2627 9 0 211249 0
Current children cumulated CPU time (s) 0.57
Current children cumulated vsize (KiB) 866972

Child status: 0
Real time (s): 0.677456
CPU time (s): 0.632903
CPU user time (s): 0.542917
CPU system time (s): 0.089986
CPU usage (%): 93.4235
Max. virtual memory (cumulated for all children) (KiB): 866972

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.542917
system time used= 0.089986
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 14676
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 595
involuntary context switches= 624

runsolver used 0.003999 second user time and 0.012998 second system time

The end

Launcher Data (download as text)

Begin job on node28 at 2008-07-02 21:50:46
IDJOB=1044632
IDBENCH=53900
IDSOLVER=363
FILE ID=node28/1044632-1215028246
PBS_JOBID= 7874414
Free space on /tmp= 66544 MiB

SOLVER NAME= Abscon 112v4 AC
BENCH NAME= CPAI08/csp/pigeons_glb/normalized-pigeons-40_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -cp abscon112V4.jar abscon.Resolution mac.xml 1 XSax BENCHNAME
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1044632-1215028246/watcher-1044632-1215028246 -o /tmp/evaluation-result-1044632-1215028246/solver-1044632-1215028246 -C 1800 -W 2200 -M 900 --output-limit 1,15  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -cp abscon112V4.jar abscon.Resolution mac.xml 1 XSax HOME/instance-1044632-1215028246.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 4d2f128f0883e3ccf59e5ad375805964
RANDOM SEED=1866258281

node28.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.231
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.231
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:       1784256 kB
Buffers:         25312 kB
Cached:         115244 kB
SwapCached:          0 kB
Active:         173252 kB
Inactive:        43080 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1784256 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2780 kB
Writeback:           0 kB
Mapped:          85808 kB
Slab:            40552 kB
Committed_AS:   363872 kB
PageTables:       1892 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= 66544 MiB
End job on node28 at 2008-07-02 21:50:47