> On Sep 28, 2016, at 9:56 AM, Sean Mackrory wrote:
> and
> Bigtop's integration tests too. Anything else you would add to this?
Be aware that bigtop does things to the jar layout that will break parts of
hadoop 3.
Hmmm. It's an interesting side-effect of how docker caches intermediate images:
===
Step 10/35 : RUN apt-get -q update
---> Using cache
---> 79fd4a487c35
Step 11/35 : RUN echo oracle-java7-installer
shared/accepted-oracle-license-v1-1 select true | sudo
/usr/bin/debconf-set-selections
--->
bcc: bui...@apache.org, dev@hbase.apache.org, d...@hive.apache.org,
common-...@hadoop.apache.org, d...@phoenix.apache.org, d...@oozie.apache.org
(These are all of the projects that had pending issues. This is not
all of the groups that actually rely upon this code...)
The recen
> On Jan 18, 2018, at 7:50 AM, Ted Yu wrote:
>
> Allen:
> We noticed that recent precommit builds always downloaded the v1 patch for
> HBase JIRAs.
> This is the latest example:
> https://issues.apache.org/jira/browse/HBASE-19799
>
> Could this be related to Yetus ?
YETUS-598.
ts. Right now, the proposed PMC would be (alphabetical by last
> name):
>
> * Andrew Bayer (ASF member, incubator pmc, bigtop pmc, flume pmc, jclouds
> pmc, sqoop pmc, all around Jenkins expert)
> * Sean Busbey (ASF member, accumulo pmc, hbase pmc)
> * Nick Dimiduk (hbase pmc, phoenix
Since a couple of people have brought it up:
I think the release question is probably one of the big question marks.
Other than tar balls, how does something like this actually get used
downstream?
For test-patch, in particular, I have a few thoughts on this:
Short term:
I suspect the bigger issue is that the hbase tests are running on the
‘ubuntu’ machines. Since they only have ~300GB for workspaces, the hbase tests
are eating a significant majority of it and likely could be dying randomly due
to space issues. [All the hbase workspace directories + the
> On Jul 25, 2018, at 10:48 AM, Chris Lambertus wrote:
>
> On-demand resources are certainly being considered (and we had these in the
> past,) but I will point out that ephemeral (“on-demand”) cloud builds are in
> direct opposition to some of the points brought up by Allen in the other
> j
I think you pretty much covered it Sean. haha.
It’s probably worth mentioning that the ability of Yetus to shrink/grow
the scope of how much work it does is a factor of a few things:
a) the build system in use (esp post-YETUS-70; committed today
to master)
For the record, I’m planning on switching Hadoop to 0.2.0 as soon as we
finish the vote. The results we’re getting from live testing has dried up.
Allen Wittenauer created HBASE-13231:
Summary: shell script rewrite
Key: HBASE-13231
URL: https://issues.apache.org/jira/browse/HBASE-13231
Project: HBase
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/HBASE-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HBASE-14163.
--
Resolution: Won't Fix
> hbase master stop loops both processes
Allen Wittenauer created HBASE-22852:
Summary: hbase nightlies leaking gpg-agents
Key: HBASE-22852
URL: https://issues.apache.org/jira/browse/HBASE-22852
Project: HBase
Issue Type: Bug
Allen Wittenauer created HBASE-14163:
Summary: hbase master stop loops both processes forever
Key: HBASE-14163
URL: https://issues.apache.org/jira/browse/HBASE-14163
Project: HBase
Issue
14 matches
Mail list logo
