Hi Robert,
Thanks for bring up this topic. The 2 ARM machines(16cores) which I
donated is just for POC test. We(Huawei) can donate more once moving to
official Azure pipeline. :)
Robert Metzger 于2019年12月6日周五 上午3:25写道：
> Thanks for your comments Yun.
> If there's strong support for idea 2, it w
>
> Thank you very much. I'll prepare and start to send the test result from
> next week.
>
>
Hi,
As discussed before, Flink ARM builds and test now is running as cron job
in OpenLab CI. The test result can be sent to this mail list once a day
from "i...@openlabtesting.org". Can you give ` i...@openlabtesting.org`
the right to send e-mail to bui...@flink.apache.org? It can help communit
Hi,
How is the CI migration going? I notice that Azure pipelines support
adding self-hosted pipeline agent.[1] How do you think that OpenLab donate
some ARM resources to Flink community as a agent pool? In this way, X86 and
ARM can be handled by the same CI config easily. Then we don't need do mor
t;
> [1]
>
> https://lists.apache.org/thread.html/4d7e6b1fd5c570973a68de91438dd9045afdae1685b1d1467b2149ce@%3Cdev.flink.apache.org%3E
> [2]
>
> http://apache-spark-developers-list.1001551.n3.nabble.com/Re-Ask-for-ARM-CI-for-spark-td27415.html#a27440
> [3]
>
> https://develop
without cache after 50 min. It's not a good
time to use travis ARM CI at the moment. While OpenLab doesn't have any
limitations (It can provide 16U16G VMs with no time limitation for CI job).
Just FYI, any response is welcome.
Thanks. Regards.
Xiyuan Wang 于2019年10月16日周三 上午10:37写道：
Hi all,
Recently Travis announced that ARM arch is in Alpha release[1]. Since Flink
has integrated with Travis already, I think it's quite easy for Flink to
use it for ARM CI.
Maybe some of you know that I'm working on Flink ARM testing and support. I
suggested to use OpenLab[2] as the ARM CI inf
>
> Till Rohrmann 于2019年9月23日周一 下午8:40写道：
>
>> This sounds good Xiyuan. I'd also be in favour of running the ARM builds
>> regularly as cron jobs and once we see that they are stable we could run
>> them for every master commit. Hence, I'd say let's
t they are stable we could run
> them for every master commit. Hence, I'd say let's fix the above mentioned
> problems and then set the nightly cron job up.
>
> Cheers,
> Till
>
> On Fri, Sep 20, 2019 at 8:57 AM Xiyuan Wang
> wrote:
>
> > Sure, we can run
ilures at the moment caused by ARM
> specific issue.
>
> What do the others think?
>
>
> On Tue, Sep 3, 2019 at 4:40 AM Xiyuan Wang
> wrote:
>
> > The ARM CI trigger has been changed to `github comment` way only. It
> means
> > that every PR won't start A
r question?
[1]: https://github.com/apache/flink/pull/9416
https://github.com/apache/flink/pull/9416#issuecomment-527268203
[2]: https://github.com/theopenlab/openlab-zuul-jobs/pull/631
Thanks
Xiyuan Wang 于2019年8月26日周一 下午7:41写道：
> Before ARM CI is ready, I can close the CI test for each
st adding noise to each PR
> >> that everyone will just ignore.
> >>
> >> I'm curious as to the benefit of having this directly in Flink; why
> >> aren't the ARM builds run outside of the Flink project, and fixes for it
> >> provided?
> >&
; aren't the ARM builds run outside of the Flink project, and fixes for it
> provided?
>
> It seems to me like nothing about these arm builds is actually handled
> by the Flink project.
>
> On 26/08/2019 03:43, Xiyuan Wang wrote:
> > Thanks for Stephan to bring up this top
Thanks for Stephan to bring up this topic.
The package build jobs work well now. I have a simple online demo which is
built and ran on a ARM VM. Feel free to have a try[1].
As the first step for ARM support, maybe it's good to add them now.
While for the next step, the test part is still broken.
6. CI service
I'm not very familar with tarvis, but according to its offical
doc[1][2]. Is it possible to run jobs in parallel? AFAIK, many CI system
supports this kind of feature.
[1]:
https://docs.travis-ci.com/user/speeding-up-the-build/#parallelizing-your-builds-across-virtual-machines
[2]
tests with ARM, or whether
> maybe only the "core" and "tests" profile would be enough to get confidence
> that Flink runs on ARM?
> Just asking because Flink has a lot of long running tests by now that can
> easily eat up a lot of CI capacity.
>
> Best,
> S
what do you think?
>
>
> On Fri, Jul 12, 2019 at 4:45 AM Xiyuan Wang
> wrote:
>
> > Hi Stephan
> > yeah, we should add an ARM CI first. But Travis CI doesn't support ARM
> > arch itself. OpenLab community support it. As I mentioned before, OpenLab
&g
d see what tests pass and which parts of the system would need
> to be adjusted?
>
> On Thu, Jul 11, 2019 at 9:24 AM Xiyuan Wang
> wrote:
>
> > Hi yun:
> > I didn't try to build rocksdb with vagrant, but just `make -j8
> > rocksdbjava` directly in an ARM machin
ster/java/RELEASE.md
> [2] https://github.com/dataArtisans/frocksdb
>
> Best
> Yun Tang
>
>
>
> From: Xiyuan Wang
> Sent: Tuesday, July 9, 2019 10:52
> To: dev@flink.apache.org
> Subject: Re: [DISCUSS] ARM support for Flink
>
> Tha
sans/frocksdb>
> [3] https://issues.apache.org/jira/browse/FLINK-10471 <
> https://issues.apache.org/jira/browse/FLINK-10471>
>
> Regards,
> Dian
>
> > 在 2019年7月8日，上午9:17，Xiyuan Wang 写道：
> >
> > Hi Flink:
> > Recently we meet a problem that we hav
Hi Flink:
Recently we meet a problem that we have to test and run Flink on ARM
arch. While after searching Flink community, I didn’t find an official ARM
release version.
Since Flink is made by Java and Scala language which can be ran
cross-platform usually, I think Flink can be built and ran o
21 matches
Mail list logo
