nuttx-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [incubator-nuttx] xiaoxiang781216 commented on issue #886: Cygwin sim:nsh failed on apps/builtin
Date Tue, 28 Apr 2020 05:52:33 GMT

xiaoxiang781216 commented on issue #886:

   > Just for reference it currently takes over 1.5hr to run the Cygwin sim builds. There
are a couple optimizations I can make but I would not expect to shave more than 30%. 
   1.5hr*70%=1hr, it's still a little bit slow, it will be great if we can finish in 40m
   > WSL is just Ubuntu so I don't see any reason to duplicate that.
   Yes, we can skip WSL. I use both Ubuntu and WSL daily, no problem specific for WSL find
so far.
   > The Native builds should be quite a bit faster.
   > > 2.Select one but different arch for each variant
   > > 3.Enable all config which can only build on Windows(e.g. z80?)
   > > > If a Windows CI is really time consuming too much time for efficent PR checks,
perhaps only a
   > > 
   > > 
   > > Now, we build on Linux/macOS with 18VMs, but the finish time is around from 7m
to 41m. So we have enough room to optimize VMs usage(distrube the work more balance) to 16VMs
at least, then we have 4VMs for each Windows variants.
   > > > nightly test would be sufficient. That would not detect breakage on the
PR, but would still catch the breakage post-merge. Which, at least to me, is and acceptable
performance/thoroughness tradeoff.
   > > 
   > > 
   > > It's hard to deploy the nightly build to Apache Windows server, since:
   > > 1.Apache Windows server is much less than Linux server
   > > 2.We don't have the right to install software directly without JNFRA help
   > I don't really see any reason we cannot do the nightly build using GitHub Actions
we can easily make the targets conditional on the job and then we don't have to redo all the
CI work and have close to full coverage.
   Good point, we can run the nightly build with GitHub too. But since Apache server run on
the real hardware with extreme large number cpu core, it is very useful to find the parallel
build issue.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

View raw message