I found the note at the bottom of the readme about the compiler.tests/template-unittest.properties file. I had previously tried adding a unittest.properties to define the environment variables, but I guess I didn't get the details right at the time. Or maybe I didn't put it in the right directory.
With the template, I knew exactly what properties to define. Then, I correctly guessed that I need to put a copy of unittest.properties in both compiler.tests and compiler.jx.tests. This part is not clear in the readme, so maybe it should be updated. - Josh On Tue, Jan 12, 2016 at 11:39 PM, Alex Harui <aha...@adobe.com> wrote: > Sounds good. What did you have to do to get the unit tests to run? It > might help the next person who tries. > > Thanks, > -Alex > > On 1/12/16, 11:36 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: > > >Before today, I could never get the unit tests to run on my local machine. > >However, now, I can do a full build of both flex-falcon and flex-asjs > >locally, so a broken build shouldn't happen as easily next time I need to > >work on the compiler. > > > >- Josh > > > >On Tue, Jan 12, 2016 at 10:35 PM, Alex Harui <aha...@adobe.com> wrote: > > > >> > >> > >> On 1/12/16, 10:29 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: > >> > >> >Good! Sorry for the trouble! > >> > >> Well, if you looked closely, you'd see I made a change that broke the > >> build as well ;-) So I don't expect anyone to go forever without > >>breaking > >> a build. > >> > >> I try to always run "ant all" from the root of the flex-falcon repo > >>before > >> pushing changes. It should only take a few minutes. However, for some > >> reason, my last commit required an "ant wipe-all" before "ant all" in > >> order to see it break. Not sure why. The CI server does do an "ant > >> wipe-all", but most of the time that doesn't make a difference and saves > >> me a few more minutes. > >> > >> -Alex > >> > >> > >
