Fixes from master #2413
Fixes from master #2413
Conversation
Add support for the arduino form factor in targets.json for the NUCLEO_F429ZI.
Note: The README is auto-generated by the importer script, which copies the QUICKSTART.md guide from ARMmbed/uvisor.
This follows:
ARMmbed/uvisor#02ecf05 - "Remove unused TFN_RPC_Callback"
ARMmbed/uvisor#483ddda - "rpc: Add `rpc_fncall_wait`"
ARMmbed/uvisor#fdb7dce - "rpc: Add missing UVISOR_EXTERN to
rpc_fncall_waitfor declaration"
When a thread is terminated signal the join semaphore so any threads joining the terminated thread wake up as expected.
|
👍 |
|
/morph test |
|
@mbed-bot: TEST HOST_OSES=windows |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 625 Test failed! |
|
[Build 794] |
|
One test box was having issues, making patches now. I can rerun this after if need be. Thing to note, the morph bot always merges with master, not the branch you're submitting against. Is that still useful in this case? |
Nope :) Can the merge happen against the tip of the branch that is trying to be merged into? In general seems this should be the case. Is it possible? |
|
Oh yeah definitely possible, just not implemented yet. Need to spend some time on the bot today then (I've been meaning to that anyways). |
|
@bridadan is this ready for some new testing to be ran? |
|
/morph test |
Result: FAILUREYour command has finished executing! Here's what you wrote!
|
|
/morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 631 All builds and test passed! |
|
@sg- I added the ability for the bot to detect which branch the PR is submitted against and merge it with that branch. The most recent build on this PR did just that 👍 |
|
@bridadan @sg- Triggering only tests and not sharing the valuable output is not much helpful. I would appreciate if you also share what's the current status (review CI log). I am blocked by this in many cases. For instance, here's my view: jenkins build - checkout failure (not relevant to this changeset), continuous-integration/mbedci - not relevant neither, failures known, the rest is OK |
|
@0xc0170 The output for the CIs should be visible, are you not able to see them? With regards to the jobs titled "Jenkins Build", I don't run those, that's done by @mazimkhan. @mazimkhan are there issues with the jobs? With regards to |
I compared master to 5.1 branch, created a patch with all commits that are bugfixes (unified wait is not here).
cc @sg- @c1728p9 @bogdanm