[IEC-35] [IEC][SEBA] Update and refresh testing tools for arm64 Created: 30/Mar/20 Updated: 08/Apr/20 |
|
| Status: | In Progress |
| Project: | Integrated Edge Cloud |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Medium |
| Reporter: | Ciprian Barbu | Assignee: | Ciprian Barbu |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Last year I made an attempt at integrating SiaB testing facilities into Akraino IEC: That effort had to be put on hold because SiaB tests were not passing due to various issues, and eventually the old SEBA 1.0.0 (on top of cord-platform 6.1.0) has stopped working altogether. Now we have moved ahead with a newer version of SEBA (see So far the manual tests we have done indicate these tests should be working fine, but we need to automate them and introduce the necessary jobs in the Akraino CI. |
| Comments |
| Comment by Ciprian Barbu [ 08/Apr/20 ] |
|
I've added the output log from running the SEBA tests on one of the arm64 PODs in the ENEA lab. |
| Comment by Ciprian Barbu [ 08/Apr/20 ] |
|
After testing manually on the internal ENEA pods, I prepared this change: Additionally, I have updated the iecedge/cord-tester image, renaming old latest to cord-6.1 (also redoing the manifest for multi-arch) and uploaded a new version, cord-7.1, also together with a manifest to support amd64 and arm64. As soon as the #3348 is merged, we need to create the necessary change in ci-management, for adding the SEBA validation job. More or less the same as the older #1243: |
| Comment by Ciprian Barbu [ 31/Mar/20 ] |
|
During the initial effort of integrating cord-tester into Akraino IEC CI, I bumped into an issue building some dependencies of cord-tester during the setup_venv.sh step. Might or might not still be the case now, but if needed, the work for that is covered in |
| Comment by Ciprian Barbu [ 30/Mar/20 ] |
|
It makes a lot of sense to first try on x86/amd64 against the baseline we have used to port our own version for arm64. |