On 2011-07-30 10:54, Mark Struberg wrote:
> Might be if the metadata got downloaded but the artifact (a fat jar for 
> example) didn't make it? 
> 
> I bet there are situations where such things still might end ugly. 
> 
> Just for the record: I'm currently looking at maven-repository-plugin 
> BundleCreateIT#createWithSCMInfoProvided().
> It looks like this issue only hits ITs.
> 
> Here is the local IT repo on our CI box:
> https://builds.apache.org/job/maven-plugins-ITs-3.x/ws/maven-repository-plugin/target/it-repo/
> 
> A comparison of the artifacts I get locally shows that commons-cli-1.0 and 
> commons-lang-2.1 don't make it on the CI box.
> 
> 
> I'll try to ping infra and get drop them from our jenkins repo cache.

That should be directed to builds@a.o
I'm a recent subscriber there, so I can ask them.

> 
> LieGrue,
> strub
> 
> 
> --- On Sat, 7/30/11, Dennis Lundberg <denn...@apache.org> wrote:
> 
>> From: Dennis Lundberg <denn...@apache.org>
>> Subject: Re: non-reproducible issues on CI
>> To: "Maven Developers List" <dev@maven.apache.org>
>> Date: Saturday, July 30, 2011, 8:31 AM
>> Hi
>>
>> I've seen this kind of error at my day job a couple of
>> times. Although
>> I'm sure sure why they happen, I do know how to get rid of
>> it.
>>
>> You need to manually remove the offending artifact from the
>> local repo
>> to get a freshly downloaded copy of it. By removing all
>> versions of the
>> artifact, including the meta data you ensure that the
>> "corrupt" meta
>> data will also be removed.
>>
>> The only reason I can think of as to why it happens is that
>> the
>> repository don't respond when the artifact is being
>> downloaded for the
>> first time. That puts some special meta data in the local
>> repository.
>> That meta data looks like it is supposed to help determine
>> when the
>> failed attempt occurred. This somehow blocks any further
>> download of the
>> artifact in question. Even forcing a new download via
>> command line
>> option have failed for us.
>>
>> I haven't reported it in JIRA yet because I don't have
>> anything even
>> remotely reproducible.
>>
>> On 2011-07-30 01:22, Mark Struberg wrote:
>>> Hi!
>>>
>>> Our CI is broken since a while and most of the errors
>> are of the following kind:
>>>
>>>
>>> [ERROR] Plugin
>> org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT
>> or one of its dependencies could not be resolved: Failed to
>> read artifact descriptor for
>> org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT:
>> Failure to find
>> org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT
>> in
>> /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo
>> was cached in the local repository, resolution will not be
>> reattempted until the update interval of local.central has
>> elapsed or updates are forced -> [Help 1]
>>> org.apache.maven.plugin.PluginResolutionException:
>> Plugin
>> org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT
>> or one of its dependencies could not be resolved: Failed to
>> read artifact descriptor for
>> org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT
>>>     at
>> org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129)
>>>     at
>> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142)
>>>     at
>> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261)
>>>     at
>> org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185)
>>>     at
>> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235)
>>>     at
>> org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106)
>>>     at
>> org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86)
>>>     at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98)
>>>     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:592)
>>>     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.sonatype.aether.resolution.ArtifactDescriptorException:
>> Failed to read artifact descriptor for
>> org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT
>>>     at
>> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:282)
>>>     at
>> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:172)
>>>     at
>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:316)
>>>     at
>> org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115)
>>>     ... 20 more
>>> Caused by:
>> org.sonatype.aether.resolution.ArtifactResolutionException:
>> Failure to find
>> org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT
>> in
>> /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo
>> was cached in the local repository, resolution will not be
>> reattempted until the update interval of local.central has
>> elapsed or updates are forced
>>>     at
>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:541)
>>>     at
>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:220)
>>>     at
>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:197)
>>>     at
>> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:267)
>>>     ... 23 more
>>> Caused by:
>> org.sonatype.aether.transfer.ArtifactNotFoundException:
>> Failure to find
>> org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT
>> in
>> /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo
>> was cached in the local repository, resolution will not be
>> reattempted until the update interval of local.central has
>> elapsed or updates are forced
>>>     at
>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:190)
>>>     at
>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:430)
>>>     ... 26 more
>>>
>>>
>>> Here is the full story:
>>>
>>> https://builds.apache.org/job/maven-plugins-ITs-3.x/ws/maven-repository-plugin/target/surefire-reports/org.apache.maven.plugins.repository.it.BundleCreateIT.txt
>>>
>>> The weird thing is that this artifact exists:
>>> https://builds.apache.org/job/maven-plugins-ITs-3.x/ws/maven-repository-plugin/target/it-repo/org/apache/maven/plugins/maven-repository-plugin/2.3.2-SNAPSHOT/
>>>
>>>
>>> We (rfscholte nor I) cannot reproduce those bugs
>> locally. All the tests just run fine here. 
>>> Is there some magic switch we need to set in Jenkins,
>> or is this a real bug?
>>>
>>> txs and LieGrue,
>>> strub
>>>
>>>
>>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to