Trace number 252697

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.735888 0.769226

DiagnosticValue
CHECKS828
NODES6

General information on the benchmark

Namecoloring/
geom-40-3-ext.xml
MD5SUMd54325db3282ef19b94f41e995b8132d
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.003998
SatisfiableNO
(Un)Satisfiability was proved
Number of variables40
Number of constraints78
Maximum constraint arity2
Maximum domain size3
Number of constraints which are defined in extension78
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.33	   
0.33	Abscon 109 (November, 2006)
0.33	   
0.33	   configuration
0.33	     name=esac.xml
0.36	   
0.36	   instance
0.36	     name=/tmp/evaluation/252697-1168409548/unknown.xml
0.40	   
0.40	   domains being loaded...
0.40	   
0.40	   variables being loaded...
0.44	     nbVariables=40  nbDomainTypes=1  minDomainSize=3  maxDomainSize=3
0.44	       =>  wckTime=0.105  cpuTime=0.09  mem=6M951
0.44	   
0.44	   relations being loaded...
0.44	   
0.44	   constraints being loaded...
0.48	     nbConstraints=78  nbRelationTypes=1  nbSingletonDomainVariables=1  nbDisconnectedVariables=1
0.48	     nbExtensionStructures=1  nbSharedExtensionStructures=77  nbConflictsStructures=1  nbSharedConflictsStructures=77
0.48	     nbSharedBinaryRepresentations=3  maxDegree=6  maxArity=2
0.48	       =>  wckTime=0.152  cpuTime=0.12  mem=7M992
0.52	   
0.52	   solver IterativeSystematicSolver being built... 
0.70	       =>  wckTime=0.369  cpuTime=0.27  mem=14M404
0.73	   
0.73	   preprocessing
0.73	     nbConstraintChecks=696  nbPropagations=271  nbRevisions=280  nbUselessRevisions=16  nbSingletonTests=60
0.73	     nbEffectiveSingletonTests=0  nbESACBranches=19  nbRemovedValues=0  detectedInconsistency=no
0.73	       =>  wckTime=0.029  cpuTime=0.02  mem=14M404
0.74	   
0.74	   search
0.74	     run=0  nbConstraintChecks=132  nbPropagations=304  nbRevisions=336  nbUselessRevisions=17  nbAssignments=6
0.74	     nbFailedAssignments=3  nbBacktracks=4  nbVisitedNodes=12  nbRestartNogoods=0  mapSize=3  nbInferences=0
0.74	     nbTooLargeKeys=0
0.74	       =>  wckTime=0.038  cpuTime=0.03  mem=14M404
0.74	   
0.74	   global
0.74	     nbConstraintChecks=828  nbPropagations=575  nbRevisions=616  nbUselessRevisions=33  nbRestartNogoods=0
0.74	     solvingWckTime=0.04  solvingCpuTime=0.03  expiredTime=no  totalExploration=yes  nbFoundSolutions=0
0.74	     globalCpuTime=0.35
0.74	       =>  wckTime=0.41  cpuTime=0.3  mem=14M404
0.75	   
0.75	s UNSATISFIABLE
0.75	d NODES 6
0.75	d CHECKS 828
0.75	   
0.75	   totalWckTime=0.496  totalCpuTime=0.35

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/node5/watcher-252697-1168409548 -o ROOT/results/node5/solver-252697-1168409548 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/252697-1168409548/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
/proc/loadavg: 2.21 2.06 2.01 4/88 2135
/proc/meminfo: memFree=1167376/2055920 swapFree=4192812/4192956
[pid=2134] ppid=2132 vsize=18540 CPUtime=0
/proc/2134/stat : 2134 (runsolver) R 2132 2064 2064 0 -1 4194368 10 0 0 0 0 0 0 0 20 0 1 0 169569251 18984960 277 18446744073709551615 4194304 4267372 548682068944 18446744073709551615 226910841038 0 0 4096 24578 0 0 0 17 1 0 0
/proc/2134/statm: 4635 277 242 17 0 2626 0
Current StackSize limit: 10240 KiB


[startup+0.10828 s]
/proc/loadavg: 2.21 2.06 2.01 4/88 2135
/proc/meminfo: memFree=1167376/2055920 swapFree=4192812/4192956
[pid=2134] ppid=2132 vsize=914988 CPUtime=0.09
/proc/2134/stat : 2134 (java) R 2132 2134 2064 0 -1 0 2996 0 1 0 8 1 0 0 17 0 8 0 169569251 936947712 2742 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4072931672 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/2134/statm: 228747 2742 1427 14 0 215242 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 914988

[startup+0.516329 s]
/proc/loadavg: 2.21 2.06 2.01 4/88 2135
/proc/meminfo: memFree=1167376/2055920 swapFree=4192812/4192956
[pid=2134] ppid=2132 vsize=915328 CPUtime=0.49
/proc/2134/stat : 2134 (java) S 2132 2134 2064 0 -1 0 6400 0 1 0 45 4 0 0 18 0 8 0 169569251 937295872 6138 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/2134/statm: 228832 6138 2161 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.769226
CPU time (s): 0.735888
CPU user time (s): 0.676897
CPU system time (s): 0.058991
CPU usage (%): 95.666
Max. virtual memory (cumulated for all children) (KiB): 915460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.676897
system time used= 0.058991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8527
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= 430
involuntary context switches= 489

runsolver used 0.004999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Wed Jan 10 06:12:28 UTC 2007


IDJOB= 252697
IDBENCH= 12963
FILE ID= node5/252697-1168409548

PBS_JOBID= 3523199

Free space on /tmp= 66552 MiB

BENCH NAME= HOME/pub/bench/CPAI06/coloring/geom-40-3-ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/252697-1168409548/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-252697-1168409548 -o ROOT/results/node5/solver-252697-1168409548 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/252697-1168409548/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  d54325db3282ef19b94f41e995b8132d

RANDOM SEED= 141156082

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.240
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.240
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:       1167856 kB
Buffers:         60412 kB
Cached:         495760 kB
SwapCached:          0 kB
Active:         619568 kB
Inactive:       209476 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1167856 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1964 kB
Writeback:           0 kB
Mapped:         292708 kB
Slab:            43500 kB
Committed_AS:  5563696 kB
PageTables:       2624 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= 66552 MiB



End job on node5 on Wed Jan 10 06:12:29 UTC 2007