Build for MXNet branch master has broken. Please view the build at
https://builds.apache.org/job/incubator-mxnet/job/master/579/
Noting that we need to move to using the Apache Mirrors for downloads
rather than direct links to apache.org/dist.
https://reference.apache.org/committer/website-policy
I did a bit of digging, and it looks like we can just refer to this:
https://www.apache.org/dyn/closer.cgi/dev/incubator/mxnet/
Hello All,
A new Apache MXNet (incubating) blog post is published covering the
highlights of 0.12 release.
https://blogs.apache.org/mxnet/entry/apache-mxnet-0-12-release
Thanks!
Apache MXNet (incubating) Team
Hello All,
A new Apache MXNet (incubating) blog post is published covering the
highlights of 0.12 release.
https://blogs.apache.org/mxnet/entry/apache-mxnet-0-12-release
Thanks!
Apache MXNet (incubating) Team
Hey Henri, I think that's what a few of us are advocating. Running a set
of quick tests as part of the PR process, and then a more detailed
regression test suite periodically (say every 4 hours). This fits nicely
into a tagging or 2 branch development system. Commits will be tagged (or
merged int
Random question - can the CI be split such that the Apache CI is doing a
basic set of checks on that hardware, and is hooked to a PR, while there is
a larger "Is trunk good for release?" test that is running periodically
rather than on every PR?
ie: do we need each PR to be run on varied hardware,
Hello All,
The Apache MXNet (incubating) Community is happy to announce the
availability of Apache MXNet (incubating) version 0.12!
Contributors in the MXNet community have collaborated to bring such feature
enhancements to users. With this release, MXNet adds two new important
features:
• S
Hi Matthias,
Channels of interest for you might be #mxnet and #mxnet-builds.
Best,
Sebastian
2017-11-01 17:20 GMT+01:00 Suneel Marthi :
> Invite sent
>
> Sent from my iPhone
>
> > On Nov 1, 2017, at 6:17 PM, Matthias Seeger wrote:
> >
> > Hello,
> >
> > I got a few PRs merged into MXNet alread
Some inline thoughts.
On Wed, Nov 1, 2017 at 9:41 AM, Bhavin Thaker
wrote:
> Few comments/suggestions:
>
> 1) Can we have this nice list of todo items on the Apache MXNet wiki page
> to track them better?
>
> 2) Can we have a set of owners for each set of tests and source code
> directory? One
Thank you, Sebastian and Henry.
Addressed your comments.
Regards,
Sandeep
On Tue, Oct 31, 2017 at 10:08 PM, Sebastian wrote:
> A few small things:
>
> In the paragraph about volta support, I'd rather talk about "users" than
> "customers". Also the reference to the imagenet training script seems
To point 7) I did a little bit of measure / profiling of our test runs a
week or two ago and came to the same conclusion. I assumed the slow downs
were mostly due to new tests which had recently been added. There were
quite a few gluon tests for example added, and I think they're fairly
resource
Bhavin: I would add on point 5 that it doesn't alway make sense to attach
ownership for the broken integration test to the PR author. We're planning
extensive integration tests on a variety of hardware. Some of these test
failures won't be reproducible by most PR authors and the effort to resolve
Hi Bhavin
Good suggestions.
I wanted to respond to your point #5
The promotion of integration to master would be done automatically by
jenkins once a commit passes the nightly tests. So it should not
impose any additional burden on the developers, as there is no manual
step involved / human gate
Few comments/suggestions:
1) Can we have this nice list of todo items on the Apache MXNet wiki page
to track them better?
2) Can we have a set of owners for each set of tests and source code
directory? One of the problems I have observed is that when there is a test
failure, it is difficult to f
Invite sent
Sent from my iPhone
> On Nov 1, 2017, at 6:17 PM, Matthias Seeger wrote:
>
> Hello,
>
> I got a few PRs merged into MXNet already (github mseeger). Could you grant
> me access to slack, and give me details on the channel?
>
>
> --
> Matthias Seeger
Hello,
I got a few PRs merged into MXNet already (github mseeger). Could you grant
me access to slack, and give me details on the channel?
--
Matthias Seeger
Committers - the MXNet website needs some work to meet Apache's policies:
Site: http://mxnet.incubator.apache.org/
Policy: https://www.apache.org/foundation/marks/pmcs
Here are some I've flagged:
https://github.com/apache/incubator-mxnet-site/issues
Could someone work on this soon? It's been a l
+1 That would be great.
On Mon, Oct 30, 2017 at 5:35 PM, Hen wrote:
> How about we ask for a new mxnet repo to store all the config in?
>
> On Fri, Oct 27, 2017 at 05:30 Pedro Larroy
> wrote:
>
>> Just to provide a high level overview of the ideas and proposals
>> coming from different sources
18 matches
Mail list logo
