Use SPR BM for e2e #1699
Use SPR BM for e2e #1699
Conversation
tkatila
force-pushed
the
bm-spr-test
branch
3 times, most recently
from
405352a
to
5f5e8cc
Compare
|
Please comment on the structure. In order to run multiple tests per run, I had to move the ginkgo variables out of the workflow. If the variables are for the whole test session, then qat is the only one that passes and dsa and iaa are skipped. This structure is a bit annoying as it ties device plugin project and the bmaas scripts more together. We wouldn't, for example, be able make a patch release for older releases without changing the bmaas side. The bmaas changes are visible in the bmaas project. |
|
@hj-johannes-lee can you comment? |
It's not clear to me what the issue is. I get a pretty comprehensive list with: |
|
When I tried to run qat, dsa and iaa e2e tests back to back, only qat executed due to the qat4's ginkgo focus/skip: It might be possible to create a "e2e-spr" target which would run all the tests with one call. I can look into it. |
It's quite likely that the regexp creation is just broken. Moreover, we have #1687 WIP that should help streamline this a bit. That's why I asked @hj-johannes-lee to comment on this |
tkatila
force-pushed
the
bm-spr-test
branch
2 times, most recently
from
526e3ad
to
a0181a5
Compare
|
sorry for being so slow recently. |
|
This is the current ginkgo focus: I think I tried it without Mode and Resource. For Resource it failed due to trying to run |
|
If mode was not used, then yeah, as you said The current focus seems ok to me regardless of the commit that I made. Why wasn't the ci/cd run? If my commit is merged, then |
There was/is an issue with the SPR machine. But it should be possible to retry it today. |
|
Flow passed now. It now runs QAT, IAA, DSA and GPU. SGX is wip in the HW. |
Run IAA, DSA, GPU, QAT and SGX tests on it. Signed-off-by: Tuomas Katila <[email protected]>
No description provided.