Trace number 192172

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.974851 1.05786

DiagnosticValue
CHECKS19097
NODES0

General information on the benchmark

Namecomposed/composed-75-1-2/
composed-75-1-2-2_ext.xml
MD5SUM31eea0700df14e1c9aa3b697ecbd85ff
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.05499
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables83
Number of constraints624
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension624
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.34	   
0.34	Abscon 109 (November, 2006)
0.34	   
0.34	   configuration
0.34	     name=esac.xml
0.37	   
0.37	   instance
0.37	     name=/tmp/evaluation/192172-1168096717/unknown.xml
0.41	   
0.41	   domains being loaded...
0.41	   
0.41	   variables being loaded...
0.46	     nbVariables=83  nbDomainTypes=1  minDomainSize=10  maxDomainSize=10
0.46	       =>  wckTime=0.118  cpuTime=0.1  mem=6M951
0.46	   
0.46	   relations being loaded...
0.56	   
0.56	   constraints being loaded...
0.71	     nbConstraints=624  nbRelationTypes=624  nbExtensionStructures=624  nbSharedExtensionStructures=0
0.71	     nbConflictsStructures=624  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=11803  maxDegree=23
0.71	     maxArity=2
0.71	       =>  wckTime=0.37  cpuTime=0.25  mem=11M860
0.76	   
0.76	   solver IterativeSystematicSolver being built... 
0.93	       =>  wckTime=0.593  cpuTime=0.4  mem=14M981
0.99	   
0.99	   preprocessing
0.99	     nbConstraintChecks=19097  nbPropagations=1013  nbRevisions=3574  nbUselessRevisions=2669  nbSingletonTests=127
0.99	     nbEffectiveSingletonTests=5  nbESACBranches=2  nbRemovedValues=67  detectedInconsistency=yes
0.99	       =>  wckTime=0.057  cpuTime=0.03  mem=14M981
0.99	   
0.99	   global
0.99	     nbConstraintChecks=19097  nbPropagations=1013  nbRevisions=3574  nbUselessRevisions=2669  nbRestartNogoods=0
0.99	     solvingWckTime=0.059  solvingCpuTime=0.03  expiredTime=no  totalExploration=yes  nbFoundSolutions=0
0.99	     globalCpuTime=0.49
0.99	       =>  wckTime=0.654  cpuTime=0.44  mem=14M981
1.00	   
1.00	s UNSATISFIABLE
1.00	d NODES 0
1.00	d CHECKS 19097
1.00	   
1.00	   totalWckTime=0.738  totalCpuTime=0.5

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/node7/watcher-192172-1168096717 -o ROOT/results/node7/solver-192172-1168096717 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/192172-1168096717/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: 1.09 1.12 1.43 4/86 23718
/proc/meminfo: memFree=1258592/2055920 swapFree=4192812/4192956
[pid=23717] ppid=23715 vsize=168 CPUtime=0
/proc/23717/stat : 23717 (java) R 23715 23717 23579 0 -1 0 39 0 0 0 0 0 0 0 18 0 1 0 158067707 172032 23 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 10416427 0 0 4096 0 0 0 0 17 0 0 0
/proc/23717/statm: 42 23 18 14 0 2 0

[startup+0.108589 s]
/proc/loadavg: 1.09 1.12 1.43 4/86 23718
/proc/meminfo: memFree=1258592/2055920 swapFree=4192812/4192956
[pid=23717] ppid=23715 vsize=912588 CPUtime=0.08
/proc/23717/stat : 23717 (java) R 23715 23717 23579 0 -1 0 2751 0 1 0 6 2 0 0 20 0 8 0 158067707 934490112 2497 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4072927684 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/23717/statm: 228147 2497 1382 14 0 215091 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 912588

[startup+0.516631 s]
/proc/loadavg: 1.09 1.12 1.43 4/86 23718
/proc/meminfo: memFree=1258592/2055920 swapFree=4192812/4192956
[pid=23717] ppid=23715 vsize=915328 CPUtime=0.47
/proc/23717/stat : 23717 (java) R 23715 23717 23579 0 -1 0 6264 0 1 0 42 5 0 0 18 0 8 0 158067707 937295872 6003 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4073556288 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/23717/statm: 228832 6003 2137 14 0 215302 0
Current children cumulated CPU time (s) 0.47
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 1.05786
CPU time (s): 0.974851
CPU user time (s): 0.887865
CPU system time (s): 0.086986
CPU usage (%): 92.1529
Max. virtual memory (cumulated for all children) (KiB): 915544

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.887865
system time used= 0.086986
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8721
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= 970
involuntary context switches= 964

runsolver used 0.001999 s user time and 0.009998 s system time

The end

Launcher Data (download as text)

Begin job on node7 on Sat Jan  6 15:18:39 UTC 2007


IDJOB= 192172
IDBENCH= 3095
FILE ID= node7/192172-1168096717

PBS_JOBID= 3476498

Free space on /tmp= 66524 MiB

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

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  31eea0700df14e1c9aa3b697ecbd85ff

RANDOM SEED= 445318247

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.220
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.220
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:       1259008 kB
Buffers:         80308 kB
Cached:         506532 kB
SwapCached:          0 kB
Active:         402876 kB
Inactive:       290756 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1259008 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1892 kB
Writeback:           0 kB
Mapped:         128260 kB
Slab:            87860 kB
Committed_AS:  4401396 kB
PageTables:       2416 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= 66524 MiB



End job on node7 on Sat Jan  6 15:18:47 UTC 2007