The semaphore assertion look like the memory corrruption(maybe the
stack too small) which platform you are running.
On Sat, Feb 22, 2020 at 6:52 PM Oleg Evseev wrote:
>
> Hi Xiang,
>
> I can check it only on Monday, thanks!
>
> But, by the way, in commits you mentioned several errors in usrsockte
On Sat, Feb 22, 2020 at 9:59 PM David Sidrane
wrote:
> Hmm - what value is a 24 hr cycle time? The build was broken and we did
> not know it.
>
>
>
Yes, the nightly build run every 24hr, because apache server is shared by
many project and each jenkins job may wait in the queue for several hours.
Hmm - what value is a 24 hr cycle time? The build was broken and we did not
know it.
How about getting actions wired against a set of container that can build
nuttx target without pulling tools?
Then run 9-10 separate build on EVERY PR
3 arm linux
3 non arm linux
1 windows arm
1 windows m
Hi Xiang,
I can check it only on Monday, thanks!
But, by the way, in commits you mentioned several errors in usrsocktest
that looks different than on my first screenshot (especially debug
assertion failed somewhere inside semaphore). Maybe there will still be
problems due to my wrong settings. Wi
Oleg, try this PR:
https://github.com/apache/incubator-nuttx/pull/354
with Masayuki and my patch, all test in usrsocktest should pass now.
Actually, all fail is very minor:
1.Set the different errno
2.Foget to check NULL pointer
3.Don't zero the sockaddr padding bytes
,usrsock work well very even w
