Project

General

Profile

Actions

action #133580

closed

Be able to bind openQA tests to x86_64 architecture sub-versions

Added by okurz 11 months ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2023-07-31
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Motivation

https://github.com/OSInside/kiwi-functional-tests/pull/19 requires workers to support x86_64 v2. This should be solvable with worker classes.

Acceptance criteria

  • AC1: All o3 x86_64 workers specify worker classes that tests can bind to

Suggestions

Actions #1

Updated by okurz 11 months ago

  • Status changed from New to In Progress
  • Assignee set to okurz
  • Target version changed from future to Ready
 hosts="aarch64 openqaworker4 openqaworker6 openqaworker7 openqaworker19 openqaworker20 openqaworker21 openqaworker22 openqaworker23 openqaworker24 openqaworker25 openqaworker26 openqaworker27 openqaworker28 qa-power8-3 rebel"; for i in $hosts; do echo $i && ssh root@$i "grep -q avx512 /proc/cpuinfo && echo x86-64-v4 && exit; grep -q avx2 /proc/cpuinfo && echo x86-64-v3 && exit; grep -q ssse3 /proc/cpuinfo && echo x86-64-v2 && exit ; grep -q sse2 /proc/cpuinfo && echo x86-64-v1 && exit; echo No x86_64 detected" ; done

should work. It says:

aarch64
No x86_64 detected
openqaworker4
x86-64-v3
openqaworker6
x86-64-v3
openqaworker7
x86-64-v3
openqaworker19
x86-64-v3
openqaworker20
x86-64-v3
openqaworker21
x86-64-v3
openqaworker22
x86-64-v3
openqaworker23
x86-64-v3
openqaworker24
x86-64-v3
openqaworker25
ssh: connect to host openqaworker25 port 22: No route to host
openqaworker26
ssh: connect to host openqaworker26 port 22: No route to host
openqaworker27
ssh: connect to host openqaworker27 port 22: No route to host
openqaworker28
ssh: connect to host openqaworker28 port 22: No route to host
qa-power8-3
No x86_64 detected
rebel
x86-64-v2
Actions #2

Updated by okurz 11 months ago

  • Status changed from In Progress to Resolved

I now have set an according worker class on all o3 machines that we have so far and wrote a comment in the github PR

Actions

Also available in: Atom PDF