Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] strange tycho errors 
With all due respect, I do not believe maven.eclipse.org in its current
state should be forced as mirrorOf=external:* on all projects running at
hudson.eclipse.org. Either it should become an opt-it service for
projects that want it or it should be managed (and understood) by
Eclipse webmasters. As it stands now, I would't recommend use of
hudson.eclipse.org for projects that use maven.

--
Regards,
Igor

On 11-12-13 11:08 AM, Alex Blewitt wrote:

There was a random upstream proxy repository added to the 'public' group which had corrupt data. I've removed that from the list and now it doesn't appear to be serving bad data.

Alex

On 13 Dec 2011, at 14:28, Igor Fedorenko wrote:


Alex,

What other proof do you need beyond information captured in

https://bugs.eclipse.org/bugs/show_bug.cgi?id=365727

?

--
Regards,
Igor

On 11-12-13 7:40 AM, Alex Blewitt wrote:

Do we have any proof that the maven.eclipse.org contains corrupt files,
or is that just a supposition?

Alex

On Dec 13, 2011, at 10:34, Matthias Sohn wrote:


I think I found the reason for these failures:

- we have a reference to
http://maven.eclipse.org/nexus/content/groups/public/ in order to be
able to use
the maven eclipse signing plugin
- this probably causes also other artifacts to be downloaded from
maven.eclipse.org<http://maven.eclipse.org>, if some of
them are corrupt this can cause any kind of ugly build errors.
- is there a way to tell maven that we only want to download the
signing plugin from maven.eclipse.org<http://maven.eclipse.org>
and all others from central ?

--
Matthias

