Project

General

Profile

Actions

action #10478

closed

aarch64

Added by RBrownSUSE about 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
New test
Start date:
2016-01-28
Due date:
% Done:

70%

Estimated time:
Difficulty:

Checklist

  • sle

Related issues 1 (0 open1 closed)

Has duplicate openQA Tests - action #9776: ARM TestsRejectedlnussel2015-12-02

Actions
Actions #1

Updated by okurz about 8 years ago

  • Assignee set to RBrownSUSE

aarch appears now in SLES but incomplete: https://openqa.suse.de/tests/200101

Actions #2

Updated by RBrownSUSE about 8 years ago

  • Status changed from New to In Progress

aarch64 in test development

waiting for Interlock/PRD and more builds to help get a picture of a required/realistic scope and will adjust testing accordingly

Actions #3

Updated by RBrownSUSE about 8 years ago

  • Checklist item changed from to [ ] sle
  • Target version set to Milestone 2

Some tests are in Test Development

aarch64 needs to be tested as close to fully as possible given available hardware

This task exists now to track any problems that arise - the Assignee is responsible for adding aarch64 jobs to the SLE 12 SP2 Server Job group and making sure they work

Actions #4

Updated by okurz about 8 years ago

current status is that keyboard seems to not work. next step: check manually in a qemu if keyboard works

Actions #5

Updated by RBrownSUSE about 8 years ago

  • Status changed from In Progress to Closed
Actions #6

Updated by RBrownSUSE about 8 years ago

  • Status changed from Closed to In Progress
  • % Done changed from 0 to 70
Actions #7

Updated by okurz almost 8 years ago

can you update on what is missing? It seems like there is bug https://bugzilla.suse.com/show_bug.cgi?id=978157 and such but as these are definetly product bugs from the side of "aarch64 support in openQA" we are done, are we not?

Actions #8

Updated by okurz almost 8 years ago

https://openqa.suse.de/tests/384742/modules/yast2_bootloader/steps/5 seems to show a correct bootloader configuration screen for "GRUB2 for EFI" on aarch64 w/o secure boot support. My guess would be: new needle needed but I am not sure

vim tries to start but takes long (or too long)

same as for sshd

Actions #9

Updated by okurz almost 8 years ago

… but aarch64 reaches gnome, fcrozat is happy :-)
bug for "missing desktop icons": https://bugzilla.suse.com/show_bug.cgi?id=979444

Actions #10

Updated by RBrownSUSE almost 8 years ago

the narrow box makes me feel it's wrong and misformatted..

I'd expect it to look more like https://openqa.suse.de/tests/384409/modules/yast2_bootloader/steps/3 just without the secure boot options

Actions #11

Updated by okurz almost 8 years ago

needle created for yast2_bootloader as discussed on irc://chat.freenode.net/yast

Actions #12

Updated by okurz almost 8 years ago

  • Checklist item changed from [ ] sle to [x] sle
  • Status changed from In Progress to Resolved

Considered done, e.g. see https://openqa.suse.de/tests/443162 for a successful allpatterns test with soft failures for known product issues.

Actions #13

Updated by okurz almost 8 years ago

Actions

Also available in: Atom PDF