I'd like to add two Scala package API improvement into the patch release:
1. https://github.com/apache/incubator-mxnet/pull/11045 - It is the
minimum change for Java users to do inference.
2. https://github.com/apache/incubator-mxnet/pull/11256 - Allow
Scala users to specify the input data/labe
On 6/11/2018 8:53 PM, Marco de Abreu wrote:
> How about you set up a personal instance of JIRA (let us know if the public
> ones differ too much from the one we're running under Apache) and play
> around a bit? We can then review the setup and migrate the necessary
> changes after everything look
Hi
We would like to start publishing pre-built beta pip wheels of MXNet for
Raspberry pi and ARM.
What's the procedure to publish these artifacts?
Would this be the right location? https://pypi.org/user/mxnet-ci/ ?
Thanks.
Hi
Thanks for your insightful comments. I see the concerns about moving PR
checks to nightly and it worries me too. We should all agree on a tradeoff
of some sorts. Flaky tests not only do not help validate the code, but are
detrimental to our progress. Agree that disabling them is suboptimal but
I think Sheng manages the publishing to PyPi and we should be fine with
just adding it as another flavour.
-Marco
On Wed, Jun 13, 2018 at 6:36 AM Pedro Larroy
wrote:
> Hi
>
> We would like to start publishing pre-built beta pip wheels of MXNet for
> Raspberry pi and ARM.
>
> What's the procedur
Where will the bot code be committed?
Are you using probot?
On Tue, Jun 12, 2018 at 2:21 PM Marco de Abreu
wrote:
> Hello Cathy,
> that's a great proposal. Thank you!
>
> A few comments from my side:
> - Good idea with the alias. We should have a special email-list for
> automated reports to pr
Thanks, we are in sync and will find a solution next week.
On Wed, Jun 13, 2018 at 4:54 PM Marco de Abreu
wrote:
> I think Sheng manages the publishing to PyPi and we should be fine with
> just adding it as another flavour.
>
> -Marco
>
> On Wed, Jun 13, 2018 at 6:36 AM Pedro Larroy >
> wrote:
HI Yizhi,
I am personally not inclined to include these two changes in the patch
release. I would like to know what others think. The patch release was
meant for critical bug fixes and low risk performance improvements. Since
this is a feature addition this should go as part of next major/minor
ve
On 6/12/2018 4:24 PM, Sebastian wrote:
> Hi,
>
> I just came across a video where two of the directors of the ASF talk
> about what the board looks for in healthy apache projects. (Note that
> they look at top level projects only and things are a little different
> in the incubator). However, I
Hi Pedro,
Is there a problem in working off a branch in your own fork and issue a
[WIP] PR ? This is a pattern I have seen a lot and personally I think it
works well, since it also gives some visibility if someone is interested in
looking at the progress of the work. You can add people collaborati
The problem is that the process of porting is incremental and requires
several patches from different collaborators to advance in different areas,
like build system, infrastructure, code fixes, virtualization This gets
difficult when having multiple scattered PRs open. We lost track of which
ch
Hi
We have this url alive, and google is indexing:
http://mxnet.incubator.apache.org/test/versions/
Is this url right, or is it pointing some users to the wrong documentation?
Pedro
I think this was some testing during migration to Apache infra, I think it
probs is sitting on a branch on mxnet-site repo
> On Jun 13, 2018, at 11:13 PM, Pedro Larroy
> wrote:
>
> Hi
>
> We have this url alive, and google is indexing:
> http://mxnet.incubator.apache.org/test/versions/
>
> I
It's not on the repo.
https://github.com/apache/incubator-mxnet-site/tree/asf-site/test
Must be sitting on the server.
Maybe infra can take a look.
On Wed, Jun 13, 2018 at 2:38 PM, Naveen Swamy wrote:
> I think this was some testing during migration to Apache infra, I think it
> probs is sittin
One of the committees can delete I think
> On Jun 14, 2018, at 12:10 AM, Aaron Markham wrote:
>
> It's not on the repo.
> https://github.com/apache/incubator-mxnet-site/tree/asf-site/test
> Must be sitting on the server.
> Maybe infra can take a look.
>
>
>> On Wed, Jun 13, 2018 at 2:38 PM, Na
Hi,
PRs still in progress : #11127, #11236, #11210, #11054, #11216.
We are currently facing two issues which are delaying the merge of some of
these PRs:
1. Flaky tests for scala API. A PR is already out to disable the test:
https://github.com/apache/incubator-mxnet/issues/11249
2. Builds breakin
I'd keep an eye on this one... Flaky test: test_gru_bidirectional #11219
https://github.com/apache/incubator-mxnet/issues/11219
Just reran several PR's CI runs that all had the same error!
On Wed, Jun 13, 2018 at 5:42 PM, Anirudh wrote:
> Hi,
>
> PRs still in progress : #11127, #11236, #11210
I can confirm that this segfaulting test has a big impact.
On Wed, Jun 13, 2018 at 9:39 PM Aaron Markham
wrote:
> I'd keep an eye on this one... Flaky test: test_gru_bidirectional #11219
>
> https://github.com/apache/incubator-mxnet/issues/11219
>
> Just reran several PR's CI runs that all had
By segfaulting test do you mean : test_gru_bidirectional. I don't see the
segfault in the logs. Can you point me to the test.
Also, this seems to be specific to the master and not in 1.2:
https://github.com/apache/incubator-mxnet/pull/10311
Anirudh
On Wed, Jun 13, 2018 at 10:00 PM, Marco de Abreu
On windows tests a segfault is indicated by "If -764728474728". I have also
seen it happen on Ubuntu, there are probably some links in the issue (on my
phone right now).
Anirudh schrieb am Mi., 13. Juni 2018, 22:16:
> By segfaulting test do you mean : test_gru_bidirectional. I don't see the
> se
Yes, #10311 is only in master branch, so I guess it won't impact 1.2.0 branch
and block the release of 1.2.1, right?
A PR (#11273) is submitted to disable the test temporally and hopefully it will
be fixed soon.
-tao
-Original Message-
From: Marco de Abreu [mailto:marco.g.ab...@google
Thanks Tao! Yes, this shouldn't be a blocker for 1.2.1.
On Wed, Jun 13, 2018 at 10:46 PM, Lv, Tao A wrote:
>
> Yes, #10311 is only in master branch, so I guess it won't impact 1.2.0
> branch and block the release of 1.2.1, right?
>
> A PR (#11273) is submitted to disable the test temporally and
22 matches
Mail list logo
