You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by Ramya N <ra...@tataelxsi.co.in.INVALID> on 2020/08/10 14:41:57 UTC

Pre-check flow

Hi,

1. In the NuttX Pre-check flow, docker image is built from "Pre-built Toolchain" of each architecture. If the pre-built toolchain is not available, can we build the toolchain from "Toolchain Source Code" in the Dockerfile of incubator-nuttx-testing repo?

2. The Pre-check build treats all warnings as error (Extra Flags: "-Werror"). Can we perform Pre-check build with warnings for a particular architecture in a new testlist? (Extra Flags: "-w")

Note: Fix for the warnings shall be done at the later stage, since the fix has to be checked for all the boards in the architecture.

Best Regards
Ramya N

________________________________
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
________________________________

Re: Pre-check flow

Posted by Brennan Ashton <ba...@brennanashton.com>.
On Mon, Aug 31, 2020, 6:18 AM Ramya N <ra...@tataelxsi.co.in.invalid>
wrote:

> Hi Brennan,
> Thank you for merging the RX Toolchain in NuttX testing repo. Now, we are
> fixing the warnings in the RX65N board build. Once the warnings are fixed,
> I would like to add the RX65N board build in CI.
>
> Can I add a new job (new testlist "renesas.dat" for RX65N board building)
> in CI or add the RX65N board to the existing arm testlist (like
> "arm-13.dat")?
>


Let's start with it separate and then we can look at rebalancing the test
lists for the runners later.

Thanks for adding this.

--Brennan

>

Re: Pre-check flow

Posted by Ramya N <ra...@tataelxsi.co.in.INVALID>.
Hi Brennan,
Thank you for merging the RX Toolchain in NuttX testing repo. Now, we are fixing the warnings in the RX65N board build. Once the warnings are fixed, I would like to add the RX65N board build in CI.

Can I add a new job (new testlist "renesas.dat" for RX65N board building) in CI or add the RX65N board to the existing arm testlist (like "arm-13.dat")?

Note: RX65N board can't be added to "avr-mips-riscv-x86-xtensa.dat" testlist, since RX Toolchain is added only for Linux.

Best Regards
Ramya N




________________________________
From: Ramya N <ra...@tataelxsi.co.in.INVALID>
Sent: 19 August 2020 19:24
To: dev@nuttx.apache.org <de...@nuttx.apache.org>
Subject: Re: Pre-check flow

________________________________
 **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
________________________________

Brennan,
Thank you for your comment. As suggested, I've opened a PR for RX toolchain inclusion.

Best Regards,
Ramya N
________________________________
From: Brennan Ashton <ba...@brennanashton.com>
Sent: 17 August 2020 22:26
To: dev@nuttx.apache.org <de...@nuttx.apache.org>
Subject: Re: Pre-check flow

________________________________
 **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
________________________________

Ramya,
Apologies, for the delay.  I think what would make the most sense to
start just updating the existing Docker file to include a new build
stage for the toolchain and open a PR.  We can then look at the build
time and move things around a bit if we need to.  One of the things
that we can do is publish an image that contains the rx build stage
and then pull that when doing later build in the CI.  This will let us
skip building that stage if it is untouched.

--Brennan

