Project

General

Profile

Actions
Copy link

action #61853

closed

[functional][y] remote_ssh_controller and remote_vnc_controller hardcode MACHINE, HDD_1 and QEMUVGA in testsuite, auto_review:"qemu-system-aarch64: Cirrus VGA not available"

Added by ggardet_arm about 5 years ago. Updated almost 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
riafarov
Category:
Enhancement to existing tests
Target version:
-
Start date:
2020-01-07
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

remote_ssh_controller and remote_vnc_controller hardcode MACHINE, HDD_1 and QEMUVGA in testsuite which is wrong and prevent to use/try the test on other architectures than x86_64.

Actions
Copy link
 #1

Updated by okurz about 5 years ago

  • Subject changed from remote_ssh_controller and remote_vnc_controller hardcode MACHINE, HDD_1 and QEMUVGA in testsuite to [functional][y] remote_ssh_controller and remote_vnc_controller hardcode MACHINE, HDD_1 and QEMUVGA in testsuite
  • Category set to Enhancement to existing tests

I think QSF-y recently added the testsuites.

Actions
Copy link
 #2

Updated by JERiveraMoya about 5 years ago

  • Status changed from New to Rejected

We still have those jobs in Development group, I had to had some of them for ssh, I didn't find other way, but we will take a look.

Actions
Copy link
 #3

Updated by JERiveraMoya about 5 years ago

  • Status changed from Rejected to New
Actions
Copy link
 #4

Updated by ybonatakis about 5 years ago

i removed the HDD_1 and QEMUVGA from the remote_vnc_controller and i will include them to the yaml. but this doesnt really help the purpose as the YAML_SCHEDULE is still used

Actions
Copy link
 #5

Updated by ggardet_arm about 5 years ago

ybonatakis wrote:

i removed the HDD_1 and QEMUVGA from the remote_vnc_controller and i will include them to the yaml. but this doesnt really help the purpose as the YAML_SCHEDULE is still used

For QEMUVGA just schedule your test on 64bit_cirrus machine. No need to define that in the test.
For HDD_1 I think you should schedule your test after the one creating the HDD_1 image. This will allow to make HDD_1 generic, as done for other tests. You may have a look at extra_tests_dracut for a template.
By the way how is built the qcow2 image?

And this should be done for ssh module as well.

Actions
Copy link
 #6

Updated by mkittler about 5 years ago

  • Subject changed from [functional][y] remote_ssh_controller and remote_vnc_controller hardcode MACHINE, HDD_1 and QEMUVGA in testsuite to [functional][y] remote_ssh_controller and remote_vnc_controller hardcode MACHINE, HDD_1 and QEMUVGA in testsuite, auto_review:"qemu-system-aarch64: Cirrus VGA not available"
Actions
Copy link
 #7

Updated by ggardet_arm about 5 years ago

ggardet_arm wrote:

For QEMUVGA just schedule your test on 64bit_cirrus machine. No need to define that in the test.

I did this for remote_ssh_* tests for x86_64.

Regarding HDD_1, I think you should use Tumbleweed gnome image, no?

Actions
Copy link
 #8

Updated by riafarov almost 5 years ago

  • Status changed from New to Rejected
  • Assignee set to riafarov

This is not yet working on 64bit, and enabled in development job group. Let us make it work there first. SSH installation is blocked with bug atm. So rejecting. See #9576.

Actions
Copy link

Also available in: Atom PDF