Hi,
I'm trying to get the tcpblaster example to work. I am using a
SAMA5D3-Xplained with Gigabit ethernet configured, directly connected to a
Linux workstation. I can ping each side of the connection from the other.
When I run the NSH telnetd on NuttX, I can telnet from the Linux
workstation to th
Hi,
> I just submitted it.
Thanks for that, it looks fine and I’ve signed dit off.
In future please follow the formatting guidelines at the top of the page and
don’t change the spacing from the template, I’ve fixed it this time.
In particular:
• Keep all lines under 76 characters long
Hi Justin,
I just submitted it.
On Wed, Feb 5, 2020 at 1:01 AM Justin Mclean wrote:
>
> Hi,
>
> Don't forget the report is due today.
>
> Thanks,
> Justin
Hi,
Don't forget the report is due today.
Thanks,
Justin
btashton commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-582189612
I pushed for this a couple times but it seemed full steam ahead for Jenkins.
My plan was to wait for some of the ci scripts to stabilize and
Hi,
> Yet another great argument for github actions.
A number of projects are experimenting with this but there no official ASF
support for it yet. [1] There’s a thread I cannot find on making that support
more “official”. Also note this thread on broken build taking up resources. [2]
Thank
davids5 commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-582159472
>Just be aware that the build servers are a shared resource from all
projects and we are expected to not make unreasonable demands on it. I’m
Yet another great argument for github actions.
-Original Message-
From: GitBox [mailto:g...@apache.org]
Sent: Tuesday, February 04, 2020 1:26 PM
To: dev@nuttx.apache.org
Subject: [GitHub] [incubator-nuttx-testing] justinmclean commented on issue
#2: Multibranch pipeline job example
justi
justinmclean commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-582122695
Hi,
> I think the " nightly build" mind set is not the way this should be looked
at. 24Hr cycle time is not going to move this projec
Hi Alan,
I committed the change. I fixed nxstyle complaints along the way,
please run a quick test to check that I didn't mess anything up.
Thanks.
On Tue, Feb 4, 2020 at 6:18 PM Alan Carvalho de Assis wrote:
>
> Hi Everyone,
>
> This patch fix an issue where Kinetis SPI was transmitting four 0
Hi Everyone,
This patch fix an issue where Kinetis SPI was transmitting four 0x00
bytes before the actual SPI_SEND() byte.
After some investigation I discovered this detail in the datasheet
about DIS_TXF and DIS_RXF bits: "This bit can be written only when the
MDIS bit is cleared."
BR,
Alan
Fro
davids5 commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-582033081
>Yes, regarding time concerns check option should take less time than full
and can be shortened if needed by simply removing/commenting out s
xiaoxiang781216 commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581985725
> I have no rights on `github.com/apache/incubator-nuttx` to inject triggers
towards my Jenkins, neither
> rights to create jobs i
maht commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581980751
Yes, regarding time concerns `check` option should take less time than
`full` and can be shortened if needed by simply removing/commenting out s
liuguo09 commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581977370
> @davids5 @patacongo @jerpelea
>
> Totally agree, and that was and is the original intention. This is just a
skeleton to build upon:
maht commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581969346
I have no rights on `github.com/apache/incubator-nuttx` to inject triggers
towards my Jenkins, neither
rights to create jobs in builds.apache
maht commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581943694
@davids5 @patacongo @jerpelea
Totally agree, and that was and is the original intention. This is just a
skeleton to build upon: I think
jerpelea edited a comment on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581928151
i think that we should hook it with github and run it automatically for each
incoming PR
---
jerpelea edited a comment on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581928151
I think that we should hook it with github and run it automatically for each
incoming PR
---
jerpelea edited a comment on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581928151
i think that we should hook it with github and run it automatically for each
coming PR
-
jerpelea commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581928151
i think that we should hook it with github and run it for each coming PR
Th
patacongo commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581925304
I don't think that huge nightly builds triggered by a cron and tailored
sanity checks triggered by PRs are mutually exclusive. I would lik
davids5 commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581921903
I think the " nightly build" mind set is not the way this should be looked
at. 24Hr cycle time is not going to move this project along. The b
maht commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581914346
@davids5 @xiaoxiang781216
One more comment: the advantage of the pipeline job respect a normal one is
that each pull request will create
maht edited a comment on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581904365
@davids5
I have not tested in builds.apache.org Jenkins, since I have no rights to
create the pipeline job.
I tested it
maht commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581904365
@David
I have not tested in builds.apache.org Jenkins, since I have no rights to
create the pipeline job.
I tested it on an exte
Hello David,
Thank you very much for your response! I excluded the -lsupc++ from my
Make.deps file and it works now.
Best regards,
Ivan Ucherdzhiev!
On Tue, Feb 4, 2020 at 2:45 PM David Sidrane
wrote:
> Ivan,
>
> There is a limit on what C++ can be compiled and built with Nuttx.
>
> The key is
xiaoxiang781216 commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581896677
Here is a test build:
https://builds.apache.org/view/Incubator%20Projects/job/NuttX-Nightly-Build/18/console
It fail due to thi
Ivan,
There is a limit on what C++ can be compiled and built with Nuttx.
The key is to not include any foreign (non nuttx) headers you can see the
defconfigs setting used on PX4 here
https://github.com/PX4/Firmware/tree/master/boards/px4/fmu-v5/nuttx-config/nsh
and the things needed in Make.def h
davids5 commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581889580
@maht - What is the URL of the job's results?
This is an automated message f
xiaoxiang781216 merged pull request #4: Add prebuilt gperf needed in
kconfig-frontends configure
URL: https://github.com/apache/incubator-nuttx-testing/pull/4
This is an automated message from the Apache Git Service.
To resp
maht commented on issue #2: Multibranch pipeline job example
URL:
https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581874207
I have updated the commits to include @liuguo09 CI script, so maybe the pull
request can be used/merged actually.
-
jerpelea commented on issue #4: Add prebuilt gperf needed in kconfig-frontends
configure
URL:
https://github.com/apache/incubator-nuttx-testing/pull/4#issuecomment-581864997
+1 for now
This is an automated message from
Hi Haitao,
I will take a look.
By the way, do Apache Jenkins slave includes Docker? Or alternatively, does
Apache Jenkins have Docker Slave [1] plugin available?
If we could use either launch Docker containers in the slave or launch the
jobs in a Docker container we could use an image with all t
Thanks Xiang!
Another PR https://github.com/apache/incubator-nuttx-testing/pull/4 since
Apache jenkins slave haven't gperf preinstalled,
so switch to use our owned prebuilt gperf. Xiang and Miguel please help to
review.
Or in another way, may I ask Justin Apache Infra team to apt-get install
gperf
liuguo09 opened a new pull request #4: Add prebuilt gperf needed in
kconfig-frontends configure
URL: https://github.com/apache/incubator-nuttx-testing/pull/4
Apache jenkins slave may not have gperf installed, so make gperf prebuilt
which needed in kconfig-frontends configure.
Sign
Hello,
I need a little bit help if possible. I am using libcxx in my project but
wil the new nuttx i start having an error during the linking
libsupc++.a(vterminate.o): In function
`__gnu_cxx::__verbose_terminate_handler()':
vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0xfc):
37 matches
Mail list logo
