Zephyr Continuous Integration made the choice of rebasing pull requests on its fast moving master branch before testing them. Unfortunately the Shippable interface assumes the other choice[*] and highlights the SHA1 of the pull request _before_ rebasing which is very misleading. For now the only way to realize this disconnect is to scrutinize the build logs and/or this source code (or tribal knowledge). To mitigate and reduce a bit this confusion, run a short: git log -n 5 --oneline --decorate before and after rebase. Making it worse, Shippable sub-runs are not pegged to a common base version. For instance the reason why shippable sub-run 35578.1 passed while all other 35578.x sub runs failed is very likely because PR #13803 was merged to master in the mean time. This commit would have been able to prove that. [*] In an ideal world with infinite time and resources, Continuous Integration would test pull requests BOTH alone and combined with the moving tip. Signed-off-by: Marc Herbert <marc.herbert@intel.com> |
||
|---|---|---|
| .. | ||
| get_modified_boards.py | ||
| get_modified_tests.py | ||
| merge_junit.py | ||
| run_ci.sh | ||