Trace number 2093990

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.629903 0.693143

DiagnosticValue
CHECKS0
NODES0

General information on the benchmark

Namecsp/pigeons_glb/
normalized-pigeons-25_ext.xml
MD5SUM743188b6e1d83e22a43c39ff1279a77e
Bench CategoryAlldiff (alldiff)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.008998
Satisfiable
(Un)Satisfiability was proved
Number of variables25
Number of constraints1
Maximum constraint arity25
Maximum domain size24
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.04/0.09	
0.04/0.09	Abscon 112 (May, 2008)
0.18/0.25	
0.18/0.25	   configuration
0.18/0.25	     name=esac.xml
0.18/0.29	   
0.18/0.29	   instance
0.18/0.29	     name=HOME/instance-2093990-1247402302.xml
0.28/0.32	   
0.28/0.32	   domains being loaded...
0.28/0.33	   
0.28/0.33	   variables being loaded...
0.28/0.36	     nbVariables=25  nbDomainTypes=1  minDomainSize=24  maxDomainSize=24  nbTotalValues=600
0.28/0.36	       =>  wckTime=0.101  cpuTime=0.09  mem=7M892
0.28/0.36	   
0.28/0.36	   constraints being loaded...
0.38/0.41	     nbConstraints=25  nbGlobalConstraints=25  nbSharedBinaryRepresentations=0  minDegree=2  maxDegree=3  minArity=2
0.38/0.41	     avgArity=2.92  maxArity=25  nbGenerators=24  nbFusions=0  symmetryWckTime=0.039  symmetryCpuTime=0.03
0.38/0.41	       =>  wckTime=0.159  cpuTime=0.14  mem=10M859
0.38/0.46	   
0.38/0.47	   solver IterativeSystematicSolver being built... 
0.47/0.55	   
0.47/0.55	   INFO : Forward propagation technique limited 
0.57/0.62	       =>  wckTime=0.369  cpuTime=0.26  mem=19M496
0.57/0.63	   
0.57/0.63	   preprocessing
0.57/0.63	     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=19M496
0.57/0.63	   
0.57/0.63	   global
0.57/0.63	     nbConstraintChecks=0  nbPropagations=1  nbRestartNogoods=0  solvingWckTime=0.0040  solvingCpuTime=0.0
0.57/0.63	     expiredTime=no  totalExploration=yes  nbFoundSolutions=0  globalCpuTime=0.3
0.57/0.63	       =>  wckTime=0.376  cpuTime=0.26  mem=20M471
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.441  totalCpuTime=0.31

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-2093990-1247402302/watcher-2093990-1247402302 -o /tmp/evaluation-result-2093990-1247402302/solver-2093990-1247402302 -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-2093990-1247402302.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: 2.13 1.99 1.44 4/80 2080
/proc/meminfo: memFree=1805264/2055920 swapFree=4192812/4192956
[pid=2080] ppid=2078 vsize=18576 CPUtime=0
/proc/2080/stat : 2080 (runsolver) R 2078 2080 32688 0 -1 4194368 16 0 0 0 0 0 0 0 19 0 1 0 27293695 19021824 284 996147200 4194304 4302564 548682068384 18446744073709551615 235371293991 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/2080/statm: 4644 284 249 26 0 2626 0

[startup+0.067834 s]
/proc/loadavg: 2.13 1.99 1.44 4/80 2080
/proc/meminfo: memFree=1805264/2055920 swapFree=4192812/4192956
[pid=2080] ppid=2078 vsize=864024 CPUtime=0.04
/proc/2080/stat : 2080 (java) S 2078 2080 32688 0 -1 0 2817 0 1 0 3 1 0 0 18 0 9 0 27293695 884760576 2353 996147200 134512640 134550932 4294955968 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/2080/statm: 216006 2353 1117 9 0 210899 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 864024

[startup+0.101795 s]
/proc/loadavg: 2.13 1.99 1.44 4/80 2080
/proc/meminfo: memFree=1805264/2055920 swapFree=4192812/4192956
[pid=2080] ppid=2078 vsize=865984 CPUtime=0.08
/proc/2080/stat : 2080 (java) S 2078 2080 32688 0 -1 0 3720 0 1 0 6 2 0 0 18 0 9 0 27293695 886767616 3188 996147200 134512640 134550932 4294955968 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/2080/statm: 216496 3188 1695 9 0 210981 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 865984

[startup+0.30181 s]
/proc/loadavg: 2.13 1.99 1.44 4/80 2080
/proc/meminfo: memFree=1805264/2055920 swapFree=4192812/4192956
[pid=2080] ppid=2078 vsize=867412 CPUtime=0.28
/proc/2080/stat : 2080 (java) S 2078 2080 32688 0 -1 0 5937 0 1 0 25 3 0 0 18 0 9 0 27293695 888229888 5303 996147200 134512640 134550932 4294955968 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/2080/statm: 216853 5303 1983 9 0 211311 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 867412

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

[startup+0.501835 s]
/proc/loadavg: 2.13 1.99 1.44 4/80 2080
/proc/meminfo: memFree=1805264/2055920 swapFree=4192812/4192956
[pid=2080] ppid=2078 vsize=867984 CPUtime=0.47
/proc/2080/stat : 2080 (java) S 2078 2080 32688 0 -1 0 10503 276 1 0 41 6 0 0 18 0 9 0 27293695 888815616 7417 996147200 134512640 134550932 4294955968 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/2080/statm: 216996 7417 2651 9 0 211432 0
Current children cumulated CPU time (s) 0.47
Current children cumulated vsize (KiB) 867984

[startup+0.601844 s]
/proc/loadavg: 2.13 1.99 1.44 4/80 2080
/proc/meminfo: memFree=1805264/2055920 swapFree=4192812/4192956
[pid=2080] ppid=2078 vsize=867984 CPUtime=0.57
/proc/2080/stat : 2080 (java) S 2078 2080 32688 0 -1 0 12764 276 1 0 50 7 0 0 18 0 9 0 27293695 888815616 8347 996147200 134512640 134550932 4294955968 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/2080/statm: 216996 8347 2651 9 0 211432 0
Current children cumulated CPU time (s) 0.57
Current children cumulated vsize (KiB) 867984

Child status: 0
Real time (s): 0.693143
CPU time (s): 0.629903
CPU user time (s): 0.527919
CPU system time (s): 0.101984
CPU usage (%): 90.8764
Max. virtual memory (cumulated for all children) (KiB): 867984

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

runsolver used 0.001999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node51 at 2009-07-12 14:38:22
IDJOB=2093990
IDBENCH=53893
IDSOLVER=774
FILE ID=node51/2093990-1247402302
PBS_JOBID= 9510543
Free space on /tmp= 66204 MiB

SOLVER NAME= Abscon 112v4 ESAC
BENCH NAME= CPAI08/csp/pigeons_glb/normalized-pigeons-25_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-2093990-1247402302/watcher-2093990-1247402302 -o /tmp/evaluation-result-2093990-1247402302/solver-2093990-1247402302 -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-2093990-1247402302.xml

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

MD5SUM BENCH= 743188b6e1d83e22a43c39ff1279a77e
RANDOM SEED=1455529111

node51.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.225
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.225
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:       1805744 kB
Buffers:         39596 kB
Cached:         100280 kB
SwapCached:          0 kB
Active:         143936 kB
Inactive:        47308 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1805744 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2584 kB
Writeback:           0 kB
Mapped:          71868 kB
Slab:            44112 kB
Committed_AS:  1019056 kB
PageTables:       1876 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= 66204 MiB
End job on node51 at 2009-07-12 14:38:23