On Mon, Aug 17, 2020 at 5:35 AM Ramya N <ra...@tataelxsi.co.in.invalid> wrote:
>
> Hi Brennan,
>
> Can you please share your comments regarding the build time for container as shared in the previous mail.
>
> Best Regards,
> Ramya N
> ________________________________
> From: Ramya N <ra...@tataelxsi.co.in.INVALID>
> Sent: 12 August 2020 20:37
> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
> Subject: Re: Pre-check flow
>
> ________________________________
>  **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
> ________________________________
>
> Hi,
>
> I am planning to add RX Toolchain for the Renesas architecture (for RX65N board) with reference to the build steps provided in the below URL,
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc-renesas.com%2Fwiki%2Findex.php%3Ftitle%3DHow_to_build_the_RX_Toolchain_under_Ubuntu_14.04&amp;data=02%7C01%7Cramya.n%40tataelxsi.co.in%7Cddf604f9bd164ef3da3108d844478027%7Cad6a39dd96b6436882daf2ec4d92e26a%7C0%7C1%7C637334421185736354&amp;sdata=WIXGoLqUDnER8W%2BfqXoWyuZ7MzTgfJbMUXSO83lDis8%3D&amp;reserved=0
>
> I checked on the local build time for the container when RX Toolchain is added. Build time would be increased to 30 minutes (approx).
>
> I'm new to the docker container setup in the github. Is there any reference available for publishing the intermediate container and using it when building?
>
> Does "publish the intermediate container" mean pushing the Dockerfile (with RX toolchain) to incubator-nuttx-testing repo?
>
> Best Regards,
> Ramya N
> ________________________________
> From: Brennan Ashton <ba...@brennanashton.com>
> Sent: 11 August 2020 10:29
> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
> Subject: Re: Pre-check flow
>
> ________________________________
>  **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
> ________________________________
>
> On Mon, Aug 10, 2020, 9:42 PM Xiang Xiao <xi...@gmail.com> wrote:
>
> >
> >
> > > -----Original Message-----
> > > From: Ramya N <ra...@tataelxsi.co.in.INVALID>
> > > Sent: Monday, August 10, 2020 10:42 PM
> > > To: dev@nuttx.apache.org
> > > Subject: Pre-check flow
> > >
> > > Hi,
> > >
> > > 1. In the NuttX Pre-check flow, docker image is built from "Pre-built
> > Toolchain" of each architecture. If the pre-built toolchain
> > is not
> > > available, can we build the toolchain from "Toolchain Source Code" in
> > the Dockerfile of incubator-nuttx-testing repo?
> > >
> >
> > I think so, but Brennan can give more input.
> >
>
> We can although I would like more details on this. I don't want to give
> people horrible build times for the container so it might make sense to
> publish the intermediate container as well and use that when building.
>
> Can you share what architecture and compiler you are wanting to add?
>
> --Brennan
>
> >
> ________________________________
> Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
> ________________________________

Re: Pre-check flow

Posted by Ramya N <ra...@tataelxsi.co.in.INVALID>.
Brennan,
Thank you for your comment. As suggested, I've opened a PR for RX toolchain inclusion.

Best Regards,
Ramya N
________________________________
From: Brennan Ashton <ba...@brennanashton.com>
Sent: 17 August 2020 22:26
To: dev@nuttx.apache.org <de...@nuttx.apache.org>
Subject: Re: Pre-check flow

________________________________
 **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
________________________________

Ramya,
Apologies, for the delay.  I think what would make the most sense to
start just updating the existing Docker file to include a new build
stage for the toolchain and open a PR.  We can then look at the build
time and move things around a bit if we need to.  One of the things
that we can do is publish an image that contains the rx build stage
and then pull that when doing later build in the CI.  This will let us
skip building that stage if it is untouched.

--Brennan

