Fire a test pr for Arm jenkins test (Do not merge) #97
Conversation
|
Hi @kalyxin02 - I've added the |
|
Just watch out in case the DNM label prevents the CIs from firing.... seeing as this PR is to test the CIs ;-). |
|
Heh heh - hi @kalyxin02 . This PR is not perfectly formed as per our commit rules - but - for now it does not matter I think. What will happen when your slave is working correctly is you should get all the way through the 'setup', and then fail the first check, which is the static If/when you get to that stage, then fix the PR to match the |
|
Build failed (third-party-check pipeline) integration testing with
|
|
We hit this line: Which is being resolved on kata-containers/tests#514 |
|
Build failed (third-party-check pipeline) integration testing with
|
|
Build failed (third-party-check pipeline) integration testing with
|
Codecov Report
@@ Coverage Diff @@
## master #97 +/- ##
==========================================
+ Coverage 37.26% 38.02% +0.76%
==========================================
Files 2 2
Lines 263 263
==========================================
+ Hits 98 100 +2
+ Misses 154 153 -1
+ Partials 11 10 -1 |
|
Build failed (third-party-check pipeline) integration testing with
|
kalyxin02
force-pushed
the
test-pr
branch
2 times, most recently
from
55cc9c3
to
ed125ae
Compare
|
Build failed (third-party-check pipeline) integration testing with
|
|
Hi, @grahamwhaley, at last we got a success build at http://jenkins.katacontainers.io/job/kata-containers-proxy-ARM-18.04-PR/33/console after we made some cleanup work to restore the environment especially when the previous build failed. @Pennyzct will send the patches to upstream soon. :-) Thanks |
|
Woot! 🎆 Yeah, clean environment is a problem if you cannot run in a VM or clean bare-metal for each build (kata-containers/ci#39) - I will look out for your patches - worst case I think you will have to completely clean and restart docker (including /var/lib/docker), and possibly some kata bits (/var/lib/vc sbs etc.). 95% of PR builds are fine, but every now and then a PR will knock things crazy. |
|
/cc @ydjainopensource , who may be interested in those patches for IBM Z Jenkins kata setup as well... |
|
@Pennyzct @grahamwhaley Yes, the patches will help prevent rework. |
|
Build failed (third-party-check pipeline) integration testing with
|
Fire a test pr for Arm jenkins test kata-containers#7 Fixes kata-containers#57 Signed-off-by: kaly xin <[email protected]>
|
Build failed (third-party-check pipeline) integration testing with
|
|
Speaking of which, how is the ARM CI status @kalyxin02 ? I see we had some passes, and then some fails - wondering what there is left here to do, and what it will take to get to enable the ARM CI across more repos? :-) |
|
Ping @kalyxin02 and @Pennyzct - could you give us an update on the ARM64 CI status? 😄 |
|
heh heh - I actually want to re-run a metrics build, so will piggy back here and try a: |
|
Hi, @grahamwhaley @jodh-intel, sorry for the late response. Seems we do have some problems on current CI testing. Sigh... Let us figure it out first. |
|
Hi @kalyxin02 - no problem. Let us know if we can help in any way. |
|
Does it work now? |
|
@kalyxin02 ping (from your weekly Kata herder) |
|
Hi @kalyxin02 - any update on this? |
|
@jodh-intel It works. Now we identified some features missing on the platform, and some of the changes may need to upgrade the current kernel, for example, to support persistent memory. @Pennyzct is currently verifying the test cases. After that we would request to upgrade to 4.20 or even newer kernel. Will this cause any problem for the testing environment, for example, to generate new test jobs from the server side? Thanks |
|
Hi @kalyxin02 - great. Regarding the kernel, our strategy is to use the "newest longterm" kernel so, yes, as of today, using 4.20 would deviate from that approach. See: However, as you know we have separate config files for each architecture so in theory you could update the arm config to 4.20: However, we'd then have potentially different behaviour depending on architecture which doesn't sound ideal. Maybe it would be worth adding this as a topic for the Architecture Committee meeting. /cc @egernst, @grahamwhaley, @chavafg. |
|
@kalyxin02 any updates is ARM Jenkins complete? |
|
It looks like the Jenkins CI is working for ARM64 now so can this be closed? |
|
hijacking this test PR to fire an IBM Power8 build as well ;-) |
|
/test |
|
/retest |
1 similar comment
|
/retest |
|
@kalyxin02 : Could you please rebase/close this PR. I have raised another PR to address this issue till then. |
Fixes: #57
Signed-off-by: Kaly Xin [email protected]