Hi Lup,
It sounds like a good plan. Let's use it as a starting point then we
finetune it.
Thanks for looking into it
Best regards
Alin
On Thu, 17 Oct 2024, 08:10 Lee, Lup Yuen, wrote:
> Hi All: We have an ultimatum to reduce (drastically) our usage of GitHub
> Actions. Or our Continuous Integ
Hi All: We have an ultimatum to reduce (drastically) our usage of GitHub
Actions. Or our Continuous Integration will halt totally in Two Weeks.
Here's what I'll implement within 24 hours for `nuttx` and `nuttx-apps`
repos:
(1) When we submit or update a Complex PR that affects All Architectures
(A
You are right! Worker enabled again sorry :-)
I also noticed we can remove:
1. LaTeX packages install that are really heavy:
- name: Install LaTeX packages
run: |
sudo apt-get update -y
sudo apt-get install -y \
texlive-latex-recommended texlive-fonts-reco
Yes, if we disable it probably we will merge commits that will damage the
Documentation/ files format.
BR,
Alan
On Wed, Oct 16, 2024 at 3:11 PM Matteo Golin wrote:
> Hi Tomek!
>
> Yes, that's the workflow I was talking about.
>
> Doesn't it make sense to leave it enabled though? It's my unders
Hi Tomek!
Yes, that's the workflow I was talking about.
Doesn't it make sense to leave it enabled though? It's my understanding
that workflow is useful for checking PRs that modify the Documentation to
catch any introduced build errors in RST file syntax, etc. Otherwise we
only detect those error
Whoops we has in fact worker enabled for rebuilting the documentation
on each commit on the nuttx repo!!
https://github.com/apache/nuttx/actions/workflows/doc.yml
It is disabled now :-)
Documentation will be built on a daily basis on the nuttx-website
repo. Lets see how that improves things.
Th
Actually the documentation is part of the nuttx-website repo:
https://github.com/apache/nuttx-website
Documentation is updated daily:
https://github.com/apache/nuttx-website/actions
Where did you find information on doc rebuild on every commit Matteo?
For sure we may improve two things there a
Implemented a quick fix for that. Adding more granularity based on path
could also be done for other workflows I think, I can spend more time
looking at what could be optimized later this week but hopefully this PR is
enough to help cut down time!
https://github.com/apache/nuttx/pull/14372
Matteo
Exactly!
I think if no file at nuttx/Documentation/ was modified we don't need to
compile it.
BR,
Alan
On Wed, Oct 16, 2024 at 1:25 PM Matteo Golin wrote:
> I also think we can use the "paths" filter to only rebuild docs when the
> documentation files are changed, similar to how it is done in
I also think we can use the "paths" filter to only rebuild docs when the
documentation files are changed, similar to how it is done in the
Docker-Linux workflow.
On Wed, Oct 16, 2024 at 12:20 PM Matteo Golin
wrote:
> It may not be ideal, but would it be possible to change the documentation
> bui
It may not be ideal, but would it be possible to change the documentation
builds to only occur periodically?
I noticed that the doc builds take roughly ~13 minutes, and if they run on each
PR merge that will add up quickly.
GitHub actions appears to allow scheduled actions:
https://docs.github.
Yep lemme do some analysis and make some recommendations. Thanks.
Lup
On Wed, 16 Oct 2024, 11:16 pm Alan C. Assis, wrote:
> Hi Lup,
>
> Please take a look.
>
> BR,
>
> Alan
>
> -- Forwarded message -
> From: Daniel Gruno
> Date: Wed, Oct 16, 2024 at 12:08 PM
> Subject: [WARNING
Whoops even though recent CI updates it did not decrease and we may loose it o_O
I guess we need to quickly show signs of CI usage decrease in the first place.
For sure we need builder for website/documentation and maybe basic set
of code builds.. then starting from simple stuff see what is the u
Hi Lup,
Please take a look.
BR,
Alan
-- Forwarded message -
From: Daniel Gruno
Date: Wed, Oct 16, 2024 at 12:08 PM
Subject: [WARNING] All NuttX builds to be turned off by October 30th
UNLESS...
To:
Cc: ASF Infrastructure
Hello again, NuttX folks.
This is a formal notice tha
Please create an issue on github, I can add Donny or other people to ask
your question.
On Wed, Oct 16, 2024 at 1:27 AM Felipe Moura Oliveira
wrote:
> Hello Xiang Xiao,
>
> Can you connect me with Donny or can you help me to understand spi_slave
> semaphore "unlock" ?
>
> Looking into spi_slave_
In this case, you can reference:
https://github.com/apache/nuttx/blob/master/drivers/rpmsg/rpmsg_port_spi.c
https://github.com/apache/nuttx/blob/master/drivers/rpmsg/rpmsg_port_spi_slave.c
which contains the common logic to send/recv messages on spi bus async.
On Tue, Oct 15, 2024 at 10:46 PM Feli
Hi all,
I am running FOSSID from time to time and now with the SPDX migration I am
scanning again the code.
Doing checks from time to time may not be enough and the best guard would be a
CI snipped scanner
Best regards
Alin
Från: raiden00pl
Skickat: den 16 okt
+1
We need to pay more attention to the license of the code that is added. GPL
can destroy this project :(
śr., 16 paź 2024 o 07:33 Jukka Laitinen napisał(a):
> Hi,
>
> A kind reminder to everyone contributing code to NuttX;
>
> Please keep in mind that it is NOT allowed to copy code snippets f
18 matches
Mail list logo
