-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Marshal data too short accessing mavengems #107
Comments
cc @mkristian I am trying to investigate myself but I could use some help. |
I have patched around it by not using plugins to install rspec in the JRuby |
Something chaned on rubygems.org that's causing the mavengem plugin to produce "marshal data too short" errors. While we investigate, remove rspec from -Pbootstrap mavengems and instead use bundler to install it in CI. See jruby/jruby-maven-plugins#107
Something changed on rubygems.org that's causing the mavengem plugin to produce "marshal data too short" errors. While we investigate, remove rspec from -Pbootstrap mavengems and instead use bundler to install it in CI. See jruby/jruby-maven-plugins#107
cc @abelsromero This is the issue I mentioned on JRuby Matrix. |
Could not reproduce with clean .m2/repository. I cloned the jruby repo, run
|
I patched around it so you may have to go back a few revisions. |
I fear I am missing something, I did not run the jruby build against the snapshot of the plugin. Just run as-is from the repo and no error occured. |
This seems fixed in recent versions, I would close it for now! |
This seems to be a recent issue, possibly related to some unknown update to rubygems.org:
This happens during JRuby's build using
mvn package -Pbootstrap
which downloads and installs additional gems for local development purposes.The URL in question is clearly not something that rubygems.org supports, and produces a page with the only content as "404 Not Found" when accessed.
Perhaps this page's content is being used as the pom? Or used as some RubyGems data that it tries to marshal and fails?
This is preventing all JRuby CI builds from working. I wiped out my local
.m2/repository
and could reproduce locally as well.The text was updated successfully, but these errors were encountered: