Re: [dash-dev] Weird build failures.. (test?)

[David Carver <d_a_carver@xxxxxxxxx>]

I actually tried this with Athena, and put it in my testing.properties 
file.  However, when I check the log file where I would expect to see 
the extraVMFlag arguements set, I don't see it in the log file when it 
goes to launch eclipse headless for the unit tests (i.e. runtests).

In particular my use case is I want to set some specific System 
properties for running eclEmma headless, was hoping I could use 
extraVMFlag property setting to do it. 

Another related note, it seems that Athena expects a ZIP to contain the 
eclipse/plugins directory structure.   Unfortunately, eclemma headless 
runner's structure is only: plugins

So it doesn't seem that when it is dropped into the dropins folder it 
will be picked up.

One way I could work around it is to extract and re-package but it would 
be nice if we could handle the other format as well.  Or is there an app 
for that? :)

Dave


Nick Boldt wrote:
> In another thread this solution was reported. Perhaps it's related?
>
> > Some projects have tests failing during the build because of changes 
> > done on the server recently.
> > For example:
> > * xText
> > * MDT OCL
> > * EMFT MWE
> > A solution was proposed in bug 295394:
> > add the following line to testing.properties in your releng project:
> > extraVMargs=-Dorg.eclipse.swt.browser.XULRunnerPath=/shared/common/mozilla-xulrunner181-1.8.1.4-30.ppc 
>
> BTW, huge thanks to Nicolas Bros for pitching in here with not just 
> questions, but *ANSWERS*!
>
> I've added the above tip to the FAQ. If you have other tips (which 
> can't be solved w/ a bug+patch) feel free to add them to the FAQ.
>
> http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/FAQ#My_build_used_to_work_but_now_headless_UI_tests_are_broken.21 
>
>
> Nick
>
> Miles Parker wrote:
> > Yeah, I did and I got the same thing. The font thing was an earlier 
> > remark I forgot to take out. The diff made it pretty obvious that the 
> > below was the hanging spot. I'm going to pull the Plugin JUnit test 
> > portion and see if that fixes it.
> >
> > cheers,
> >
> > Miles
> >
> >
> > On Nov 17, 2009, at 11:51 PM, David Carver wrote:
> >
> > > Don't know why P2 would be giving you some errors.  There are always 
> > > messages about X not being able to find some Fonts so I don't think 
> > > that has anything to do with it.   I know that the web masters 
> > > recently rebooted the build server today, so not sure if you might 
> > > be running into the following bug:
> > >
> > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=295394
> > >
> > > But don't see how that bug would affect P2.
> > >
> > > Out of curiosity have you tried just re-running again, or does it 
> > > just die at the same spot in the build?
> > >
> > > Dave
> > >
> > >
> > > Miles Parker wrote:
> > > > Hi all,
> > > >
> > > > I've just had a really perplexing error show up on my nightly 
> > > > build. I haven't changes anything that should affect the tests -- 
> > > > in fact the changes form last succesful are pretty minimal -- but 
> > > > there seems to be some kind of failure there -- something to do 
> > > > with fonts!?  -- even though at the end of the log I get a success 
> > > > reported. Any ideas what might be going on here?
> > > >
> > > >
> > > > This seems to be where the trouble is.. an NPE in p2..
> > > >
> > > >     [exec]    [p2.dir] !SESSION 2009-11-16 22:22:40.816 
> > > > -----------------------------------------------
> > > >     [exec]    [p2.dir] eclipse.buildId=M20090917-0800
> > > >     [exec]    [p2.dir] java.fullversion=J2RE 1.5.0 IBM J9 2.3 Linux 
> > > > ppc-32 j9vmxp3223-20071007 (JIT enabled)
> > > >     [exec]    [p2.dir] J9VM - 20071004_14218_bHdSMR
> > > >     [exec]    [p2.dir] JIT  - 20070820_1846ifx1_r8
> > > >     [exec]    [p2.dir] GC   - 200708_10
> > > >     [exec]    [p2.dir] BootLoader constants: OS=linux, ARCH=ppc, 
> > > > WS=gtk, NL=en_US
> > > >     [exec]    [p2.dir] Framework arguments:  -application 
> > > > org.eclipse.equinox.p2.director.app.application -flavor tooling 
> > > > -roaming -profile SDKProfile -installIU 
> > > > org.eclipse.amp.all.feature.group -destination 
> > > > /opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/target/eclipse 
> > > > -bundlepool 
> > > > /opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/target/eclipse 
> > > > -metadataRepository 
> > > > file:/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/p2dirTmp/eclipse,file:/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/target/eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/SDKProfile.profile 
> > > > -artifactRepository 
> > > > file:/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/p2dirTmp/eclipse,file:/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/target/eclipse 
> > > > -profileProperties org.eclipse.update.install.features=true
> > > >     [exec]    [p2.dir] Command-line arguments:  -os linux -ws gtk 
> > > > -arch ppc -application 
> > > > org.eclipse.equinox.p2.director.app.application -consoleLog -flavor 
> > > > tooling -roaming -profile SDKProfile -installIU 
> > > > org.eclipse.amp.all.feature.group -destination 
> > > > /opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/target/eclipse 
> > > > -bundlepool 
> > > > /opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/target/eclipse 
> > > > -metadataRepository 
> > > > file:/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/p2dirTmp/eclipse,file:/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/target/eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/SDKProfile.profile 
> > > > -artifactRepository 
> > > > file:/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/p2dirTmp/eclipse,file:/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/N200911162210/testing/target/eclipse 
> > > > -profileProperties org.eclipse.update.install.features=true
> > > >     [exec]    [p2.dir]      [exec]    [p2.dir] !ENTRY 
> > > > org.eclipse.core.jobs 4 2 2009-11-16 22:25:11.628
> > > >     [exec]    [p2.dir] !MESSAGE An internal error occurred during: 
> > > > "Saving profile preferences".
> > > >     [exec]    [p2.dir] !STACK 0
> > > >     [exec]    [p2.dir] java.lang.NullPointerException
> > > >     [exec]    [p2.dir] at 
> > > > org.eclipse.equinox.internal.p2.engine.ProfilePreferences.getProfileLocation(ProfilePreferences.java:155) 
> > > >
> > > >     [exec]    [p2.dir] at 
> > > > org.eclipse.equinox.internal.p2.engine.ProfilePreferences.doSave(ProfilePreferences.java:117) 
> > > >
> > > >     [exec]    [p2.dir] at 
> > > > org.eclipse.equinox.internal.p2.engine.ProfilePreferences$SaveJob.run(ProfilePreferences.java:45) 
> > > >
> > > >     [exec]    [p2.dir] at 
> > > > org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> > > >
> > > >
> > > > cheers,
> > > >
> > > > Miles
> > > > ------------------------------------------------------------------------ 
> > > >
> > > >
> > > > _______________________________________________
> > > > dash-dev mailing list
> > > > dash-dev@xxxxxxxxxxx
> > > > https://dev.eclipse.org/mailman/listinfo/dash-dev
> > >
> > > _______________________________________________
> > > dash-dev mailing list
> > > dash-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/dash-dev
> >
> > _______________________________________________
> > dash-dev mailing list
> > dash-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/dash-dev