You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@trafficserver.apache.org by Leif Hedstrom <zw...@apache.org> on 2013/04/16 00:35:35 UTC
[VOTE] Release v3.3.2
Hi all,
I've prepared a release for v3.3.2, which has quite a few improvements and
bug fixes over 3.3.0. Please see the CHANGES for more details. It's
important we get as much testing as possible for these dev releases for the
next few months, in preparation for v3.4.0. There are several known bugs
already, which are (now) scheduled for v3.3.3, v3.3.4 and v3.3.5
accordingly. Help triaging, commenting and closing those bugs are also much
needed.
This is a community effort, so we need everyone to help out. Most important
is that the users of ATS helps with these efforts, and your votes are much
appreciated. PMC votes are of course also necessary to get this to pass.
The artifacts are available at http://people.apache.org/~zwoop/rel-candidates/:
-rw-r--r-- 1 zwoop zwoop 2782877 Apr 15 22:18 trafficserver-3.3.2-dev.tar.bz2
-rw-r--r-- 1 zwoop zwoop 836 Apr 15 22:18
trafficserver-3.3.2-dev.tar.bz2.asc
-rw-r--r-- 1 zwoop zwoop 66 Apr 15 22:18
trafficserver-3.3.2-dev.tar.bz2.md5
-rw-r--r-- 1 zwoop zwoop 74 Apr 15 22:18
trafficserver-3.3.2-dev.tar.bz2.sha1
MD5: dc736e78743bb7dd94f8980770b6856f
SHA1: a9463dbe12a0c42b2922df9d8d209c67118bc46f
The goal is to release this on April 18th, so please cast your +, - or 0
votes asap.
Cheers,
-- leif
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <zw...@apache.org>.
On 4/15/13 4:35 PM, Leif Hedstrom wrote:
> Hi all,
>
> I've prepared a release for v3.3.2, which has quite a few improvements and
> bug fixes over 3.3.0. Please see the CHANGES for more details. It's
> important we get as much testing as possible for these dev releases for
> the next few months, in preparation for v3.4.0. There are several known
> bugs already, which are (now) scheduled for v3.3.3, v3.3.4 and v3.3.5
> accordingly. Help triaging, commenting and closing those bugs are also
> much needed.
This vote passes with 9 +1 votes (8 binding) and 1 -1 vote. For the -1 vote,
we have fixed the issue with certain (older compilers), it's committed on
master in 5b44534f7bdc2338c23c5cf89ddf86d6de3ae829. I'm including the tiny
patch below as well. The v.3.3.2 release has been pushed to the dist server,
and I'll make an official announcement tomorrow.
Thanks to everyone for voting! v3.3.3 in a month, keep up the great work
towards v3.4.0 stable.
-- Leif
diff --git a/lib/records/RecUtils.cc b/lib/records/RecUtils.cc
index d04fce7..3680fee 100644
--- a/lib/records/RecUtils.cc
+++ b/lib/records/RecUtils.cc
@@ -76,7 +76,7 @@ RecDataSetMax(RecDataT type, RecData * data)
#endif
case RECD_INT:
case RECD_COUNTER:
- data->rec_int = 0x7fffffffffffffff;
+ data->rec_int = INT64_MAX; // Assumes rec_int is int64_t, which it currently is
break;
#if defined(STAT_PROCESSOR)
case RECD_CONST:
@@ -98,7 +98,7 @@ RecDataSetMin(RecDataT type, RecData * data)
#endif
case RECD_INT:
case RECD_COUNTER:
- data->rec_int = 0x8000000000000000;
+ data->rec_int = INT64_MIN; // Assumes rec_int is int64_t, which it currently is
break;
#if defined(STAT_PROCESSOR)
case RECD_CONST:
Re: [VOTE] Release v3.3.2
Posted by Daniel Gruno <ru...@cord.dk>.
+1 from here, tested on FreeBSD 9.1 - make, make check, make install, ts
-R and so on passed (surprise, surprise! I would've expected the SDK
checks to fail, as always ;) ).
With regards,
Daniel.
On 04/16/2013 12:35 AM, Leif Hedstrom wrote:
> Hi all,
>
> I've prepared a release for v3.3.2, which has quite a few improvements
> and bug fixes over 3.3.0. Please see the CHANGES for more details. It's
> important we get as much testing as possible for these dev releases for
> the next few months, in preparation for v3.4.0. There are several known
> bugs already, which are (now) scheduled for v3.3.3, v3.3.4 and v3.3.5
> accordingly. Help triaging, commenting and closing those bugs are also
> much needed.
>
> This is a community effort, so we need everyone to help out. Most
> important is that the users of ATS helps with these efforts, and your
> votes are much appreciated. PMC votes are of course also necessary to
> get this to pass.
>
>
> The artifacts are available at
> http://people.apache.org/~zwoop/rel-candidates/:
>
> -rw-r--r-- 1 zwoop zwoop 2782877 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2
> -rw-r--r-- 1 zwoop zwoop 836 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2.asc
> -rw-r--r-- 1 zwoop zwoop 66 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2.md5
> -rw-r--r-- 1 zwoop zwoop 74 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2.sha1
>
>
> MD5: dc736e78743bb7dd94f8980770b6856f
> SHA1: a9463dbe12a0c42b2922df9d8d209c67118bc46f
>
> The goal is to release this on April 18th, so please cast your +, - or 0
> votes asap.
>
> Cheers,
>
> -- leif
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <zw...@apache.org>.
On 4/15/13 4:35 PM, Leif Hedstrom wrote:
> Hi all,
>
> I've prepared a release for v3.3.2, which has quite a few improvements and
> bug fixes over 3.3.0. Please see the CHANGES for more details. It's
> important we get as much testing as possible for these dev releases for
> the next few months, in preparation for v3.4.0. There are several known
> bugs already, which are (now) scheduled for v3.3.3, v3.3.4 and v3.3.5
> accordingly. Help triaging, commenting and closing those bugs are also
> much needed.
This vote passes with 9 +1 votes (8 binding) and 1 -1 vote. For the -1 vote,
we have fixed the issue with certain (older compilers), it's committed on
master in 5b44534f7bdc2338c23c5cf89ddf86d6de3ae829. I'm including the tiny
patch below as well. The v.3.3.2 release has been pushed to the dist server,
and I'll make an official announcement tomorrow.
Thanks to everyone for voting! v3.3.3 in a month, keep up the great work
towards v3.4.0 stable.
-- Leif
diff --git a/lib/records/RecUtils.cc b/lib/records/RecUtils.cc
index d04fce7..3680fee 100644
--- a/lib/records/RecUtils.cc
+++ b/lib/records/RecUtils.cc
@@ -76,7 +76,7 @@ RecDataSetMax(RecDataT type, RecData * data)
#endif
case RECD_INT:
case RECD_COUNTER:
- data->rec_int = 0x7fffffffffffffff;
+ data->rec_int = INT64_MAX; // Assumes rec_int is int64_t, which it currently is
break;
#if defined(STAT_PROCESSOR)
case RECD_CONST:
@@ -98,7 +98,7 @@ RecDataSetMin(RecDataT type, RecData * data)
#endif
case RECD_INT:
case RECD_COUNTER:
- data->rec_int = 0x8000000000000000;
+ data->rec_int = INT64_MIN; // Assumes rec_int is int64_t, which it currently is
break;
#if defined(STAT_PROCESSOR)
case RECD_CONST:
Re: [VOTE] Release v3.3.2
Posted by Brian Geffon <br...@gmail.com>.
+1 from me RHEL 6.2 64bit, regressions pass.
Re: [VOTE] Release v3.3.2
Posted by Brian Geffon <br...@gmail.com>.
+1 from me RHEL 6.2 64bit, regressions pass.
Re: [VOTE] Release v3.3.2
Posted by "Alan M. Carroll" <am...@network-geographics.com>.
Running it in my test rig, built & tested on FC17, Ubuntu 12.0.4 (32bit).
+1
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <zw...@apache.org>.
Yeah, this is an unfortunate artifact of the SRV changes. I filed an RFE on
it, it's unreasonable to reserve space for SRV even when the feature is
disabled (which is the default ).
-- Leif
On Apr 16, 2013, at 4:12 PM, Bryan Call <bc...@yahoo-inc.com> wrote:
> +1
>
> Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
>
> -Bryan
>
> On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
>> On 4/16/13 4:19 AM, Igor Galić wrote:
>>>
>>> -
>>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> make check-TESTS
>>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Buffer
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Event
>>> =============================================
>>> 2 of 2 tests failed
>>> Please report to dev@trafficserver.apache.org
>>> =============================================
>>
>> I have some fixes for this, which I will commit for v3.3.3. If everyone is
>> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
>> runtime or compile time at all (only make test fails, which is bad, but not
>> mission critical). The changes does not change anything in the core code,
>> only in the building of the test programs themselves. With my fixes, all
>> tests succeeds, for v3.3.2 as well.
>>
>> Thanks Igor.
>>
>> -- Leif
>
Re: [VOTE] Release v3.3.2
Posted by Jim Jagielski <ji...@jaguNET.com>.
+1 from me as well...
On Apr 16, 2013, at 6:12 PM, Bryan Call <bc...@yahoo-inc.com> wrote:
> +1
>
> Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
>
> -Bryan
>
> On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
>> On 4/16/13 4:19 AM, Igor Galić wrote:
>>>
>>> -
>>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> make check-TESTS
>>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Buffer
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Event
>>> =============================================
>>> 2 of 2 tests failed
>>> Please report to dev@trafficserver.apache.org
>>> =============================================
>>
>> I have some fixes for this, which I will commit for v3.3.3. If everyone is
>> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
>> runtime or compile time at all (only make test fails, which is bad, but not
>> mission critical). The changes does not change anything in the core code,
>> only in the building of the test programs themselves. With my fixes, all
>> tests succeeds, for v3.3.2 as well.
>>
>> Thanks Igor.
>>
>> -- Leif
>>
>
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <zw...@apache.org>.
Yeah, this is an unfortunate artifact of the SRV changes. I filed an RFE on
it, it's unreasonable to reserve space for SRV even when the feature is
disabled (which is the default ).
-- Leif
On Apr 16, 2013, at 4:12 PM, Bryan Call <bc...@yahoo-inc.com> wrote:
> +1
>
> Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
>
> -Bryan
>
> On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
>> On 4/16/13 4:19 AM, Igor Galić wrote:
>>>
>>> -
>>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> make check-TESTS
>>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Buffer
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Event
>>> =============================================
>>> 2 of 2 tests failed
>>> Please report to dev@trafficserver.apache.org
>>> =============================================
>>
>> I have some fixes for this, which I will commit for v3.3.3. If everyone is
>> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
>> runtime or compile time at all (only make test fails, which is bad, but not
>> mission critical). The changes does not change anything in the core code,
>> only in the building of the test programs themselves. With my fixes, all
>> tests succeeds, for v3.3.2 as well.
>>
>> Thanks Igor.
>>
>> -- Leif
>
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <le...@ogre.com>.
Yeah, this is an unfortunate artifact of the SRV changes. I filed an RFE on it, it's unreasonable to reserve space for SRV even when the feature is disabled (which is the default ).
-- Leif
Sent from my C64
On Apr 16, 2013, at 4:12 PM, Bryan Call <bc...@yahoo-inc.com> wrote:
> +1
>
> Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
>
> -Bryan
>
> On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
>> On 4/16/13 4:19 AM, Igor Galić wrote:
>>>
>>> -
>>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> make check-TESTS
>>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Buffer
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Event
>>> =============================================
>>> 2 of 2 tests failed
>>> Please report to dev@trafficserver.apache.org
>>> =============================================
>>
>> I have some fixes for this, which I will commit for v3.3.3. If everyone is
>> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
>> runtime or compile time at all (only make test fails, which is bad, but not
>> mission critical). The changes does not change anything in the core code,
>> only in the building of the test programs themselves. With my fixes, all
>> tests succeeds, for v3.3.2 as well.
>>
>> Thanks Igor.
>>
>> -- Leif
>
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <zw...@apache.org>.
On 4/18/13 11:41 AM, James Peach wrote:
> On Apr 18, 2013, at 10:25 AM, Bryan Call <bc...@yahoo-inc.com> wrote:
>
>> Couldn't resolve the origin hostname. I had to turn on debugging in traffic server and saw that it couldn't resolve the hostname for the origin server. I don't remember if the response to the client was an empty reply or if there was a valid http error response.
> Ick, that's nasty. We should make sure that it auto-upgrades hostDB for people coming from 3.2 to 3.4. I filed https://issues.apache.org/jira/browse/TS-1832
It does that. The issue is trying to run current trunk with a v3.2 config,
it doesn't work. The old config said "Please store 120,000 objects in 32MB",
and that worked fine. With the SRV changes, if you try that, it gets
confused, and won't do it (and apparently disables HostDB :). This is why
the default size was changed to 200MB.
I think we should do https://issues.apache.org/jira/browse/TS-1811 before we
release v3.3.3 / v3.4, and then we don't have to worry about the "upgrade
path" to v3.4.
Fwiw, I agree that the configs are confusing, I never liked it. Feels like
we ought to have one, or the other, but not both. That's a different bug
though, there might even be one filed (I haven't looked).
Cheers,
-- leif
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <zw...@apache.org>.
On 4/18/13 11:41 AM, James Peach wrote:
> On Apr 18, 2013, at 10:25 AM, Bryan Call <bc...@yahoo-inc.com> wrote:
>
>> Couldn't resolve the origin hostname. I had to turn on debugging in traffic server and saw that it couldn't resolve the hostname for the origin server. I don't remember if the response to the client was an empty reply or if there was a valid http error response.
> Ick, that's nasty. We should make sure that it auto-upgrades hostDB for people coming from 3.2 to 3.4. I filed https://issues.apache.org/jira/browse/TS-1832
It does that. The issue is trying to run current trunk with a v3.2 config,
it doesn't work. The old config said "Please store 120,000 objects in 32MB",
and that worked fine. With the SRV changes, if you try that, it gets
confused, and won't do it (and apparently disables HostDB :). This is why
the default size was changed to 200MB.
I think we should do https://issues.apache.org/jira/browse/TS-1811 before we
release v3.3.3 / v3.4, and then we don't have to worry about the "upgrade
path" to v3.4.
Fwiw, I agree that the configs are confusing, I never liked it. Feels like
we ought to have one, or the other, but not both. That's a different bug
though, there might even be one filed (I haven't looked).
Cheers,
-- leif
Re: [VOTE] Release v3.3.2
Posted by James Peach <jp...@apache.org>.
On Apr 18, 2013, at 10:25 AM, Bryan Call <bc...@yahoo-inc.com> wrote:
> Couldn't resolve the origin hostname. I had to turn on debugging in traffic server and saw that it couldn't resolve the hostname for the origin server. I don't remember if the response to the client was an empty reply or if there was a valid http error response.
Ick, that's nasty. We should make sure that it auto-upgrades hostDB for people coming from 3.2 to 3.4. I filed https://issues.apache.org/jira/browse/TS-1832
J
>
> -Bryan
>
> On Apr 16, 2013, at 4:09 PM, James Peach <jp...@apache.org> wrote:
>
>> On Apr 16, 2013, at 3:12 PM, Bryan Call <bc...@yahoo-inc.com> wrote:
>>
>>> +1
>>>
>>> Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
>>
>> What were the symptoms of hostdb not working?
>>
>>>
>>> -Bryan
>>>
>>> On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>>> On 4/16/13 4:19 AM, Igor Galić wrote:
>>>>>
>>>>> -
>>>>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>>>> make check-TESTS
>>>>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>>>
>>>>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>>>>> FAIL: test_Buffer
>>>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>>>
>>>>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>>>>> FAIL: test_Event
>>>>> =============================================
>>>>> 2 of 2 tests failed
>>>>> Please report to dev@trafficserver.apache.org
>>>>> =============================================
>>>>
>>>> I have some fixes for this, which I will commit for v3.3.3. If everyone is
>>>> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
>>>> runtime or compile time at all (only make test fails, which is bad, but not
>>>> mission critical). The changes does not change anything in the core code,
>>>> only in the building of the test programs themselves. With my fixes, all
>>>> tests succeeds, for v3.3.2 as well.
>>>>
>>>> Thanks Igor.
>>>>
>>>> -- Leif
>>>>
>>>
>>
>
Re: [VOTE] Release v3.3.2
Posted by James Peach <jp...@apache.org>.
On Apr 18, 2013, at 10:25 AM, Bryan Call <bc...@yahoo-inc.com> wrote:
> Couldn't resolve the origin hostname. I had to turn on debugging in traffic server and saw that it couldn't resolve the hostname for the origin server. I don't remember if the response to the client was an empty reply or if there was a valid http error response.
Ick, that's nasty. We should make sure that it auto-upgrades hostDB for people coming from 3.2 to 3.4. I filed https://issues.apache.org/jira/browse/TS-1832
J
>
> -Bryan
>
> On Apr 16, 2013, at 4:09 PM, James Peach <jp...@apache.org> wrote:
>
>> On Apr 16, 2013, at 3:12 PM, Bryan Call <bc...@yahoo-inc.com> wrote:
>>
>>> +1
>>>
>>> Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
>>
>> What were the symptoms of hostdb not working?
>>
>>>
>>> -Bryan
>>>
>>> On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>>> On 4/16/13 4:19 AM, Igor Galić wrote:
>>>>>
>>>>> -
>>>>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>>>> make check-TESTS
>>>>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>>>
>>>>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>>>>> FAIL: test_Buffer
>>>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>>>
>>>>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>>>>> FAIL: test_Event
>>>>> =============================================
>>>>> 2 of 2 tests failed
>>>>> Please report to dev@trafficserver.apache.org
>>>>> =============================================
>>>>
>>>> I have some fixes for this, which I will commit for v3.3.3. If everyone is
>>>> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
>>>> runtime or compile time at all (only make test fails, which is bad, but not
>>>> mission critical). The changes does not change anything in the core code,
>>>> only in the building of the test programs themselves. With my fixes, all
>>>> tests succeeds, for v3.3.2 as well.
>>>>
>>>> Thanks Igor.
>>>>
>>>> -- Leif
>>>>
>>>
>>
>
Re: [VOTE] Release v3.3.2
Posted by Bryan Call <bc...@yahoo-inc.com>.
Couldn't resolve the origin hostname. I had to turn on debugging in traffic server and saw that it couldn't resolve the hostname for the origin server. I don't remember if the response to the client was an empty reply or if there was a valid http error response.
-Bryan
On Apr 16, 2013, at 4:09 PM, James Peach <jp...@apache.org> wrote:
> On Apr 16, 2013, at 3:12 PM, Bryan Call <bc...@yahoo-inc.com> wrote:
>
>> +1
>>
>> Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
>
> What were the symptoms of hostdb not working?
>
>>
>> -Bryan
>>
>> On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>>> On 4/16/13 4:19 AM, Igor Galić wrote:
>>>>
>>>> -
>>>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>>> make check-TESTS
>>>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>>
>>>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>>>> FAIL: test_Buffer
>>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>>
>>>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>>>> FAIL: test_Event
>>>> =============================================
>>>> 2 of 2 tests failed
>>>> Please report to dev@trafficserver.apache.org
>>>> =============================================
>>>
>>> I have some fixes for this, which I will commit for v3.3.3. If everyone is
>>> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
>>> runtime or compile time at all (only make test fails, which is bad, but not
>>> mission critical). The changes does not change anything in the core code,
>>> only in the building of the test programs themselves. With my fixes, all
>>> tests succeeds, for v3.3.2 as well.
>>>
>>> Thanks Igor.
>>>
>>> -- Leif
>>>
>>
>
Re: [VOTE] Release v3.3.2
Posted by Bryan Call <bc...@yahoo-inc.com>.
Couldn't resolve the origin hostname. I had to turn on debugging in traffic server and saw that it couldn't resolve the hostname for the origin server. I don't remember if the response to the client was an empty reply or if there was a valid http error response.
-Bryan
On Apr 16, 2013, at 4:09 PM, James Peach <jp...@apache.org> wrote:
> On Apr 16, 2013, at 3:12 PM, Bryan Call <bc...@yahoo-inc.com> wrote:
>
>> +1
>>
>> Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
>
> What were the symptoms of hostdb not working?
>
>>
>> -Bryan
>>
>> On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>>> On 4/16/13 4:19 AM, Igor Galić wrote:
>>>>
>>>> -
>>>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>>> make check-TESTS
>>>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>>
>>>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>>>> FAIL: test_Buffer
>>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>>
>>>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>>>> FAIL: test_Event
>>>> =============================================
>>>> 2 of 2 tests failed
>>>> Please report to dev@trafficserver.apache.org
>>>> =============================================
>>>
>>> I have some fixes for this, which I will commit for v3.3.3. If everyone is
>>> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
>>> runtime or compile time at all (only make test fails, which is bad, but not
>>> mission critical). The changes does not change anything in the core code,
>>> only in the building of the test programs themselves. With my fixes, all
>>> tests succeeds, for v3.3.2 as well.
>>>
>>> Thanks Igor.
>>>
>>> -- Leif
>>>
>>
>
Re: [VOTE] Release v3.3.2
Posted by James Peach <jp...@apache.org>.
On Apr 16, 2013, at 3:12 PM, Bryan Call <bc...@yahoo-inc.com> wrote:
> +1
>
> Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
What were the symptoms of hostdb not working?
>
> -Bryan
>
> On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
>> On 4/16/13 4:19 AM, Igor Galić wrote:
>>>
>>> -
>>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> make check-TESTS
>>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Buffer
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Event
>>> =============================================
>>> 2 of 2 tests failed
>>> Please report to dev@trafficserver.apache.org
>>> =============================================
>>
>> I have some fixes for this, which I will commit for v3.3.3. If everyone is
>> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
>> runtime or compile time at all (only make test fails, which is bad, but not
>> mission critical). The changes does not change anything in the core code,
>> only in the building of the test programs themselves. With my fixes, all
>> tests succeeds, for v3.3.2 as well.
>>
>> Thanks Igor.
>>
>> -- Leif
>>
>
Re: [VOTE] Release v3.3.2
Posted by James Peach <jp...@apache.org>.
On Apr 16, 2013, at 3:12 PM, Bryan Call <bc...@yahoo-inc.com> wrote:
> +1
>
> Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
What were the symptoms of hostdb not working?
>
> -Bryan
>
> On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
>> On 4/16/13 4:19 AM, Igor Galić wrote:
>>>
>>> -
>>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> make check-TESTS
>>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Buffer
>>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>>
>>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>>> FAIL: test_Event
>>> =============================================
>>> 2 of 2 tests failed
>>> Please report to dev@trafficserver.apache.org
>>> =============================================
>>
>> I have some fixes for this, which I will commit for v3.3.3. If everyone is
>> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
>> runtime or compile time at all (only make test fails, which is bad, but not
>> mission critical). The changes does not change anything in the core code,
>> only in the building of the test programs themselves. With my fixes, all
>> tests succeeds, for v3.3.2 as well.
>>
>> Thanks Igor.
>>
>> -- Leif
>>
>
Re: [VOTE] Release v3.3.2
Posted by Bryan Call <bc...@yahoo-inc.com>.
+1
Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
-Bryan
On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
> On 4/16/13 4:19 AM, Igor Galić wrote:
>>
>> -
>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>> make check-TESTS
>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>
>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>> FAIL: test_Buffer
>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>
>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>> FAIL: test_Event
>> =============================================
>> 2 of 2 tests failed
>> Please report to dev@trafficserver.apache.org
>> =============================================
>
> I have some fixes for this, which I will commit for v3.3.3. If everyone is
> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
> runtime or compile time at all (only make test fails, which is bad, but not
> mission critical). The changes does not change anything in the core code,
> only in the building of the test programs themselves. With my fixes, all
> tests succeeds, for v3.3.2 as well.
>
> Thanks Igor.
>
> -- Leif
>
Re: [VOTE] Release v3.3.2
Posted by Bryan Call <bc...@yahoo-inc.com>.
+1
Passed all signatures, compiled, and passed regression. It is running as my forward proxy now. One problem I ran into was it didn't work with a hostdb size of 32M and I had to increase it to 200M.
-Bryan
On Apr 16, 2013, at 8:31 AM, Leif Hedstrom <zw...@apache.org> wrote:
> On 4/16/13 4:19 AM, Igor Galić wrote:
>>
>> -
>> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>> make check-TESTS
>> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>
>> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
>> FAIL: test_Buffer
>> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>>
>> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
>> FAIL: test_Event
>> =============================================
>> 2 of 2 tests failed
>> Please report to dev@trafficserver.apache.org
>> =============================================
>
> I have some fixes for this, which I will commit for v3.3.3. If everyone is
> ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
> runtime or compile time at all (only make test fails, which is bad, but not
> mission critical). The changes does not change anything in the core code,
> only in the building of the test programs themselves. With my fixes, all
> tests succeeds, for v3.3.2 as well.
>
> Thanks Igor.
>
> -- Leif
>
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <zw...@apache.org>.
On 4/16/13 4:19 AM, Igor Galić wrote:
>
> -
> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
> make check-TESTS
> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>
> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
> FAIL: test_Buffer
> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>
> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
> FAIL: test_Event
> =============================================
> 2 of 2 tests failed
> Please report to dev@trafficserver.apache.org
> =============================================
I have some fixes for this, which I will commit for v3.3.3. If everyone is
ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
runtime or compile time at all (only make test fails, which is bad, but not
mission critical). The changes does not change anything in the core code,
only in the building of the test programs themselves. With my fixes, all
tests succeeds, for v3.3.2 as well.
Thanks Igor.
-- Leif
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <zw...@apache.org>.
On 4/16/13 4:19 AM, Igor Galić wrote:
>
> -
> make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
> make check-TESTS
> make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>
> /bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
> FAIL: test_Buffer
> ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
>
> /bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
> FAIL: test_Event
> =============================================
> 2 of 2 tests failed
> Please report to dev@trafficserver.apache.org
> =============================================
I have some fixes for this, which I will commit for v3.3.3. If everyone is
ok with it, I'd prefer not to reroll v3.3.2, these fixes doesn't affect
runtime or compile time at all (only make test fails, which is bad, but not
mission critical). The changes does not change anything in the core code,
only in the building of the test programs themselves. With my fixes, all
tests succeeds, for v3.3.2 as well.
Thanks Igor.
-- Leif
Re: [VOTE] Release v3.3.2
Posted by Igor Galić <i....@brainsware.org>.
----- Original Message -----
> Hi all,
>
> I've prepared a release for v3.3.2, which has quite a few
> improvements and
> bug fixes over 3.3.0. Please see the CHANGES for more details. It's
> important we get as much testing as possible for these dev releases
> for the
> next few months, in preparation for v3.4.0. There are several known
> bugs
> already, which are (now) scheduled for v3.3.3, v3.3.4 and v3.3.5
> accordingly. Help triaging, commenting and closing those bugs are
> also much
> needed.
>
> This is a community effort, so we need everyone to help out. Most
> important
> is that the users of ATS helps with these efforts, and your votes are
> much
> appreciated. PMC votes are of course also necessary to get this to
> pass.
Checksums and GPG sig are good.
difference between the tag and tar-ball within the expected.
./configure --prefix=/opt/ats-3.3 && make are successfull
make check fails:
make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
make check-TESTS
make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
/bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
FAIL: test_Buffer
ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
/bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
FAIL: test_Event
=============================================
2 of 2 tests failed
Please report to dev@trafficserver.apache.org
=============================================
See https://issues.apache.org/jira/browse/TS-1819 for reference.
Regression tests, however, are passed fine.
Right now I'm running it as forward proxy on my local system.
+1 from me.
> The artifacts are available at
> http://people.apache.org/~zwoop/rel-candidates/:
>
> -rw-r--r-- 1 zwoop zwoop 2782877 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2
> -rw-r--r-- 1 zwoop zwoop 836 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2.asc
> -rw-r--r-- 1 zwoop zwoop 66 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2.md5
> -rw-r--r-- 1 zwoop zwoop 74 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2.sha1
>
>
> MD5: dc736e78743bb7dd94f8980770b6856f
> SHA1: a9463dbe12a0c42b2922df9d8d209c67118bc46f
>
> The goal is to release this on April 18th, so please cast your +, -
> or 0
> votes asap.
>
> Cheers,
>
> -- leif
>
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
Re: [VOTE] Release v3.3.2
Posted by Mohd Akhbar <my...@gmail.com>.
configure, make & make install on Centos 6.4 64bit running on XenServer 6.
Seems OK
Setup as forward proxy.
Vote++
On Tue, Apr 16, 2013 at 6:35 AM, Leif Hedstrom <zw...@apache.org> wrote:
> Hi all,
>
> I've prepared a release for v3.3.2, which has quite a few improvements and
> bug fixes over 3.3.0. Please see the CHANGES for more details. It's
> important we get as much testing as possible for these dev releases for the
> next few months, in preparation for v3.4.0. There are several known bugs
> already, which are (now) scheduled for v3.3.3, v3.3.4 and v3.3.5
> accordingly. Help triaging, commenting and closing those bugs are also much
> needed.
>
> This is a community effort, so we need everyone to help out. Most
> important is that the users of ATS helps with these efforts, and your votes
> are much appreciated. PMC votes are of course also necessary to get this to
> pass.
>
>
> The artifacts are available at http://people.apache.org/~**
> zwoop/rel-candidates/ <http://people.apache.org/~zwoop/rel-candidates/>:
>
> -rw-r--r-- 1 zwoop zwoop 2782877 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.**bz2
> -rw-r--r-- 1 zwoop zwoop 836 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.**bz2.asc
> -rw-r--r-- 1 zwoop zwoop 66 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.**bz2.md5
> -rw-r--r-- 1 zwoop zwoop 74 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.**bz2.sha1
>
>
> MD5: dc736e78743bb7dd94f8980770b685**6f
> SHA1: a9463dbe12a0c42b2922df9d8d209c**67118bc46f
>
> The goal is to release this on April 18th, so please cast your +, - or 0
> votes asap.
>
> Cheers,
>
> -- leif
>
Re: [VOTE] Release v3.3.2
Posted by James Peach <jp...@apache.org>.
On Apr 17, 2013, at 4:37 AM, Nick Kew <ni...@apache.org> wrote:
> On Mon, 15 Apr 2013 16:35:35 -0600
> Leif Hedstrom <zw...@apache.org> wrote:
>
>> The goal is to release this on April 18th, so please cast your +, - or 0
>> votes asap.
>
> -1. Won't compile for me:
>
> cc1plus: warnings being treated as errors
> RecUtils.cc:79: error: integer constant is too large for ‘long’ type
> RecUtils.cc:101: error: integer constant is too large for ‘long’ type
> make[2]: *** [libreclocal_a-RecUtils.o] Error 1
>
>
> This is a regression, introduced in
> https://git-wip-us.apache.org/repos/asf/trafficserver/?p=trafficserver.git;a=commitdiff;h=5bcc19e6e901e7115bfbbcc6b4b8f60dfc51f4a7
> (March 12th).
>
> Looks like it needs a LONG_MAX construct. Or an explicitly-sized type.
> Surely I can't be the only one on 32 bits?
I just built and ran regressions on the quantal32 vagrant box. What platform and toolchain are you using?
>
> Manually fixing those constants, all else is well.
> It passes make test, and runs as a drop-in update and is
> binary-compatible with my existing ironbee binaries.
>
> --
> Nick Kew
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <zw...@apache.org>.
On 4/17/13 5:37 AM, Nick Kew wrote:
> On Mon, 15 Apr 2013 16:35:35 -0600
> Leif Hedstrom <zw...@apache.org> wrote:
>
>> The goal is to release this on April 18th, so please cast your +, - or 0
>> votes asap.
> -1. Won't compile for me:
>
> cc1plus: warnings being treated as errors
> RecUtils.cc:79: error: integer constant is too large for ‘long’ type
> RecUtils.cc:101: error: integer constant is too large for ‘long’ type
> make[2]: *** [libreclocal_a-RecUtils.o] Error 1
Well, it compiles and runs for me on my 32-bit platform :-/. I use gcc
v4.7.0 on an old (RHEL4) 32-bit machine.
We need a respin for this? Nick can you file a bug for this please?
Cheers,
-- Leif
gcc version 4.7.0 (GCC)
root@kramer 300/0 # uname -a
Linux kramer.ogre.com 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007
i686 i686 i386 GNU/Linux
Re: [VOTE] Release v3.3.2
Posted by Leif Hedstrom <zw...@apache.org>.
On 4/19/13 4:54 AM, Igor Galić wrote:
>>> It's a compiler warning rather than an error.
>>> If you build without -Werror you probably wouldn't
>>> notice the warnings as they scroll past.
>>>
>>> We need a respin for this? Nick can you file a bug for this please?
>> respin?
>>
>> I wouldn't treat it as fatal for a dev release (with release note),
>> but I'll file a bug.
> Pretty sure we have 4.4 somewhere on the buildbots - but maybe not on 32bit.
No idea. But fwiw, I ended up duplicating this on Fedora Core 12, so a
pretty old distro.
-- Leif
Re: [VOTE] Release v3.3.2
Posted by Igor Galić <i....@brainsware.org>.
> >
> > Well, it compiles and runs for me on my 32-bit platform :-/. I use
> > gcc
> > v4.7.0 on an old (RHEL4) 32-bit machine.
>
> Hmm, this is an older gcc:
>
> $ gcc --version
> gcc (Ubuntu 4.4.3-4ubuntu5.1) 4.4.3
>
> It's a compiler warning rather than an error.
> If you build without -Werror you probably wouldn't
> notice the warnings as they scroll past.
>
> > We need a respin for this? Nick can you file a bug for this please?
>
> respin?
>
> I wouldn't treat it as fatal for a dev release (with release note),
> but I'll file a bug.
Pretty sure we have 4.4 somewhere on the buildbots - but maybe not on 32bit.
> --
> Nick Kew
-- i
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
Re: [VOTE] Release v3.3.2
Posted by Nick Kew <ni...@apache.org>.
On Wed, 17 Apr 2013 09:16:00 -0600
Leif Hedstrom <zw...@apple.com> wrote:
> On 4/17/13 5:37 AM, Nick Kew wrote:
> > On Mon, 15 Apr 2013 16:35:35 -0600
> > Leif Hedstrom <zw...@apache.org> wrote:
> >
> >> The goal is to release this on April 18th, so please cast your +, - or 0
> >> votes asap.
> > -1. Won't compile for me:
> >
> > cc1plus: warnings being treated as errors
> > RecUtils.cc:79: error: integer constant is too large for ‘long’ type
> > RecUtils.cc:101: error: integer constant is too large for ‘long’ type
> > make[2]: *** [libreclocal_a-RecUtils.o] Error 1
>
> Well, it compiles and runs for me on my 32-bit platform :-/. I use gcc
> v4.7.0 on an old (RHEL4) 32-bit machine.
Hmm, this is an older gcc:
$ gcc --version
gcc (Ubuntu 4.4.3-4ubuntu5.1) 4.4.3
It's a compiler warning rather than an error.
If you build without -Werror you probably wouldn't
notice the warnings as they scroll past.
> We need a respin for this? Nick can you file a bug for this please?
respin?
I wouldn't treat it as fatal for a dev release (with release note),
but I'll file a bug.
--
Nick Kew
Re: [VOTE] Release v3.3.2
Posted by Nick Kew <ni...@apache.org>.
On Mon, 15 Apr 2013 16:35:35 -0600
Leif Hedstrom <zw...@apache.org> wrote:
> The goal is to release this on April 18th, so please cast your +, - or 0
> votes asap.
-1. Won't compile for me:
cc1plus: warnings being treated as errors
RecUtils.cc:79: error: integer constant is too large for ‘long’ type
RecUtils.cc:101: error: integer constant is too large for ‘long’ type
make[2]: *** [libreclocal_a-RecUtils.o] Error 1
This is a regression, introduced in
https://git-wip-us.apache.org/repos/asf/trafficserver/?p=trafficserver.git;a=commitdiff;h=5bcc19e6e901e7115bfbbcc6b4b8f60dfc51f4a7
(March 12th).
Looks like it needs a LONG_MAX construct. Or an explicitly-sized type.
Surely I can't be the only one on 32 bits?
Manually fixing those constants, all else is well.
It passes make test, and runs as a drop-in update and is
binary-compatible with my existing ironbee binaries.
--
Nick Kew
RE: [VOTE] Release v3.3.2
Posted by Uri Shachar <us...@hotmail.com>.
+1
Compiled, regression passes and running as forward proxy on CentOS 6.3 and Ubuntu 12.04
> Date: Mon, 15 Apr 2013 16:35:35 -0600
> From: zwoop@apache.org
> To: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: [VOTE] Release v3.3.2
>
> Hi all,
>
> I've prepared a release for v3.3.2, which has quite a few improvements and
> bug fixes over 3.3.0. Please see the CHANGES for more details. It's
> important we get as much testing as possible for these dev releases for the
> next few months, in preparation for v3.4.0. There are several known bugs
> already, which are (now) scheduled for v3.3.3, v3.3.4 and v3.3.5
> accordingly. Help triaging, commenting and closing those bugs are also much
> needed.
>
> This is a community effort, so we need everyone to help out. Most important
> is that the users of ATS helps with these efforts, and your votes are much
> appreciated. PMC votes are of course also necessary to get this to pass.
Re: [VOTE] Release v3.3.2
Posted by Igor Galić <i....@brainsware.org>.
----- Original Message -----
> Hi all,
>
> I've prepared a release for v3.3.2, which has quite a few
> improvements and
> bug fixes over 3.3.0. Please see the CHANGES for more details. It's
> important we get as much testing as possible for these dev releases
> for the
> next few months, in preparation for v3.4.0. There are several known
> bugs
> already, which are (now) scheduled for v3.3.3, v3.3.4 and v3.3.5
> accordingly. Help triaging, commenting and closing those bugs are
> also much
> needed.
>
> This is a community effort, so we need everyone to help out. Most
> important
> is that the users of ATS helps with these efforts, and your votes are
> much
> appreciated. PMC votes are of course also necessary to get this to
> pass.
Checksums and GPG sig are good.
difference between the tag and tar-ball within the expected.
./configure --prefix=/opt/ats-3.3 && make are successfull
make check fails:
make[3]: Leaving directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
make check-TESTS
make[3]: Entering directory `/tmp/ts/trafficserver-3.3.2-dev/iocore/eventsystem'
ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
/bin/bash: line 5: 19607 Segmentation fault (core dumped) ${dir}$tst
FAIL: test_Buffer
ERROR: unable to access() TS_ROOT '/opt/ats-3.3': 2, No such file or directory
/bin/bash: line 5: 19631 Segmentation fault (core dumped) ${dir}$tst
FAIL: test_Event
=============================================
2 of 2 tests failed
Please report to dev@trafficserver.apache.org
=============================================
See https://issues.apache.org/jira/browse/TS-1819 for reference.
Regression tests, however, are passed fine.
Right now I'm running it as forward proxy on my local system.
+1 from me.
> The artifacts are available at
> http://people.apache.org/~zwoop/rel-candidates/:
>
> -rw-r--r-- 1 zwoop zwoop 2782877 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2
> -rw-r--r-- 1 zwoop zwoop 836 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2.asc
> -rw-r--r-- 1 zwoop zwoop 66 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2.md5
> -rw-r--r-- 1 zwoop zwoop 74 Apr 15 22:18
> trafficserver-3.3.2-dev.tar.bz2.sha1
>
>
> MD5: dc736e78743bb7dd94f8980770b6856f
> SHA1: a9463dbe12a0c42b2922df9d8d209c67118bc46f
>
> The goal is to release this on April 18th, so please cast your +, -
> or 0
> votes asap.
>
> Cheers,
>
> -- leif
>
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
RE: [VOTE] Release v3.3.2
Posted by Uri Shachar <us...@hotmail.com>.
+1
Compiled, regression passes and running as forward proxy on CentOS 6.3 and Ubuntu 12.04
> Date: Mon, 15 Apr 2013 16:35:35 -0600
> From: zwoop@apache.org
> To: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: [VOTE] Release v3.3.2
>
> Hi all,
>
> I've prepared a release for v3.3.2, which has quite a few improvements and
> bug fixes over 3.3.0. Please see the CHANGES for more details. It's
> important we get as much testing as possible for these dev releases for the
> next few months, in preparation for v3.4.0. There are several known bugs
> already, which are (now) scheduled for v3.3.3, v3.3.4 and v3.3.5
> accordingly. Help triaging, commenting and closing those bugs are also much
> needed.
>
> This is a community effort, so we need everyone to help out. Most important
> is that the users of ATS helps with these efforts, and your votes are much
> appreciated. PMC votes are of course also necessary to get this to pass.