On Mon, Aug 17, 2020 at 5:35 AM Ramya N <ra...@tataelxsi.co.in.invalid> wrote:
>
> Hi Brennan,
>
> Can you please share your comments regarding the build time for container as shared in the previous mail.
>
> Best Regards,
> Ramya N
> ________________________________
> From: Ramya N <ra...@tataelxsi.co.in.INVALID>
> Sent: 12 August 2020 20:37
> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
> Subject: Re: Pre-check flow
>
> ________________________________
>  **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
> ________________________________
>
> Hi,
>
> I am planning to add RX Toolchain for the Renesas architecture (for RX65N board) with reference to the build steps provided in the below URL,
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc-renesas.com%2Fwiki%2Findex.php%3Ftitle%3DHow_to_build_the_RX_Toolchain_under_Ubuntu_14.04&amp;data=02%7C01%7Cramya.n%40tataelxsi.co.in%7Ce85b01ab283f49baf4b608d842ce92f7%7Cad6a39dd96b6436882daf2ec4d92e26a%7C0%7C0%7C637332802289450257&amp;sdata=QkFgf7IPtDKJ9uv1gxo25PRYrx5B7W6D1bPj9y%2B2nag%3D&amp;reserved=0
>
> I checked on the local build time for the container when RX Toolchain is added. Build time would be increased to 30 minutes (approx).
>
> I'm new to the docker container setup in the github. Is there any reference available for publishing the intermediate container and using it when building?
>
> Does "publish the intermediate container" mean pushing the Dockerfile (with RX toolchain) to incubator-nuttx-testing repo?
>
> Best Regards,
> Ramya N
> ________________________________
> From: Brennan Ashton <ba...@brennanashton.com>
> Sent: 11 August 2020 10:29
> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
> Subject: Re: Pre-check flow
>
> ________________________________
>  **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
> ________________________________
>
> On Mon, Aug 10, 2020, 9:42 PM Xiang Xiao <xi...@gmail.com> wrote:
>
> >
> >
> > > -----Original Message-----
> > > From: Ramya N <ra...@tataelxsi.co.in.INVALID>
> > > Sent: Monday, August 10, 2020 10:42 PM
> > > To: dev@nuttx.apache.org
> > > Subject: Pre-check flow
> > >
> > > Hi,
> > >
> > > 1. In the NuttX Pre-check flow, docker image is built from "Pre-built
> > Toolchain" of each architecture. If the pre-built toolchain
> > is not
> > > available, can we build the toolchain from "Toolchain Source Code" in
> > the Dockerfile of incubator-nuttx-testing repo?
> > >
> >
> > I think so, but Brennan can give more input.
> >
>
> We can although I would like more details on this. I don't want to give
> people horrible build times for the container so it might make sense to
> publish the intermediate container as well and use that when building.
>
> Can you share what architecture and compiler you are wanting to add?
>
> --Brennan
>
> >
> ________________________________
> Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
> ________________________________

Re: Pre-check flow

Posted by Brennan Ashton <ba...@brennanashton.com>.
Ramya,
Apologies, for the delay.  I think what would make the most sense to
start just updating the existing Docker file to include a new build
stage for the toolchain and open a PR.  We can then look at the build
time and move things around a bit if we need to.  One of the things
that we can do is publish an image that contains the rx build stage
and then pull that when doing later build in the CI.  This will let us
skip building that stage if it is untouched.

--Brennan

On Mon, Aug 17, 2020 at 5:35 AM Ramya N <ra...@tataelxsi.co.in.invalid> wrote:
>
> Hi Brennan,
>
> Can you please share your comments regarding the build time for container as shared in the previous mail.
>
> Best Regards,
> Ramya N
> ________________________________
> From: Ramya N <ra...@tataelxsi.co.in.INVALID>
> Sent: 12 August 2020 20:37
> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
> Subject: Re: Pre-check flow
>
> ________________________________
>  **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
> ________________________________
>
> Hi,
>
> I am planning to add RX Toolchain for the Renesas architecture (for RX65N board) with reference to the build steps provided in the below URL,
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc-renesas.com%2Fwiki%2Findex.php%3Ftitle%3DHow_to_build_the_RX_Toolchain_under_Ubuntu_14.04&amp;data=02%7C01%7Cramya.n%40tataelxsi.co.in%7Cd246105d086140414f3108d83ed17604%7Cad6a39dd96b6436882daf2ec4d92e26a%7C0%7C0%7C637328416671279997&amp;sdata=rrECtJf5DVRS0XIhA0fPiD2SdJbzvsGrbOkw73oYTRI%3D&amp;reserved=0
>
> I checked on the local build time for the container when RX Toolchain is added. Build time would be increased to 30 minutes (approx).
>
> I'm new to the docker container setup in the github. Is there any reference available for publishing the intermediate container and using it when building?
>
> Does "publish the intermediate container" mean pushing the Dockerfile (with RX toolchain) to incubator-nuttx-testing repo?
>
> Best Regards,
> Ramya N
> ________________________________
> From: Brennan Ashton <ba...@brennanashton.com>
> Sent: 11 August 2020 10:29
> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
> Subject: Re: Pre-check flow
>
> ________________________________
>  **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
> ________________________________
>
> On Mon, Aug 10, 2020, 9:42 PM Xiang Xiao <xi...@gmail.com> wrote:
>
> >
> >
> > > -----Original Message-----
> > > From: Ramya N <ra...@tataelxsi.co.in.INVALID>
> > > Sent: Monday, August 10, 2020 10:42 PM
> > > To: dev@nuttx.apache.org
> > > Subject: Pre-check flow
> > >
> > > Hi,
> > >
> > > 1. In the NuttX Pre-check flow, docker image is built from "Pre-built
> > Toolchain" of each architecture. If the pre-built toolchain
> > is not
> > > available, can we build the toolchain from "Toolchain Source Code" in
> > the Dockerfile of incubator-nuttx-testing repo?
> > >
> >
> > I think so, but Brennan can give more input.
> >
>
> We can although I would like more details on this. I don't want to give
> people horrible build times for the container so it might make sense to
> publish the intermediate container as well and use that when building.
>
> Can you share what architecture and compiler you are wanting to add?
>
> --Brennan
>
> >
> ________________________________
> Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
> ________________________________

