Trace number 2094020

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 ESACUNSAT 0.58191 0.631817

DiagnosticValue
CHECKS0
NODES0

General information on the benchmark

Namecsp/pigeons_glb/
normalized-pigeons-12_ext.xml
MD5SUM9196e5c7777f24f6f1d3b1cf02c8d7a0
Bench CategoryAlldiff (alldiff)
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 variables12
Number of constraints1
Maximum constraint arity12
Maximum domain size11
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 

0.01/0.09	
0.01/0.09	Abscon 112 (May, 2008)
0.18/0.24	
0.18/0.24	   configuration
0.18/0.24	     name=esac.xml
0.18/0.28	   
0.18/0.28	   instance
0.18/0.28	     name=HOME/instance-2094020-1247402307.xml
0.28/0.32	   
0.28/0.32	   domains being loaded...
0.28/0.32	   
0.28/0.33	   variables being loaded...
0.28/0.35	     nbVariables=12  nbDomainTypes=1  minDomainSize=11  maxDomainSize=11  nbTotalValues=132
0.28/0.35	       =>  wckTime=0.104  cpuTime=0.08  mem=7M892
0.28/0.35	   
0.28/0.35	   constraints being loaded...
0.37/0.40	     nbConstraints=12  nbGlobalConstraints=12  nbSharedBinaryRepresentations=0  minDegree=2  maxDegree=3  minArity=2
0.37/0.40	     avgArity=2.83  maxArity=12  nbGenerators=11  nbFusions=0  symmetryWckTime=0.034  symmetryCpuTime=0.02
0.37/0.40	       =>  wckTime=0.156  cpuTime=0.12  mem=10M990
0.37/0.44	   
0.37/0.44	   solver IterativeSystematicSolver being built... 
0.47/0.52	   
0.47/0.52	   INFO : Forward propagation technique limited 
0.47/0.58	       =>  wckTime=0.339  cpuTime=0.23  mem=19M501
0.47/0.59	   
0.47/0.59	   preprocessing
0.47/0.59	     nbConstraintChecks=0  nbPropagations=1  nbRevisions=0  nbUselessRevisions=0  nbRemovedValues=0
0.47/0.59	     detectedInconsistency=yes
0.47/0.59	       =>  wckTime=0.0020  cpuTime=0.0  mem=19M501
0.47/0.59	   
0.47/0.59	   global
0.47/0.59	     nbConstraintChecks=0  nbPropagations=1  nbRestartNogoods=0  solvingWckTime=0.0040  solvingCpuTime=0.01
0.47/0.59	     expiredTime=no  totalExploration=yes  nbFoundSolutions=0  globalCpuTime=0.29
0.47/0.59	       =>  wckTime=0.345  cpuTime=0.24  mem=19M501
0.47/0.59	   
0.47/0.59	s UNSATISFIABLE
0.47/0.59	d NODES 0
0.47/0.59	d CHECKS 0
0.47/0.59	   
0.47/0.59	   totalWckTime=0.411  totalCpuTime=0.3

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-2094020-1247402307/watcher-2094020-1247402307 -o /tmp/evaluation-result-2094020-1247402307/solver-2094020-1247402307 -C 1800 -W 2000 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -cp abscon112V4.jar abscon.Resolution esac.xml 1 XSax HOME/instance-2094020-1247402307.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.99 1.94 1.41 4/81 31815
/proc/meminfo: memFree=1800232/2055920 swapFree=4192812/4192956
[pid=31815] ppid=31813 vsize=18576 CPUtime=0
/proc/31815/stat : 31815 (runsolver) R 31813 31815 31337 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 27296100 19021824 284 996147200 4194304 4302564 548682068384 18446744073709551615 243665530151 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/31815/statm: 4644 284 249 26 0 2626 0

[startup+0.0288991 s]
/proc/loadavg: 1.99 1.94 1.41 4/81 31815
/proc/meminfo: memFree=1800232/2055920 swapFree=4192812/4192956
[pid=31815] ppid=31813 vsize=861936 CPUtime=0.01
/proc/31815/stat : 31815 (java) S 31813 31815 31337 0 -1 0 1885 0 1 0 0 1 0 0 21 0 5 0 27296100 882622464 1568 996147200 134512640 134550932 4294955968 18446744073709551615 4294960144 0 0 0 16784584 18446744073709551615 0 0 17 0 0 0
/proc/31815/statm: 215484 1568 688 9 0 210399 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 861936

