Project Description

openSUSE claims quite a lot of Arm boards to be supported. But we lack testing on that boards. There was some effort done to test Raspberry Pi on bare metal. The idea of this project is, to enhance the support and integrate other boards as well.

Goal for this Hackweek

Build a small lab with two or more boards testing openSUSE with openQA bare metal.

Resources

https://github.com/ggardet/blog/blob/master/HowTo-AddtestsonrealhardwarewithopenQA-RPi3_case.md

Looking for hackers with the skills:

arm arm64 openqa

This project is part of:

Hack Week 20

Activity

  • over 4 years ago: okurz liked this project.
  • over 4 years ago: mbrugger started this project.
  • over 4 years ago: pdostal liked this project.
  • over 4 years ago: radolin liked this project.
  • over 4 years ago: maritawerner liked this project.
  • over 4 years ago: dancermak liked this project.
  • over 4 years ago: mbrugger added keyword "arm64" to this project.
  • over 4 years ago: mbrugger added keyword "openqa" to this project.
  • over 4 years ago: mbrugger added keyword "arm" to this project.
  • over 4 years ago: mbrugger originated this project.

  • Comments

    Be the first to comment!

    Similar Projects

    Create openSUSE images for Arm/RISC-V boards by avicenzi

    Project Description

    Create openSUSE images (or test generic EFI images) for Arm and/or RISC-V boards that are not yet supported.

    Goal for this Hackweek

    Create bootable images of Tumbleweed for SBCs that currently have no images available or are untested.

    Consider generic EFI images where possible, as some boards can hold a bootloader.

    Document in the openSUSE Wiki how to flash and use the image for a given board.

    Hack Week 22

    Hack Week 21

    Resources


    openQA log viewer by mpagot

    Description

    *** Warning: Are You at Risk for VOMIT? ***

    Do you find yourself staring at a screen, your eyes glossing over as thousands of lines of text scroll by? Do you feel a wave of text-based nausea when someone asks you to "just check the logs"?

    You may be suffering from VOMIT (Verbose Output Mental Irritation Toxicity).

    This dangerous, work-induced ailment is triggered by exposure to an overwhelming quantity of log data, especially from parallel systems. The human brain, not designed to mentally process 12 simultaneous autoinst-log.txt files, enters a state of toxic shock. It rejects the "Verbose Output," making it impossible to find the one critical error line buried in a 50,000-line sea of "INFO: doing a thing."

    Before you're forced to rm -rf /var/log in a fit of desperation, we present the digital antacid.

    No panic: The openQA Log Visualizer (Also known as the "VOMIT-B-Gone 9000")

    This is your web-based hazmat suit for handling toxic log environments. It bravely dives into the chaotic, multi-machine mess of your openQA test runs, finds all the related, verbose logs, and force-feeds them into a parser.

    image

    Goals

    Work on the existing POC openqa-log-visualizer and change it to something usable

    Resources

    openqa-log-visualizer