Trace number 244703

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.902862 0.932872

DiagnosticValue
CHECKS169
NODES0

General information on the benchmark

Namedimacs/
jnhUnsat/jnh302_ext.xml
MD5SUM26910c14e0d5a375ffdaad373f23f2c9
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.052991
SatisfiableNO
(Un)Satisfiability was proved
Number of variables100
Number of constraints898
Maximum constraint arity10
Maximum domain size2
Number of constraints which are defined in extension898
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=mac.xml
0.34	   
0.34	   instance
0.34	     name=/tmp/evaluation/244703-1168085718/unknown.xml
0.37	   
0.37	   domains being loaded...
0.38	   
0.38	   variables being loaded...
0.41	     nbVariables=100  nbDomainTypes=1  minDomainSize=2  maxDomainSize=2
0.41	       =>  wckTime=0.096  cpuTime=0.08  mem=6M951
0.41	   
0.41	   relations being loaded...
0.46	   
0.46	   constraints being loaded...
0.63	     nbConstraints=898  nbRelationTypes=248  nbExtensionStructures=248  nbSharedExtensionStructures=650
0.63	     nbConflictsStructures=248  nbSharedConflictsStructures=650  nbSharedBinaryRepresentations=16  maxDegree=65
0.63	     maxArity=10
0.63	       =>  wckTime=0.315  cpuTime=0.22  mem=11M827
0.67	   
0.67	   solver IterativeSystematicSolver being built... 
0.88	       =>  wckTime=0.567  cpuTime=0.4  mem=23M150
0.90	   
0.90	   preprocessing
0.90	     nbConstraintChecks=169  nbValidityChecks=3  nbPropagations=130  nbRevisions=138  nbUselessRevisions=100
0.90	     nbRemovedValues=38  detectedInconsistency=yes
0.90	       =>  wckTime=0.018  cpuTime=0.01  mem=23M150
0.90	   
0.90	   global
0.90	     nbConstraintChecks=169  nbValidityChecks=3  nbPropagations=130  nbRevisions=138  nbUselessRevisions=100
0.90	     nbRestartNogoods=0  solvingWckTime=0.02  solvingCpuTime=0.01  expiredTime=no  totalExploration=yes
0.90	     nbFoundSolutions=0  globalCpuTime=0.45
0.90	       =>  wckTime=0.588  cpuTime=0.41  mem=23M150
0.90	   
0.90	s UNSATISFIABLE
0.91	d NODES 0
0.91	d CHECKS 169
0.91	   
0.91	   totalWckTime=0.664  totalCpuTime=0.45

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/node4/watcher-244703-1168085718 -o ROOT/results/node4/solver-244703-1168085718 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/244703-1168085718/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.07 0.41 1.06 4/81 15264
/proc/meminfo: memFree=1585824/2055920 swapFree=4191880/4192956
[pid=15263] ppid=15261 vsize=1496 CPUtime=0
/proc/15263/stat : 15263 (java) R 15261 15263 15083 0 -1 0 63 0 0 0 0 0 0 0 20 0 1 0 156968231 1531904 46 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 10573440 0 0 4096 0 0 0 0 17 1 0 0
/proc/15263/statm: 375 55 43 14 0 8 0

[startup+0.105644 s]
/proc/loadavg: 0.07 0.41 1.06 4/81 15264
/proc/meminfo: memFree=1585824/2055920 swapFree=4191880/4192956
[pid=15263] ppid=15261 vsize=913068 CPUtime=0.07
/proc/15263/stat : 15263 (java) S 15261 15263 15083 0 -1 0 2886 0 1 0 6 1 0 0 16 0 8 0 156968231 934981632 2632 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/15263/statm: 228267 2634 1396 14 0 215168 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 913068

[startup+0.513744 s]
/proc/loadavg: 0.07 0.41 1.06 4/81 15264
/proc/meminfo: memFree=1585824/2055920 swapFree=4191880/4192956
[pid=15263] ppid=15261 vsize=915328 CPUtime=0.48
/proc/15263/stat : 15263 (java) R 15261 15263 15083 0 -1 0 6305 0 1 0 45 3 0 0 16 0 8 0 156968231 937295872 6044 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4072917395 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/15263/statm: 228832 6044 2137 14 0 215302 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.932872
CPU time (s): 0.902862
CPU user time (s): 0.832873
CPU system time (s): 0.069989
CPU usage (%): 96.7831
Max. virtual memory (cumulated for all children) (KiB): 915556

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.832873
system time used= 0.069989
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 10702
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= 669
involuntary context switches= 74

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Sat Jan  6 12:15:24 UTC 2007


IDJOB= 244703
IDBENCH= 8495
FILE ID= node4/244703-1168085718

PBS_JOBID= 3476334

Free space on /tmp= 66308 MiB

BENCH NAME= HOME/pub/bench/CPAI06/dimacs/jnhUnsat/jnh302_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/244703-1168085718/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-244703-1168085718 -o ROOT/results/node4/solver-244703-1168085718 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/244703-1168085718/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  26910c14e0d5a375ffdaad373f23f2c9

RANDOM SEED= 719647262

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.223
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.223
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:       1586304 kB
Buffers:         54776 kB
Cached:         281828 kB
SwapCached:        268 kB
Active:          90784 kB
Inactive:       295348 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1586304 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            1844 kB
Writeback:           0 kB
Mapped:          67768 kB
Slab:            68388 kB
Committed_AS:  3811240 kB
PageTables:       2232 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= 66308 MiB



End job on node4 on Sat Jan  6 12:15:34 UTC 2007