Re: Pre-check flow

Posted by Ramya N <ra...@tataelxsi.co.in.INVALID>.
Hi Brennan,

Can you please share your comments regarding the build time for container as shared in the previous mail.

Best Regards,
Ramya N
________________________________
From: Ramya N <ra...@tataelxsi.co.in.INVALID>
Sent: 12 August 2020 20:37
To: dev@nuttx.apache.org <de...@nuttx.apache.org>
Subject: Re: Pre-check flow

________________________________
 **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
________________________________

Hi,

I am planning to add RX Toolchain for the Renesas architecture (for RX65N board) with reference to the build steps provided in the below URL,
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc-renesas.com%2Fwiki%2Findex.php%3Ftitle%3DHow_to_build_the_RX_Toolchain_under_Ubuntu_14.04&amp;data=02%7C01%7Cramya.n%40tataelxsi.co.in%7Cd246105d086140414f3108d83ed17604%7Cad6a39dd96b6436882daf2ec4d92e26a%7C0%7C0%7C637328416671279997&amp;sdata=rrECtJf5DVRS0XIhA0fPiD2SdJbzvsGrbOkw73oYTRI%3D&amp;reserved=0

I checked on the local build time for the container when RX Toolchain is added. Build time would be increased to 30 minutes (approx).

I'm new to the docker container setup in the github. Is there any reference available for publishing the intermediate container and using it when building?

Does "publish the intermediate container" mean pushing the Dockerfile (with RX toolchain) to incubator-nuttx-testing repo?

Best Regards,
Ramya N
________________________________
From: Brennan Ashton <ba...@brennanashton.com>
Sent: 11 August 2020 10:29
To: dev@nuttx.apache.org <de...@nuttx.apache.org>
Subject: Re: Pre-check flow

________________________________
 **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
________________________________

On Mon, Aug 10, 2020, 9:42 PM Xiang Xiao <xi...@gmail.com> wrote:

>
>
> > -----Original Message-----
> > From: Ramya N <ra...@tataelxsi.co.in.INVALID>
> > Sent: Monday, August 10, 2020 10:42 PM
> > To: dev@nuttx.apache.org
> > Subject: Pre-check flow
> >
> > Hi,
> >
> > 1. In the NuttX Pre-check flow, docker image is built from "Pre-built
> Toolchain" of each architecture. If the pre-built toolchain
> is not
> > available, can we build the toolchain from "Toolchain Source Code" in
> the Dockerfile of incubator-nuttx-testing repo?
> >
>
> I think so, but Brennan can give more input.
>

We can although I would like more details on this. I don't want to give
people horrible build times for the container so it might make sense to
publish the intermediate container as well and use that when building.

Can you share what architecture and compiler you are wanting to add?

--Brennan

>
________________________________
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
________________________________

Re: Pre-check flow

Posted by Ramya N <ra...@tataelxsi.co.in.INVALID>.
Hi,