2011/12/13 Matthias Sohn<matthias.sohn@xxxxxxxxxxxxxx
<mailto:matthias.sohn@xxxxxxxxxxxxxx>>

    No, I can't reproduce this locally. I think the similar failure I
    observed in a local build
    yesterday was caused by missing proxy configuration. I ran the
    same build sequence again
    today with proper proxy configuration and the build succeeded.

    So it looks like there is a severe problem on hudson.eclipse.org
    <http://hudson.eclipse.org>. If build jobs are forced
    to use maven.eclipse.org<http://maven.eclipse.org>  via centrally
    configured settings.xml (don't know if that's the case)
    and if maven.eclipse.org<http://maven.eclipse.org>  contains
    corrupt artifacts this will create random build errors like the
    ones we hit.

    The two failing builds both run on sandbox hudson.

    --
    Matthias


    2011/12/13 Igor Fedorenko<igor@xxxxxxxxxxxxxx
    <mailto:igor@xxxxxxxxxxxxxx>>

        Are you able to reproduce this problem outside of
        hudson.eclipse.org<http://hudson.eclipse.org>?

        https://bugs.eclipse.org/bugs/__show_bug.cgi?id=365727
        <https://bugs.eclipse.org/bugs/show_bug.cgi?id=365727>

        --
        Regards,
        Igor


        On 11-12-12 6:03 PM, Matthias Sohn wrote:

            The egit [1] and egit-github [2] gerrit-trigger build jobs
            used to verify
            changes uploaded for code review experience some strange
            errors
            since a couple of days.

            [1] reproducably hits a NPE (using tycho 0.12)

            [ERROR] Failed to execute goal
            org.eclipse.tycho:tycho-p2-__plugin:0.12.0:update-site-p2-__metadata
            (default-update-site-p2-__metadata) on project
            org.eclipse.egit-updatesite: Cannot generate P2 metadata:
            java.lang.NullPointerException ->  [Help 1]
            org.apache.maven.lifecycle.__LifecycleExecutionException:
            Failed to execute goal
            org.eclipse.tycho:tycho-p2-__plugin:0.12.0:update-site-p2-__metadata
            (default-update-site-p2-__metadata) on project
            org.eclipse.egit-updatesite: Cannot generate P2 metadata
            at
            org.apache.maven.lifecycle.__internal.MojoExecutor.execute(__MojoExecutor.java:217)
            at
            org.apache.maven.lifecycle.__internal.MojoExecutor.execute(__MojoExecutor.java:153)
            at
            org.apache.maven.lifecycle.__internal.MojoExecutor.execute(__MojoExecutor.java:145)
            at
            org.apache.maven.lifecycle.__internal.__LifecycleModuleBuilder.__buildProject(__LifecycleModuleBuilder.java:__84)
            at
            org.apache.maven.lifecycle.__internal.__LifecycleModuleBuilder.__buildProject(__LifecycleModuleBuilder.java:__59)
            at
            org.apache.maven.lifecycle.__internal.LifecycleStarter.__singleThreadedBuild(__LifecycleStarter.java:183)
            at
            org.apache.maven.lifecycle.__internal.LifecycleStarter.__execute(LifecycleStarter.java:__161)
            at
            org.apache.maven.DefaultMaven.__doExecute(DefaultMaven.java:__319)
            at
            org.apache.maven.DefaultMaven.__execute(DefaultMaven.java:156)
            at org.apache.maven.cli.MavenCli.__execute(MavenCli.java:537)
            at org.apache.maven.cli.MavenCli.__doMain(MavenCli.java:196)
            at org.apache.maven.cli.MavenCli.__main(MavenCli.java:141)
            at sun.reflect.__NativeMethodAccessorImpl.__invoke0(Native
            Method)
            at
            sun.reflect.__NativeMethodAccessorImpl.__invoke(__NativeMethodAccessorImpl.java:__39)
            at
            sun.reflect.__DelegatingMethodAccessorImpl.__invoke(__DelegatingMethodAccessorImpl.__java:25)
            at java.lang.reflect.Method.__invoke(Method.java:597)
            at
            org.codehaus.plexus.__classworlds.launcher.Launcher.__launchEnhanced(Launcher.java:__290)
            at
            org.codehaus.plexus.__classworlds.launcher.Launcher.__launch(Launcher.java:230)
            at
            org.codehaus.plexus.__classworlds.launcher.Launcher.__mainWithExitCode(Launcher.__java:409)
            at
            org.codehaus.plexus.__classworlds.launcher.Launcher.__main(Launcher.java:352)
            Caused by:
            org.apache.maven.plugin.__MojoExecutionException: Cannot
            generate P2 metadata
            at
            org.eclipse.tycho.plugins.p2.__AbstractP2MetadataMojo.__execute(__AbstractP2MetadataMojo.java:__95)
            at
            org.apache.maven.plugin.__DefaultBuildPluginManager.__executeMojo(__DefaultBuildPluginManager.__java:101)
            at
            org.apache.maven.lifecycle.__internal.MojoExecutor.execute(__MojoExecutor.java:209)
            ... 19 more
            Caused by: java.lang.RuntimeException:
            java.lang.NullPointerException
            at
            org.eclipse.tycho.p2.facade.__internal.__P2ApplicationLauncher.execute(__P2ApplicationLauncher.java:__127)
            at
            org.eclipse.tycho.plugins.p2.__AbstractP2MetadataMojo.__generateMetadata(__AbstractP2MetadataMojo.java:__112)
            at
            org.eclipse.tycho.plugins.p2.__AbstractP2MetadataMojo.__execute(__AbstractP2MetadataMojo.java:__88)
            ... 21 more
            Caused by: java.lang.NullPointerException
            at
            org.eclipse.tycho.core.__osgitools.DefaultBundleReader.__toProperties(__DefaultBundleReader.java:162)
            at
            org.eclipse.tycho.core.__osgitools.DefaultBundleReader.__parseHeader(__DefaultBundleReader.java:173)
            at
            org.eclipse.tycho.core.__osgitools.OsgiBundleProject.__readArtifactKey(__OsgiBundleProject.java:130)
            at
            org.eclipse.tycho.p2.facade.__internal.__P2ApplicationLauncher.__addBundle(__P2ApplicationLauncher.java:__132)
            at
            org.eclipse.tycho.p2.facade.__internal.__P2ApplicationLauncher.execute(__P2ApplicationLauncher.java:99)
            ... 23 more


            [2] (using tycho 0.13) seems to fail to download some of
            the tycho
            plugins and then fails with a ClassNotFoundException

            Wiping the workspace to remove the job private maven repo
            doesn't seem
            to help in both cases.
            I tried this many times, also Jan Sievers looked into
            these failing jobs
            and we are running out
            of ideas what could be the cause of these.build errors.
            Today I also saw
            the second issue when
            running the egit-github build locally. Again wiping the
            local maven
            repository didn't resolve the
            issue. What helped was to remove the tycho plugins from
            the local maven
            repository and then
            rerunning the build, wiping the complete Maven repository
            didn't help.

            [1] https://hudson.eclipse.org/__sandbox/job/egit.gerrit/
            <https://hudson.eclipse.org/sandbox/job/egit.gerrit/>
            [2]
            https://hudson.eclipse.org/__sandbox/job/egit-github.__gerrit/
            <https://hudson.eclipse.org/sandbox/job/egit-github.gerrit/>

            --
            Matthias


            _________________________________________________
            tycho-user mailing list
            tycho-user@xxxxxxxxxxx<mailto:tycho-user@xxxxxxxxxxx>
            https://dev.eclipse.org/__mailman/listinfo/tycho-user
            <https://dev.eclipse.org/mailman/listinfo/tycho-user>

        _________________________________________________
        tycho-user mailing list
        tycho-user@xxxxxxxxxxx<mailto:tycho-user@xxxxxxxxxxx>
        https://dev.eclipse.org/__mailman/listinfo/tycho-user
        <https://dev.eclipse.org/mailman/listinfo/tycho-user>


_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx<mailto:tycho-user@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/tycho-user




_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user


_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user

Back to the top