Trace number 246914

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, and are wall clock time (not CPU 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 109 ACUNSAT 0.989849 1.035

DiagnosticValue
CHECKS126880
NODES15

General information on the benchmark

Namerlfap/
rlfapSubs/scen06-sub4.xml
MD5SUM2f2ef4b2595ce0c7e703964138e6a5a2
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.178972
SatisfiableNO
(Un)Satisfiability was proved
Number of variables44
Number of constraints499
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension499
Global constraints used (with number of constraints)

Solver Data (download as text)

0.31	   
0.31	Abscon 109 (November, 2006)
0.31	   
0.31	   configuration
0.31	     name=mac.xml
0.34	   
0.34	   instance
0.34	     name=/tmp/evaluation/246914-1168085791/unknown.xml
0.38	   
0.38	   domains being loaded...
0.38	   
0.38	   variables being loaded...
0.42	     nbVariables=44  nbDomainTypes=2  minDomainSize=36  maxDomainSize=44
0.42	       =>  wckTime=0.099  cpuTime=0.07  mem=6M887
0.42	   
0.42	   predicates being loaded...
0.42	   
0.42	   constraints being loaded...
0.74	     nbConstraints=499  nbConvertedConstraints=499  nbConvertConstraintsChecks=270496  nbExtensionStructures=156
0.74	     nbSharedExtensionStructures=343  nbConflictsStructures=156  nbSharedConflictsStructures=343
0.74	     nbSharedBinaryRepresentations=12078  maxDegree=36  maxArity=2
0.74	       =>  wckTime=0.426  cpuTime=0.31  mem=10M788
0.78	   
0.78	   solver IterativeSystematicSolver being built... 
0.94	       =>  wckTime=0.625  cpuTime=0.45  mem=14M634
0.96	   
0.96	   preprocessing
0.96	     nbConstraintChecks=20376  nbPropagations=65  nbRevisions=811  nbUselessRevisions=714  nbRemovedValues=1028
0.96	     detectedInconsistency=no
0.96	       =>  wckTime=0.022  cpuTime=0.01  mem=14M634
1.00	   
1.00	   search
1.00	     run=0  nbConstraintChecks=106504  nbPropagations=345  nbRevisions=8689  nbUselessRevisions=7500  nbAssignments=15
1.00	     nbFailedAssignments=15  nbBacktracks=1  nbVisitedNodes=31  nbRestartNogoods=0  mapSize=0  nbInferences=0
1.00	     nbTooLargeKeys=0
1.00	       =>  wckTime=0.052  cpuTime=0.03  mem=14M634
1.00	   
1.00	   global
1.00	     nbConstraintChecks=126880  nbPropagations=410  nbRevisions=9500  nbUselessRevisions=8214  nbRestartNogoods=0
1.00	     solvingWckTime=0.054  solvingCpuTime=0.03  expiredTime=no  totalExploration=yes  nbFoundSolutions=0
1.00	     globalCpuTime=0.54
1.00	       =>  wckTime=0.681  cpuTime=0.48  mem=14M634
1.00	   
1.00	s UNSATISFIABLE
1.00	d NODES 15
1.00	d CHECKS 126880
1.00	   
1.00	   totalWckTime=0.767  totalCpuTime=0.54

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node9/watcher-246914-1168085791 -o ROOT/results/node9/solver-246914-1168085791 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/246914-1168085791/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 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

/proc/loadavg: 0.44 0.54 1.18 5/93 20581
/proc/meminfo: memFree=1010608/2055920 swapFree=4191880/4192956
[pid=20580] ppid=20578 vsize=18540 CPUtime=0
/proc/20580/stat : 20580 (runsolver) R 20578 20580 19774 0 -1 4194368 17 0 0 0 0 0 0 0 18 0 1 0 156975699 18984960 279 18446744073709551615 4194304 4267372 548682068960 18446744073709551615 215418989863 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/20580/statm: 4635 279 244 17 0 2626 0

[startup+0.10857 s]
/proc/loadavg: 0.44 0.54 1.18 5/93 20581
/proc/meminfo: memFree=1010608/2055920 swapFree=4191880/4192956
[pid=20580] ppid=20578 vsize=914988 CPUtime=0.09
/proc/20580/stat : 20580 (java) R 20578 20580 19774 0 -1 0 3048 0 1 0 8 1 0 0 17 0 8 0 156975699 936947712 2794 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/20580/statm: 228747 2794 1446 14 0 215242 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 914988

[startup+0.520615 s]
/proc/loadavg: 0.44 0.54 1.18 5/93 20581
/proc/meminfo: memFree=1010608/2055920 swapFree=4191880/4192956
[pid=20580] ppid=20578 vsize=915328 CPUtime=0.5
/proc/20580/stat : 20580 (java) S 20578 20580 19774 0 -1 0 6363 0 1 0 46 4 0 0 18 0 8 0 156975699 937295872 6102 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/20580/statm: 228832 6102 2147 14 0 215302 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 1.035
CPU time (s): 0.989849
CPU user time (s): 0.900863
CPU system time (s): 0.088986
CPU usage (%): 95.6379
Max. virtual memory (cumulated for all children) (KiB): 915556

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

runsolver used 0.002999 s user time and 0.009998 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Sat Jan  6 12:16:37 UTC 2007


IDJOB= 246914
IDBENCH= 11073
FILE ID= node9/246914-1168085791

PBS_JOBID= 3476290

Free space on /tmp= 66536 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapSubs/scen06-sub4.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/246914-1168085791/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-246914-1168085791 -o ROOT/results/node9/solver-246914-1168085791 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/246914-1168085791/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  2f2ef4b2595ce0c7e703964138e6a5a2

RANDOM SEED= 410639702

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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:       1011024 kB
Buffers:         84236 kB
Cached:         599168 kB
SwapCached:        268 kB
Active:         540132 kB
Inactive:       402228 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1011024 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            3440 kB
Writeback:           0 kB
Mapped:         280720 kB
Slab:            86868 kB
Committed_AS:  4852936 kB
PageTables:       2752 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= 66536 MiB



End job on node9 on Sat Jan  6 12:16:57 UTC 2007