Thanks for testing! Edison just told me it's because devCloud is not clean up. So on his deploy it works when it's the first run. Second run he sees the problems. He's working on it.
--Alex > -----Original Message----- > From: Chip Childers [mailto:[email protected]] > Sent: Friday, October 05, 2012 3:47 PM > To: Alex Huang > Cc: [email protected] > Subject: Re: bugs 259 and 260 > > Edison mentioned on IRC that he thought he knew the issue. I didn't get the > details. > > I've tried clearing my local maven cache, cutting a new release from HEAD of > 4.0, and various other things. The issue happens every time. > > - chip > > Sent from my iPhone. > > On Oct 5, 2012, at 6:24 PM, Alex Huang <[email protected]> wrote: > > > Chip, > > > > Any luck with testing these two bugs? Thanks. > > > > --Alex > > > >> -----Original Message----- > >> From: Alex Huang [mailto:[email protected]] > >> Sent: Friday, October 05, 2012 9:51 AM > >> To: [email protected] > >> Cc: Chip Childers ([email protected]) > >> Subject: bugs 259 and 260 > >> > >> Chip, > >> > >> I talked to Edison about this yesterday and he said that you guys > >> talked yesterday and you needed to download a new devCoud image to > >> perform the test procedure instead of using the old one? That's what > >> I meant by using the new devCloud image. > >> > >> Kelven's tested from his mac and says other than the default memory > >> for devcloud image was too small, he didn't see any problems. > >> > >> What type of configuration are your running on? Is it mac, windows, linux? > >> Did you download another devcloud image or used an existing one? > >> Edison is not here right now so I need more input from you on the bug. > >> > >> Thanks. > >> > >> --Alex > >
