Trace number 191853

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 ESACUNSAT 0.886864 0.927261

DiagnosticValue
CHECKS12017
NODES0

General information on the benchmark

Namecomposed/composed-75-1-25/
composed-75-1-25-2_ext.xml
MD5SUM926a57a748b9c2e90417660875733010
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.061989
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables83
Number of constraints647
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension647
Number of constraints which are defined in intension0
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=esac.xml
0.34	   
0.34	   instance
0.34	     name=/tmp/evaluation/191853-1168096269/unknown.xml
0.37	   
0.37	   domains being loaded...
0.37	   
0.37	   variables being loaded...
0.42	     nbVariables=83  nbDomainTypes=1  minDomainSize=10  maxDomainSize=10
0.42	       =>  wckTime=0.105  cpuTime=0.09  mem=6M951
0.42	   
0.42	   relations being loaded...
0.51	   
0.51	   constraints being loaded...
0.65	     nbConstraints=647  nbRelationTypes=647  nbExtensionStructures=647  nbSharedExtensionStructures=0
0.65	     nbConflictsStructures=647  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=12263  maxDegree=23
0.65	     maxArity=2
0.65	       =>  wckTime=0.337  cpuTime=0.24  mem=11M844
0.69	   
0.69	   solver IterativeSystematicSolver being built... 
0.85	       =>  wckTime=0.538  cpuTime=0.36  mem=15M4
0.89	   
0.89	   preprocessing
0.89	     nbConstraintChecks=12017  nbPropagations=570  nbRevisions=2056  nbUselessRevisions=1513  nbSingletonTests=54
0.89	     nbEffectiveSingletonTests=6  nbESACBranches=1  nbRemovedValues=62  detectedInconsistency=yes
0.89	       =>  wckTime=0.037  cpuTime=0.02  mem=15M4
0.89	   
0.89	   global
0.89	     nbConstraintChecks=12017  nbPropagations=570  nbRevisions=2056  nbUselessRevisions=1513  nbRestartNogoods=0
0.89	     solvingWckTime=0.039  solvingCpuTime=0.02  expiredTime=no  totalExploration=yes  nbFoundSolutions=0
0.89	     globalCpuTime=0.44
0.89	       =>  wckTime=0.58  cpuTime=0.39  mem=15M4
0.89	   
0.89	s UNSATISFIABLE
0.89	d NODES 0
0.89	d CHECKS 12017
0.89	   
0.89	   totalWckTime=0.655  totalCpuTime=0.44

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/node26/watcher-191853-1168096269 -o ROOT/results/node26/solver-191853-1168096269 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/191853-1168096269/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.08 0.52 1.23 4/82 25081
/proc/meminfo: memFree=1303632/2055920 swapFree=4192812/4192956
[pid=25080] ppid=25076 vsize=168 CPUtime=0
/proc/25080/stat : 25080 (java) R 25076 25080 24427 0 -1 0 39 0 0 0 0 0 0 0 19 0 1 0 158022238 172032 23 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 12591908 0 0 4096 0 0 0 0 17 1 0 0
/proc/25080/statm: 42 23 18 14 0 2 0

[startup+0.10755 s]
/proc/loadavg: 0.08 0.52 1.23 4/82 25081
/proc/meminfo: memFree=1303632/2055920 swapFree=4192812/4192956
[pid=25080] ppid=25076 vsize=914988 CPUtime=0.07
/proc/25080/stat : 25080 (java) R 25076 25080 24427 0 -1 0 2958 0 1 0 6 1 0 0 17 0 8 0 158022238 936947712 2704 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4155166642 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/25080/statm: 228747 2705 1416 14 0 215242 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 914988

[startup+0.515584 s]
/proc/loadavg: 0.08 0.52 1.23 4/82 25081
/proc/meminfo: memFree=1303632/2055920 swapFree=4192812/4192956
[pid=25080] ppid=25076 vsize=915328 CPUtime=0.49
/proc/25080/stat : 25080 (java) R 25076 25080 24427 0 -1 0 6484 0 1 0 45 4 0 0 16 0 8 0 158022238 937295872 6223 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4152819938 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/25080/statm: 228832 6223 2138 14 0 215302 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.927261
CPU time (s): 0.886864
CPU user time (s): 0.818875
CPU system time (s): 0.067989
CPU usage (%): 95.6434
Max. virtual memory (cumulated for all children) (KiB): 915544

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

runsolver used 0.003999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node26 on Sat Jan  6 15:11:14 UTC 2007


IDJOB= 191853
IDBENCH= 3076
FILE ID= node26/191853-1168096269

PBS_JOBID= 3476735

Free space on /tmp= 66538 MiB

BENCH NAME= HOME/pub/bench/CPAI06/composed/composed-75-1-25/composed-75-1-25-2_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/191853-1168096269/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node26/watcher-191853-1168096269 -o ROOT/results/node26/solver-191853-1168096269 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/191853-1168096269/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  926a57a748b9c2e90417660875733010

RANDOM SEED= 283437621

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.236
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.236
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:       1304568 kB
Buffers:         44512 kB
Cached:         567284 kB
SwapCached:          0 kB
Active:         141548 kB
Inactive:       534524 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1304568 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1900 kB
Writeback:           0 kB
Mapped:          83288 kB
Slab:            60304 kB
Committed_AS:  2818464 kB
PageTables:       2112 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= 66537 MiB



End job on node26 on Sat Jan  6 15:11:33 UTC 2007