[startup+0.101913 s]
/proc/loadavg: 1.99 1.94 1.41 4/81 31815
/proc/meminfo: memFree=1800232/2055920 swapFree=4192812/4192956
[pid=31815] ppid=31813 vsize=865980 CPUtime=0.09
/proc/31815/stat : 31815 (java) S 31813 31815 31337 0 -1 0 3739 0 1 0 7 2 0 0 21 0 9 0 27296100 886763520 3207 996147200 134512640 134550932 4294955968 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/31815/statm: 216495 3207 1700 9 0 210980 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 865980

[startup+0.30195 s]
/proc/loadavg: 1.99 1.94 1.41 4/81 31815
/proc/meminfo: memFree=1800232/2055920 swapFree=4192812/4192956
[pid=31815] ppid=31813 vsize=866380 CPUtime=0.28
/proc/31815/stat : 31815 (java) S 31813 31815 31337 0 -1 0 5984 0 1 0 24 4 0 0 21 0 9 0 27296100 887173120 5350 996147200 134512640 134550932 4294955968 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/31815/statm: 216595 5350 1984 9 0 211053 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 866380

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

[startup+0.501988 s]
/proc/loadavg: 1.99 1.94 1.41 4/81 31815
/proc/meminfo: memFree=1800232/2055920 swapFree=4192812/4192956
[pid=31815] ppid=31813 vsize=866904 CPUtime=0.47
/proc/31815/stat : 31815 (java) S 31813 31815 31337 0 -1 0 10731 272 1 0 41 6 0 0 21 0 9 0 27296100 887709696 7351 996147200 134512640 134550932 4294955968 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/31815/statm: 216726 7351 2651 9 0 211162 0
Current children cumulated CPU time (s) 0.47
Current children cumulated vsize (KiB) 866904

[startup+0.602 s]
/proc/loadavg: 1.99 1.94 1.41 4/81 31815
/proc/meminfo: memFree=1800232/2055920 swapFree=4192812/4192956
[pid=31815] ppid=31813 vsize=867052 CPUtime=0.56
/proc/31815/stat : 31815 (java) S 31813 31815 31337 0 -1 0 14380 272 1 0 48 8 0 0 21 0 9 0 27296100 887861248 10008 996147200 134512640 134550932 4294955968 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/31815/statm: 216763 10008 2653 9 0 211199 0
Current children cumulated CPU time (s) 0.56
Current children cumulated vsize (KiB) 867052

Child status: 0
Real time (s): 0.631817
CPU time (s): 0.58191
CPU user time (s): 0.488925
CPU system time (s): 0.092985
CPU usage (%): 92.101
Max. virtual memory (cumulated for all children) (KiB): 867052

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

runsolver used 0.001999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node84 at 2009-07-12 14:38:27
IDJOB=2094020
IDBENCH=53908
IDSOLVER=774
FILE ID=node84/2094020-1247402307
PBS_JOBID= 9510483
Free space on /tmp= 66316 MiB

SOLVER NAME= Abscon 112v4 ESAC
BENCH NAME= CPAI08/csp/pigeons_glb/normalized-pigeons-12_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -cp abscon112V4.jar abscon.Resolution esac.xml 1 XSax BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2094020-1247402307/watcher-2094020-1247402307 -o /tmp/evaluation-result-2094020-1247402307/solver-2094020-1247402307 -C 1800 -W 2000 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -cp abscon112V4.jar abscon.Resolution esac.xml 1 XSax HOME/instance-2094020-1247402307.xml

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

MD5SUM BENCH= 9196e5c7777f24f6f1d3b1cf02c8d7a0
RANDOM SEED=1297797434

node84.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.259
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.259
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:       1800584 kB
Buffers:         32244 kB
Cached:         118308 kB
SwapCached:          0 kB
Active:         133096 kB
Inactive:        66600 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1800584 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2328 kB
Writeback:           0 kB
Mapped:          67448 kB
Slab:            40820 kB
Committed_AS:  1007232 kB
PageTables:       1816 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= 66312 MiB
End job on node84 at 2009-07-12 14:38:28