Open GoogleCodeExporter opened 8 years ago
Can you try updating and running again? This used to happen but it should be
fixed by now. If it happens even
after updating, please zip and post your log.
Original comment by gianmerlino@gmail.com
on 15 May 2009 at 3:39
Well, I can't upload a file....I am trying but I don't see it after....is there
a limit on size? mine is about 8.8Mb
zipped?
Same thing happened this week, updated to 258 right before running....it just
flat ignores Yoggy
Original comment by 19vett...@gmail.com
on 24 May 2009 at 3:24
OK, last weeks is http://www.fawws.net/WoWLog1.txt.zip
This weeks (Including kill) is http://www.fawws.net/WoWLog.txt.zip
Original comment by 19vett...@gmail.com
on 24 May 2009 at 3:27
I tried both of your logs using r258. The first one (wowlog1.txt.zip) worked
without problems. The full output is:
% curl -s http://www.fawws.net/WoWLog1.txt.zip | funzip | ./stasis add -attempt
-dir wowlog1
./stasis: Using directory: wowlog1
./stasis: Encounter start: yoggsaron at 5/14 19:47:07.463 .. writing Yogg-Saron
try 1 (sws-yoggsaron-1242355627) .. done.
./stasis: Encounter start: yoggsaron at 5/14 19:57:45.097 .. writing Yogg-Saron
try 2 (sws-yoggsaron-1242356265) .. done.
./stasis: Encounter start: yoggsaron at 5/14 20:13:39.934 .. writing Yogg-Saron
try 3 (sws-yoggsaron-1242357219) .. done.
./stasis: Encounter start: yoggsaron at 5/14 20:21:34.033 .. writing Yogg-Saron
try 4 (sws-yoggsaron-1242357694) .. done.
./stasis: Encounter start: yoggsaron at 5/14 20:39:59.991 .. writing Yogg-Saron
try 5 (sws-yoggsaron-1242358799) .. done.
./stasis: Encounter start: yoggsaron at 5/14 20:49:07.849 .. writing Yogg-Saron
try 6 (sws-yoggsaron-1242359347) .. done.
./stasis: Encounter start: yoggsaron at 5/14 20:57:18.287 .. writing Yogg-Saron
try 7 (sws-yoggsaron-1242359838) .. done.
./stasis: Encounter start: yoggsaron at 5/14 21:13:11.634 .. writing Yogg-Saron
try 8 (sws-yoggsaron-1242360791) .. done.
./stasis: Encounter start: yoggsaron at 5/14 21:28:00.419 .. writing Yogg-Saron
try 9 (sws-yoggsaron-1242361680) .. done.
./stasis: Encounter start: yoggsaron at 5/14 21:34:09.005 .. writing Yogg-Saron
try 10 (sws-yoggsaron-1242362049) .. done.
./stasis: Encounter start: yoggsaron at 5/14 21:41:16.721 .. writing Yogg-Saron
try 11 (sws-yoggsaron-1242362476) .. done.
./stasis: Encounter start: yoggsaron at 5/14 21:58:30.293 .. writing Yogg-Saron
try 12 (sws-yoggsaron-1242363510) .. done.
./stasis: Encounter start: yoggsaron at 5/14 22:18:24.254 .. writing Yogg-Saron
try 13 (sws-yoggsaron-1242364704) .. done.
./stasis: Encounter start: yoggsaron at 5/14 22:38:35.621 .. writing Yogg-Saron
try 14 (sws-yoggsaron-1242365915) .. done.
./stasis: Encounter start: yoggsaron at 5/14 22:45:37.731 .. writing Yogg-Saron
try 15 (sws-yoggsaron-1242366337) .. done.
./stasis: Encounter start: yoggsaron at 5/14 22:58:16.195 .. writing Yogg-Saron
try 16 (sws-yoggsaron-1242367096) .. done.
./stasis: Done processing. Found 30 players, 2759 pets, and 16 boss encounters.
The second one (wowlog.txt) seemed to work fine through 4 yogg attempts, a
kill, then some sartharion and emalon. It wrote parses successfully for those.
Then, it ran into a bunch of mangled lines like:
5/21 22:38:22.075 SPELL_D5/21 22:38:23.734
SPELL_PERIODIC_DAMAGE,0x0200000001634D52,"Komui",0x514,0xF1300070BB000006,"Malyg
os",0xa48,48672,"Rupture",0x1,819,0,1,0,0,0,nil,nil,nil
Note "SPELL_D5/21". It looks like one line got cut off and attached to the
next. I don't know why these lines are there, but they appear in the original
text file and are definitely not normal. Even so, it managed to
write out 8 parses before running into those and getting confused.
I don't know why you see zero bosses instead of what I see when I run your
logs. Can you copy and paste the command you're running for these as well as
its full output? Also, the output of "/usr/bin/perl -V".
Original comment by gianmerlino@gmail.com
on 24 May 2009 at 5:17
I run
./stasis add -dir /Users/Hunk/Desktop/FAwws/5_19ulduar -ver 2 -attempt -file
/Users/Hunk/Desktop/FAwws/WoWCombatLog.txt
Here is the output of the /usr/bin/perl -V
acPro:volumes Hunk$ /usr/bin/perl -V
Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
Platform:
osname=darwin, osvers=9.0, archname=darwin-thread-multi-2level
uname='darwin b02.apple.com 9.0 darwin kernel version 9.3.0: tue aug 12 17:18:07 pdt 2008; root:xnu-
1228.5.90~13release_i386 i386 '
config_args='-ds -e -Dprefix=/usr -Dccflags=-g -pipe -Dldflags= -Dman3ext=3pm -Duseithreads -
Duseshrplib'
hint=recommended, useposix=true, d_sigaction=define
usethreads=define use5005threads=undef useithreads=define usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=define use64bitall=define uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='cc', ccflags ='-arch ppc -arch i386 -g -pipe -fno-common -DPERL_DARWIN -no-cpp-precomp -fno-
strict-aliasing -Wdeclaration-after-statement -I/usr/local/include',
optimize='-O3',
cppflags='-no-cpp-precomp -arch ppc -g -pipe -fno-common -DPERL_DARWIN -no-cpp-precomp -
fno-strict-aliasing -Wdeclaration-after-statement -I/usr/local/include'
ccversion='', gccversion='4.0.1 (Apple Inc. build 5465)', gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='cc -mmacosx-version-min=10.5.7', ldflags ='-arch ppc -arch i386 -L/usr/local/lib'
libpth=/usr/local/lib /usr/lib
libs=-ldbm -ldl -lm -lutil -lc
perllibs=-ldl -lm -lutil -lc
libc=/usr/lib/libc.dylib, so=dylib, useshrplib=true, libperl=libperl.dylib
gnulibc_version=''
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=bundle, d_dlsymun=undef, ccdlflags=' '
cccdlflags=' ', lddlflags='-arch ppc -arch i386 -bundle -undefined dynamic_lookup -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY PERL_IMPLICIT_CONTEXT
PERL_MALLOC_WRAP USE_ITHREADS USE_LARGE_FILES
USE_PERLIO USE_REENTRANT_API
Locally applied patches:
fix for regcomp CVE-2007-5116 security vulnerability
fix for double-free CVE-2008-1927 security vulnerability
/Library/Perl/Updates/<version> comes before system perl directories
installprivlib and installarchlib points to the Updates directory
Built under darwin
Compiled at Mar 11 2009 16:09:08
@INC:
/Library/Perl/Updates/5.8.8
/System/Library/Perl/5.8.8/darwin-thread-multi-2level
/System/Library/Perl/5.8.8
/Library/Perl/5.8.8/darwin-thread-multi-2level
/Library/Perl/5.8.8
/Library/Perl
/Network/Library/Perl/5.8.8/darwin-thread-multi-2level
/Network/Library/Perl/5.8.8
/Network/Library/Perl
/System/Library/Perl/Extras/5.8.8/darwin-thread-multi-2level
/System/Library/Perl/Extras/5.8.8
/Library/Perl/5.8.6
/Library/Perl/5.8.1/darwin-thread-multi-2level
/Library/Perl/5.8.1
.
MacPro:volumes Hunk$
Original comment by 19vett...@gmail.com
on 24 May 2009 at 6:00
Ignore the Maly errors, I was 2 boxing and i run 1 game and a dupe of the .app,
not a second folder, so i had 2
apps writing to the same combat log......never works out well
Original comment by 19vett...@gmail.com
on 24 May 2009 at 6:01
OK, I renamed my stasis folder, and started with "svn checkout
http://stasiscl.googlecode.com/svn/trunk/
stasiscl" all over again. It downloaded 259 (Which I don't think has
anything to do with parsing, but it
worked fine.
I had been using that to update my directory since 240ish rev, dunno if it
missed one or not, but it didn't
work until I remade a new folder and downloaded the whole SVN. It might be
something on my end, but
using a mac.....prolly not...but weirder things have happened :)
Thanks for your time and patience, you have a fantastic product.
Original comment by 19vett...@gmail.com
on 24 May 2009 at 6:08
I don't know why you see zero bosses instead of what I see when I run your
logs. Can you copy and paste the
command you're running for these as well as its full output? Also, the output
of "/usr/bin/perl -V".
That is what was so weird, I cut out alot of crap in the logs i uploaded, but
it would parse the entire night...5-6
bosses and there was NEVER even a mention in the window of Yogg, it was like it
just flat out skipped that part
of the log, but the other 5-6 bosses came out perfect.....
Original comment by 19vett...@gmail.com
on 24 May 2009 at 6:10
Original issue reported on code.google.com by
19vett...@gmail.com
on 15 May 2009 at 10:24