You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Sean Busbey <bu...@apache.org> on 2017/10/24 18:06:34 UTC
[NOTICE] possible cause of recent poor build quality on builds.a.o
hi folks!
FYI, the Hadoop folks have identified that some recent changes to HDFS
have been eating all memory on hosts where their tests run. So that
might be the culprit in our recent spat of new odd looking surefire
failures.
Yetus is working to add in some guard rails to keep Hadoop from doing
this in the future:
https://issues.apache.org/jira/browse/YETUS-561
Related, I have a temporary measure in place on our precommit runs
that grabs a bunch of machine information (cpus, memory, disks, etc).
If you look at build artifacts they'll be in a directory named
'machine' under 'patchprocess'.
Re: [NOTICE] possible cause of recent poor build quality on builds.a.o
Posted by Sean Busbey <bu...@apache.org>.
And now there's a jira:
HDFS-12711
On Wed, Oct 25, 2017 at 12:42 AM, Sean Busbey <bu...@apache.org> wrote:
> sure here's the hadoop thread:
>
> https://s.apache.org/azOi
>
> On Wed, Oct 25, 2017 at 12:20 AM, Chia-Ping Tsai <ch...@apache.org> wrote:
>> Could you share the reference to the hdfs changes or discussion?
>>
>> On 2017-10-25 02:06, Sean Busbey <bu...@apache.org> wrote:
>>> hi folks!
>>>
>>> FYI, the Hadoop folks have identified that some recent changes to HDFS
>>> have been eating all memory on hosts where their tests run. So that
>>> might be the culprit in our recent spat of new odd looking surefire
>>> failures.
>>>
>>> Yetus is working to add in some guard rails to keep Hadoop from doing
>>> this in the future:
>>>
>>> https://issues.apache.org/jira/browse/YETUS-561
>>>
>>> Related, I have a temporary measure in place on our precommit runs
>>> that grabs a bunch of machine information (cpus, memory, disks, etc).
>>> If you look at build artifacts they'll be in a directory named
>>> 'machine' under 'patchprocess'.
>>>
Re: [NOTICE] possible cause of recent poor build quality on builds.a.o
Posted by Sean Busbey <bu...@apache.org>.
sure here's the hadoop thread:
https://s.apache.org/azOi
On Wed, Oct 25, 2017 at 12:20 AM, Chia-Ping Tsai <ch...@apache.org> wrote:
> Could you share the reference to the hdfs changes or discussion?
>
> On 2017-10-25 02:06, Sean Busbey <bu...@apache.org> wrote:
>> hi folks!
>>
>> FYI, the Hadoop folks have identified that some recent changes to HDFS
>> have been eating all memory on hosts where their tests run. So that
>> might be the culprit in our recent spat of new odd looking surefire
>> failures.
>>
>> Yetus is working to add in some guard rails to keep Hadoop from doing
>> this in the future:
>>
>> https://issues.apache.org/jira/browse/YETUS-561
>>
>> Related, I have a temporary measure in place on our precommit runs
>> that grabs a bunch of machine information (cpus, memory, disks, etc).
>> If you look at build artifacts they'll be in a directory named
>> 'machine' under 'patchprocess'.
>>
Re: [NOTICE] possible cause of recent poor build quality on builds.a.o
Posted by Chia-Ping Tsai <ch...@apache.org>.
Could you share the reference to the hdfs changes or discussion?
On 2017-10-25 02:06, Sean Busbey <bu...@apache.org> wrote:
> hi folks!
>
> FYI, the Hadoop folks have identified that some recent changes to HDFS
> have been eating all memory on hosts where their tests run. So that
> might be the culprit in our recent spat of new odd looking surefire
> failures.
>
> Yetus is working to add in some guard rails to keep Hadoop from doing
> this in the future:
>
> https://issues.apache.org/jira/browse/YETUS-561
>
> Related, I have a temporary measure in place on our precommit runs
> that grabs a bunch of machine information (cpus, memory, disks, etc).
> If you look at build artifacts they'll be in a directory named
> 'machine' under 'patchprocess'.
>