Forum: Ruby-core 1.9.3 patch level release

Posted by Zachary Scott (Guest)
on 2012-12-20 16:43
(Received via mailing list)
I know unak-san was asking about a 1.9.3 patch level release, so I
wanted to bring it up for discussion.
Posted by Luis Lavena (luislavena)
on 2012-12-20 20:03
(Received via mailing list)
On Thu, Dec 20, 2012 at 12:43 PM, Zachary Scott
<zachary@zacharyscott.net> wrote:
> I know unak-san was asking about a 1.9.3 patch level release, so I
> wanted to bring it up for discussion.
>

I would love a release, but since latest merges I see one failure
happening on Windows:

http://ci.rubyinstaller.org/job/ruby-1_9_3-x64-tes...
http://ci.rubyinstaller.org/job/ruby-1_9_3-x86-tes...

  1) Error:
test_chars(TestArgf):
ArgumentError: dump format error(0x67)
    C:/Users/Worker/Jenkins/workspace/ruby-1_9_3-x64-build/test/ruby/test_argf.rb:772:in
`load'
    C:/Users/Worker/Jenkins/workspace/ruby-1_9_3-x64-build/test/ruby/test_argf.rb:772:in
`block in test_chars'
    C:/Users/Worker/Jenkins/workspace/ruby-1_9_3-x64-build/test/ruby/test_argf.rb:49:in
`ruby'
    C:/Users/Worker/Jenkins/workspace/ruby-1_9_3-x64-build/test/ruby/test_argf.rb:769:in
`test_chars'

This seems to be new and wasn't happening before.

To my bad, I don't have time to dig into this until next week :(
Posted by Heesob Park (phasis)
on 2012-12-21 04:51
(Received via mailing list)
Hi,

2012/12/21 Luis Lavena <luislavena@gmail.com>:
> http://ci.rubyinstaller.org/job/ruby-1_9_3-x86-tes...
> 
C:/Users/Worker/Jenkins/workspace/ruby-1_9_3-x64-build/test/ruby/test_argf.rb:769:in
> `test_chars'
>
> This seems to be new and wasn't happening before.
>
> To my bad, I don't have time to dig into this until next week :(

In order to fix this error, the change set
r37862(https://bugs.ruby-lang.org/projects/ruby-trunk/rep...)
should be backported.

Regards,

Park Heesob
Posted by U.Nakamura (Guest)
on 2012-12-21 08:05
(Received via mailing list)
Hello,

Thank you all, I've backported it now.


In message "[ruby-core:51021] Re: 1.9.3 patch level release"
    on Dec.21,2012 12:51:16, <phasis@gmail.com> wrote:
> > happening on Windows:
> > `block in test_chars'
> 
r37862(https://bugs.ruby-lang.org/projects/ruby-trunk/rep...)
> should be backported.
>
> Regards,
>
> Park Heesob


Regards,
Posted by U.Nakamura (Guest)
on 2012-12-21 08:12
(Received via mailing list)
Hello,

In message "[ruby-core:51015] 1.9.3 patch level release"
    on Dec.21,2012 00:43:00, <zachary@zacharyscott.net> wrote:
> I know unak-san was asking about a 1.9.3 patch level release, so I
> wanted to bring it up for discussion.

Ah, It's confidential that Santa Claus is coming to us :)


Currently, RubyCI status is green about 1.9.3.
(OS X reports an error, but it's CI servers' problem.)
RubyInstaller CI reports an error, but it was fixed, I hope.

So, if any accident does not occur by somewhere, maybe something
will happen at Christmas.


Regards,
Posted by "Vít Ondruch" <v.ondruch@gmail.com> (Guest)
on 2012-12-21 08:35
(Received via mailing list)
Dne 21.12.2012 8:12, U.Nakamura napsal(a):
> (OS X reports an error, but it's CI servers' problem.)
> RubyInstaller CI reports an error, but it was fixed, I hope.
>
> So, if any accident does not occur by somewhere, maybe something
> will happen at Christmas.
>
>
> Regards,

If only https://bugs.ruby-lang.org/issues/6573 would be fixed there ....


V
Posted by Luis Lavena (luislavena)
on 2012-12-21 14:13
(Received via mailing list)
On Fri, Dec 21, 2012 at 4:34 AM, Vt Ondruch <v.ondruch@gmail.com> wrote:
>
> If only https://bugs.ruby-lang.org/issues/6573 would be fixed there ....
>

Vit, do you have a CI we can look at when working on fixes? Because is
really hard to keep track of every single failure on every single
platform.

The reason RubyInstaller CI was setup is that I was tired of running
and reporting tests a couple of times a week. Having those available
for everybody to see, and specially for committers to see if their
changes break something.
Posted by "Vít Ondruch" <v.ondruch@gmail.com> (Guest)
on 2012-12-21 14:44
(Received via mailing list)
2012/12/21 Luis Lavena <luislavena@gmail.com>

> and reporting tests a couple of times a week. Having those available
> for everybody to see, and specially for committers to see if their
> changes break something.
>


Yay, of course I would love to see CI running our builds and this would 
be
definitely the most annoying bug because of its randomness. 
Unfortunately
we are not there yet and there is no schedule to establish CI. But you
definitely prioritized CI on my TODO list :)

Vt
Please log in before posting. Registration is free and takes only a minute.
Existing account (Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
No account? Register here.