xiaoxiang781216 commented on a change in pull request #17: Add Dockerfile for
CI system and hook into GitHub Actions
URL:
https://github.com/apache/incubator-nuttx-testing/pull/17#discussion_r396065947
##
File path: docker/linux/Dockerfile
##
@@ -0,0 +1,153 @@
+#
liuguo09 commented on a change in pull request #17: Add Dockerfile for CI
system and hook into GitHub Actions
URL:
https://github.com/apache/incubator-nuttx-testing/pull/17#discussion_r396072819
##
File path: .github/workflows/docker_linux.yml
##
@@ -0,0 +1,58 @@
+#
liuguo09 commented on issue #17: Add Dockerfile for CI system and hook into
GitHub Actions
URL:
https://github.com/apache/incubator-nuttx-testing/pull/17#issuecomment-602171894
> @liuguo09 Sorry it took me so long to get this together after I pointed
you at my proof of concept. I was
xiaoxiang781216 commented on a change in pull request #18: Configure python
environment and install esptool
URL:
https://github.com/apache/incubator-nuttx-testing/pull/18#discussion_r396066270
##
File path: cibuild.sh
##
@@ -118,6 +123,7 @@ function
xiaoxiang781216 commented on a change in pull request #18: Configure python
environment and install esptool
URL:
https://github.com/apache/incubator-nuttx-testing/pull/18#discussion_r396066155
##
File path: cibuild.sh
##
@@ -24,6 +24,11 @@ apps=$WD/../apps
Ouss4 commented on issue #18: Configure python environment and install esptool
URL:
https://github.com/apache/incubator-nuttx-testing/pull/18#issuecomment-602169680
@xiaoxiang781216 Will this suffice to fix
[437](https://github.com/apache/incubator-nuttx/pull/437) ?
The POSTBUILD
xiaoxiang781216 commented on issue #18: Configure python environment and
install esptool
URL:
https://github.com/apache/incubator-nuttx-testing/pull/18#issuecomment-602170823
> @xiaoxiang781216 Will this suffice to fix
[437](https://github.com/apache/incubator-nuttx/pull/437) ?
> The
liuguo09 commented on a change in pull request #17: Add Dockerfile for CI
system and hook into GitHub Actions
URL:
https://github.com/apache/incubator-nuttx-testing/pull/17#discussion_r396072392
##
File path: .github/workflows/docker_linux.yml
##
@@ -0,0 +1,58 @@
+#
xiaoxiang781216 commented on a change in pull request #17: Add Dockerfile for
CI system and hook into GitHub Actions
URL:
https://github.com/apache/incubator-nuttx-testing/pull/17#discussion_r396065709
##
File path: .github/workflows/docker_linux.yml
##
@@ -0,0 +1,58 @@
xiaoxiang781216 commented on a change in pull request #17: Add Dockerfile for
CI system and hook into GitHub Actions
URL:
https://github.com/apache/incubator-nuttx-testing/pull/17#discussion_r396065702
##
File path: .github/workflows/docker_linux.yml
##
@@ -0,0 +1,58 @@
xiaoxiang781216 commented on issue #17: Add Dockerfile for CI system and hook
into GitHub Actions
URL:
https://github.com/apache/incubator-nuttx-testing/pull/17#issuecomment-602163664
https://github.com/apache/incubator-nuttx/pull/437
btashton opened a new pull request #18: Configure python environment and
install esptool
URL: https://github.com/apache/incubator-nuttx-testing/pull/18
This configures a the python user installation environment and then installs
the `esptool` dependency. Should resolve the nightly build
Sorry if I missed something.
Is there a reason why nuttx-testing PR discussions on github are being
forwarded to the dev list?
I think either all PR discussions should be forwarded or none. I would prefer
none.
Regards, Johannes
>
> I think either all PR discussions should be forwarded or none. I would
> prefer none.
All of the repos discussions were forwarded to the dev list. A prior JIRA
issue solved this for the nuttx/ and apps/ repos. At that time the testing
repo didn't exist.
On Sun, Mar 22, 2020 at 2:58 PM
> -Ursprüngliche Nachricht-
> Von: Abdelatif Guettouche [mailto:abdelatif.guettou...@gmail.com]
> Gesendet: Sonntag, 22. März 2020 15:58
> An: dev@nuttx.apache.org
> Betreff: Re: nuttx-testing PR discussions on dev list
>
> Hi,
> Today I filled a JIRA issue to forward them to the commit
Hi,
Today I filled a JIRA issue to forward them to the commit list.
That's solved. They shouldn't appear in the dev list anymore.
On Sun, Mar 22, 2020 at 2:01 PM Schock, Johannes - NIVUS GmbH <
johannes.sch...@nivus.com> wrote:
> Sorry if I missed something.
> Is there a reason why nuttx-testing
I mentioned it in the PR that broke this,
https://github.com/apache/incubator-nuttx/pull/603#issuecomment-602264860
I don't really understand what all happened with that PR, but when I
reverted it and the corresponding one in incubator-nuttx-apps everything
went back to normal.
--Brennan
On
Ok, then we're good to go.
I have a list of files that only NuttX committers have touched, I uploaded
to the wiki page. Shall I change the headers on those files and create a PR
for them?
I am not sure how to use your 'apache_authors' file. By committer, do you
mean NuttX committer, or just an
Brennan,
What's the SHA of the commit I should use to do my authors/committers
analysis? I'm using HEAD right now. If you tell me, I'll re-run the
analysis at that SHA.
I updated the wiki page here:
https://cwiki.apache.org/confluence/display/NUTTX/Analysis+March+2020
-adam
--
Adam Feuer
There are a bunch of commits that changed things which is why I just greped
for the files that included the header.
So I think we can just do everything you were looking for in sched/** and
then circle back on the files that changed outside of it, which I don't
think should be too bad.
--Brennan
hi,
is anyone already looking at these failures?
https://github.com/apache/incubator-nuttx/pull/607/checks?check_run_id=526302981
Configuration/Tool: pcduino-a10/nsh,CONFIG_ARMV7M_TOOLCHAIN_GNU_EABIL
21 matches
Mail list logo
