Additional tweaks...
* There's a difference in File.flock behavior between Java 5 and later
versions. Specifically, on later versions you have to have the file
open in specific modes (read/write) to be able to do shared and
exclusive locks. There's a guard in RubySpec for this behavior, which
is e
Man, is this ever a painful job.
I've spent most of the day trying to get CI builds green again, and
the server has been working against me.
Most of the major builds were red...the spec builds, test-all, dist,
and I think jruby-base as well. In the process of fixing one build I
uncovered regressi
I should point out that everyone "jruby-core" has commit rights to
jruby/rubyspec, and as with rubyspec/rubyspec I'm fine opening it up
for commit access if you have access to rubyspec/rubyspec or submit a
"first patch".
Fire away.
- Charlie
On Mon, Dec 5, 2011 at 11:12 PM, Subramanya Sastry wr
Awesome! -Subbu.
On Tue, Dec 6, 2011 at 7:44 AM, Charles Oliver Nutter
wrote:
> In order to make it a bit easier and less daunting to contribute to
> RubySpec, I'm proposing (and have mostly already made) a minor change
> in our process.
>
> * Instead of pulling directly from github.com/rubyspe
very nice, this really helps people like me who have problems finding
the right places all the time ;)
- Kristian
On Tue, Dec 6, 2011 at 7:44 AM, Charles Oliver Nutter
wrote:
> In order to make it a bit easier and less daunting to contribute to
> RubySpec, I'm proposing (and have mostly already
I've added a new build to CI, jruby-test-all-release, which will
nightly run "test-all" against whatever is the current release branch
(currently jruby-1_6). A few bugs have snuck through lately that would
have been caught by test-all, so it makes sense for us to start
running test-all in CI agains
In order to make it a bit easier and less daunting to contribute to
RubySpec, I'm proposing (and have mostly already made) a minor change
in our process.
* Instead of pulling directly from github.com/rubyspec/rubyspec we
will pull from a forked copy at github.com/jruby/rubyspec.
* Developers may
When executing an Ant build.xml file, the Ant executable should not be required
to live on the environment's $PATH
--
Key: JRUBY-6250
URL: https://jira
Creating binary for jffi
Key: JRUBY-6249
URL: https://jira.codehaus.org/browse/JRUBY-6249
Project: JRuby
Issue Type: Task
Affects Versions: JRuby 1.6.5
Environment: Suse Linux SLES 11-SP2 on s390x archit
thread leak with puts
-
Key: JRUBY-6248
URL: https://jira.codehaus.org/browse/JRUBY-6248
Project: JRuby
Issue Type: Bug
Environment: jruby 1.7.0.dev (ruby-1.8.7-p330) (2011-11-16 b7c3cc2)
(Java HotSpot(TM) Clien
10 matches
Mail list logo