I am planning to add RX Toolchain for the Renesas architecture (for RX65N board) with reference to the build steps provided in the below URL,
https://gcc-renesas.com/wiki/index.php?title=How_to_build_the_RX_Toolchain_under_Ubuntu_14.04

I checked on the local build time for the container when RX Toolchain is added. Build time would be increased to 30 minutes (approx).

I'm new to the docker container setup in the github. Is there any reference available for publishing the intermediate container and using it when building?

Does "publish the intermediate container" mean pushing the Dockerfile (with RX toolchain) to incubator-nuttx-testing repo?

Best Regards,
Ramya N
________________________________
From: Brennan Ashton <ba...@brennanashton.com>
Sent: 11 August 2020 10:29
To: dev@nuttx.apache.org <de...@nuttx.apache.org>
Subject: Re: Pre-check flow

________________________________
 **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
________________________________

On Mon, Aug 10, 2020, 9:42 PM Xiang Xiao <xi...@gmail.com> wrote:

>
>
> > -----Original Message-----
> > From: Ramya N <ra...@tataelxsi.co.in.INVALID>
> > Sent: Monday, August 10, 2020 10:42 PM
> > To: dev@nuttx.apache.org
> > Subject: Pre-check flow
> >
> > Hi,
> >
> > 1. In the NuttX Pre-check flow, docker image is built from "Pre-built
> Toolchain" of each architecture. If the pre-built toolchain
> is not
> > available, can we build the toolchain from "Toolchain Source Code" in
> the Dockerfile of incubator-nuttx-testing repo?
> >
>
> I think so, but Brennan can give more input.
>

We can although I would like more details on this. I don't want to give
people horrible build times for the container so it might make sense to
publish the intermediate container as well and use that when building.

Can you share what architecture and compiler you are wanting to add?

--Brennan

>
________________________________
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
________________________________

Re: Pre-check flow

Posted by Brennan Ashton <ba...@brennanashton.com>.
On Mon, Aug 10, 2020, 9:42 PM Xiang Xiao <xi...@gmail.com> wrote:

>
>
> > -----Original Message-----
> > From: Ramya N <ra...@tataelxsi.co.in.INVALID>
> > Sent: Monday, August 10, 2020 10:42 PM
> > To: dev@nuttx.apache.org
> > Subject: Pre-check flow
> >
> > Hi,
> >
> > 1. In the NuttX Pre-check flow, docker image is built from "Pre-built
> Toolchain" of each architecture. If the pre-built toolchain
> is not
> > available, can we build the toolchain from "Toolchain Source Code" in
> the Dockerfile of incubator-nuttx-testing repo?
> >
>
> I think so, but Brennan can give more input.
>

We can although I would like more details on this. I don't want to give
people horrible build times for the container so it might make sense to
publish the intermediate container as well and use that when building.

Can you share what architecture and compiler you are wanting to add?

--Brennan

>

RE: Pre-check flow

Posted by Xiang Xiao <xi...@gmail.com>.

> -----Original Message-----
> From: Ramya N <ra...@tataelxsi.co.in.INVALID>
> Sent: Monday, August 10, 2020 10:42 PM
> To: dev@nuttx.apache.org
> Subject: Pre-check flow
> 
> Hi,
> 
> 1. In the NuttX Pre-check flow, docker image is built from "Pre-built Toolchain" of each architecture. If the pre-built toolchain
is not
> available, can we build the toolchain from "Toolchain Source Code" in the Dockerfile of incubator-nuttx-testing repo?
> 

I think so, but Brennan can give more input. 

> 2. The Pre-check build treats all warnings as error (Extra Flags: "-Werror"). Can we perform Pre-check build with warnings for a
> particular architecture in a new testlist? (Extra Flags: "-w")
> 

Why we need relax the check? It took a long time to fix all warning before turning -Werror.

> Note: Fix for the warnings shall be done at the later stage, since the fix has to be checked for all the boards in the
architecture.
> 
> Best Regards
> Ramya N
> 
> ________________________________
> Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or
entity to
> whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in
> error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the
> intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is
> strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for
any errors,
> omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If
verification
> is required, please request for a hard-copy version.
> ________________________________