This is a follow up to my previous post about How to test things with openQA without running your own instance, so you might want to read that first.

Now, while hunting for bsc#1219073 which is quite sporadic, and took quite some time to show up often enough so that became noticeable and traceable, once stars aligned and managed to find a way to get a higher failure rate, I wanted to have a way for me and for the developer to test the kernel with the different patches to help with the bisecting and ease the process of finding the culprit and finding a solution for it.

I came with a fairly simple solution, using the --repeat parameter of the openqa-cli tool, and a simple shell script to run it:

```bash
$ cat ~/Downloads/trigger-kernel-openqa-mdadm.sh
# the kernel repo must be the one without https; tests don't have the kernel CA installed
KERNEL="KOTD_REPO=http://download.opensuse.org/repositories/Kernel:/linux-next/standard/"

REPEAT="--repeat 100" # using 100 by default
JOBS="https://openqa.your.instan.ce/tests/13311283 https://openqa.your.instan.ce/tests/13311263 https://openqa.your.instan.ce/tests/13311276 https://openqa.your.instan.ce/tests/13311278"
BUILD="bsc1219073"
for JOB in $JOBS; do 
	openqa-clone-job --within-instance $JOB CASEDIR=https://github.com/foursixnine/os-autoinst-distri-opensuse.git#tellmewhy ${REPEAT} \
		_GROUP=DEVELOPERS ${KERNEL} BUILD=${BUILD} FORCE_SERIAL_TERMINAL=1\
		TEST="${BUILD}_checkmdadm" YAML_SCHEDULE=schedule/qam/QR/15-SP5/textmode/textmode-skip-registration-extra.yaml INSTALLONLY=0 DESKTOP=textmode\
		|& tee jobs-launched.list;
done;

There are few things to note here:

• the kernel repo must be the one without https; tests don’t have the CA installed by default.
• the --repeat parameter is set to 100 by default, but can be changed to whatever number is desired.
• the JOBS variable contains the list of jobs to clone and run, having all supported architecures is recommended (at least for this case)
• the BUILD variable can be anything, but it’s recommended to use the bug number or something that makes sense.
• the TEST variable is used to set the name of the test as it will show in the test overview page, you can use TEST+=foo if you want to append text instead of overriding it, the --repeat parameter, will append a number incrementally to your test, see os-autoinst/openQA#5331 for more details.
• the YAML_SCHEDULE variable is used to set the yaml schedule to use, there are other ways to modify the schedule, but in this case I want to perform a full installation

Running the script

• Ensure you can run at least the openQA client; if you need API keys, see post linked at the beginning of this post
• replace the kernel repo with your branch in line 5
• run the script $ bash trigger-kernel-openqa-mdadm.sh and you should get the following, times the --repeat if you modified it

1 job has been created:
 - sle-15-SP5-Full-QR-x86_64-Build134.5-skip_registration+workaround_modules@64bit -> https://openqa.your.instan.ce/tests/13345270

Each URL, will be a job triggered in openQA, depending on the load and amount of jobs, you might need to wait quite a bit (some users can help moving the priority of these jobs so it executes faster)

The review stuff:

Looking at the results

• Go to https://openqa.your.instan.ce/tests/overview?distri=sle&build=bsc1219073&version=15-SP5 or from any job from the list above click on Job groups menu at the top, and select Build bsc1219073
• Click on “Filter”
• type the name of the test module to filter in the field Module name, e.g mdadm, and select the desired result of such test module e.g failed (you can also type, and select multiple result types)
• Click Apply
• The overall summary of the build overview page, will provide you with enough information to calculate the pass/fail rate.

A rule of thumb: anything above 5% is bad, but you need to also understand your sample size + the setup you’re using; YMMV.

Ain’t nobody got time to wait

The script will generate a file called: jobs-launched.list, in case you absolutely need to change the priority of the jobs, set it to 45, so it runs higher than default priority, which is 50 cat jobs-launched.list | grep https | sed -E 's/^.*->\s.*tests\///' | xargs -r -I {} bash -c "openqa-cli api --osd -X POST jobs/{}/prio prio=45; sleep 1"

The magic

The actual magic is in the schedule, so right after booting the system and setting it up, before running the mdadm test, I inserted the update_kernel module, which will add the kernel repo specified by KOTD_REPO, and install the kernel from there, reboot the system, and leave the system ready for the actual test, however I had to add very small changes:

---
 tests/kernel/update_kernel.pm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/kernel/update_kernel.pm b/tests/kernel/update_kernel.pm
index 1d6312bee0dc..048da593f68f 100644
--- a/tests/kernel/update_kernel.pm
+++ b/tests/kernel/update_kernel.pm
@@ -398,7 +398,7 @@ sub boot_to_console {
 sub run {
     my $self = shift;
 
-    if ((is_ipmi && get_var('LTP_BAREMETAL')) || is_transactional) {
+    if ((is_ipmi && get_var('LTP_BAREMETAL')) || is_transactional || get_var('FORCE_SERIAL_TERMINAL')) {
         # System is already booted after installation, just switch terminal
         select_serial_terminal;
     } else {
@@ -476,7 +476,7 @@ sub run {
         reboot_on_changes;
     } elsif (!get_var('KGRAFT')) {
         power_action('reboot', textmode => 1);
-        $self->wait_boot if get_var('LTP_BAREMETAL');
+        $self->wait_boot if (get_var('FORCE_SERIAL_TERMINAL') || get_var('LTP_BAREMETAL'));
     }
 }
 

Likely I’ll make a new pull request to have this in the test distribution, but for now this is good enough to help kernel developers to do some self-service and trigger their own openQA tests, that have many more tests (hopefully in parallel) and faster than if there was a person doing all of this manually.

Special thanks to the QE Kernel team, who do the amazing job of thinking of some scenarios like this, because they save a lot of time.

En esta ocasión tengo muy fácil hacer esta entrada ya que básicamente es un copia y pega de la entrada que he hecho para la Asociación en la que anunciamos la iniciativa «Colabora y gana una camiseta de KDE España Akademy-es de Málaga 2023 Opensouthcode Edition». ¿Te interesa? Sigue leyendo.

Recordatorio – Colabora y gana una camiseta de KDE España Akademy-es de Málaga 2023 Opensouthcode Edition

Tal y como podemos leer en la página web de KDE España:

¿Quieres ganar una camiseta conmemorativa de la última Akademy-es celebrada en Málaga? Pues lo tienes muy fácil.

Para conseguirla debes realizar alguna de las siguientes acciones:

• Conseguir traer a la asociación un nuevo socio (ver condiciones y proceso en este enlace)
• Resolver un bug de KDE (mira cómo se hace en este artículo)
• Realizar 3 informes de bugs a partir de la publicación de estas bases hasta el lanzamiento de Plasma 6 (que será el 28 de febrero de 2024, mira como se hace en este enlace)
• Escribir 3 artículos de calidad hablando de noticias de KDE en tu blog (más de 300 palabras, que sea original, etc.)
• Poner subtítulos a los vídeos de los podcast largos de KDE España o charlas de Akademy-es. (ponte en contacto con la asociación para conocer detalles )

Bases:

1. KDE España se reserva el derecho de dar por válidas las participaciones.

2. Para dar fe se debe enviar un correo a junta@kde_espana.org donde se muestre que ha cumplido con los requisitos: capturas de pantalla, bug resuelto, enlaces, etc.

3. En caso de que estos sean correctos nos pondremos en contacto contigo para pedirte los datos del envío de la camiseta.
4. La promoción es válida hasta agotar existencias.
5. Solo se puede ganar una camiseta por persona.



Así que, no te lo pienses más y ponte manos a la obra ya que participando no solo puedes conseguir una camiseta sino que colaboras a que el Software Libre siga creciendo.



¿Qué es Akademy-es?

Akademy-es (#akademyes, que es la etiqueta para las redes sociales) es evento más importante para los desarrolladores y simpatizantes de KDE, que se ha ido celebrando desde el 2006 con éxito creciente.

En general, las Akademy-es son el lugar adecuado para conocer a los desarrolladores, diseñadores, traductores, usuarios y empresas  que mueven este gran proyecto.

En ellas se realizan ponencias, se presentan programas, se hace un poco de caja para los proyectos libres (camisetas, chapas, etc) pero sobre todo se conoce a gente muy interesante y se cargan baterías para el futuro.

La entrada Recordatorio – Colabora y gana una camiseta de KDE España Akademy-es de Málaga 2023 Opensouthcode Edition se publicó primero en KDE Blog.

You know that support for MacOS is important when every third visitor at the syslog-ng booth of Red Hat Summit asks if syslog-ng works on MacOS. With the upcoming syslog-ng version 4.6.0, syslog-ng not only compiles on MacOS, but it also collects local log messages natively. From this blog you can learn how to compile syslog-ng yourself, options of the MacOS source, and also a bit of history.

https://www.syslog-ng.com/community/b/blog/posts/native-macos-source-in-syslog-ng

The January syslog-ng newsletter is now on-line:

• Why use a http()-based destination in syslog-ng?
• An overview of Cloudflare’s logging pipeline
• Working with multiple systemd-journal namespaces in syslog-ng
• Logging to Humio / Logscale simplified in syslog-ng

It is available at https://www.syslog-ng.com/community/b/blog/posts/the-syslog-ng-insider-2024-01-http-cloudflare-systemd-journal-humio-logscale

Publicada la versión GNU Moe 1.14 de este editor de texto para la terminal

GNU moe es un editor de texto que forma parte del software GNU y que ha publicado este 22 de enero de 2024 su versión 1.14. Después de casi un año desde la publicación de su anterior versión.

Pero ¿Qué es GNU Moe?

GNU moe es un editor de texto sencillo (pero potente) para la terminal, similar a otros editores más conocidos como pueden ser nano o micro o en un ranking algo superior, Vim.

GNU moe a diferencia de Vim, no es un editor modal. Es decir no dispone de modos de utilización del editor. Según abres un archivo en él podrás empezar a editar, añadir o quitar texto. Es un editor que lo que ves es lo que tienes y puedes editar texto fácilmente.

GNU moe dispone de un buen número de opciones y herramientas que se espera de un editor de texto. Todas esas herramientas se invocan mediante el uso de atajos de teclado utilizando las teclas Alt , Ctrl o Tab del teclado combinadas con otras teclas.

La tecla Alt junto con las diferentes combinaciones de teclas, están reservadas para las acciones menos peligrosas a la hora de editar texto: moverte por el texto, marcar un texto, etc.

La tecl Ctrl junto con sus opciones ya realizan acciones sobre el propio texto, para copiarlo, borrarlo, etc.

La tecla Tab sirve para autocompletar nombres de archivos.

Pero muchas de las opciones más frecuentes están disponibles con un solo dedo usando las teclas de función del teclado.

Por ejemplo, como es casi normal en mucho otro software, con la tecla de función F1 accedes a la ayuda propia a la hora de utilizar GNU moe. F2 guarda el contenido del archivo, etc…

Puedes trabajar con varios textos a la vez, múltiples ventanas, buscar y sustituir texto en varios archivos, etc.

Al abrirlo, ya sea con un archivo o sin nada, nos mostrará en la parte superior una barra de estado que nos muestra información:

• El estado del teclado. Muestra la parte ya escrita de un comando de múltiples teclas, o ‘<‘ para indicar que hay columnas de texto a la izquierda de la ventana.
• El de estado de los caracteres. ‘I’ para el modo de inserción, ‘O’ para el modo de sobrescritura, ‘W’ para ajuste de texto, ‘A’ para sangría automática, ‘R’ para solo lectura y ‘X’ para el modo de bloque rectangular.
• El nombre del archivo que se está editando, o ‘(unnamed)’ si el búfer aún no tiene nombre. Si el búfer se ha modificado desde la última vez que se guardó o abrió, se muestra un asterisco ‘*’ antes del nombre y ‘(Modified)’ después del nombre.
• La posición del cursor en el búfer (columna de línea).
• Un reloj
• La tecla de ayuda, o el código del carácter debajo del cursor, o la posición de la línea del cursor en el búfer.

Puedes abrir el editor vacío y empezar a escribir y guardarlo en un archivo, un archivo ya creado que quieras modificar o abrir un directorio y lo que hará será abrir de manera recursiva todos los archivos que haya dentro.

Puedes crear un archivo de configuración del editor, en el que configures a tu gusto las diferentes opciones del editor, cambiando las opciones predeterminadas por otras que tu prefieras.

Te animo a que explores este editor de texto del proyecto GNU si no lo conocías y que veas por ti mismo todo lo que ofrece, igual se convierte en ¡tu próximo editor de texto preferido!

Enlaces de interés

• https://www.gnu.org/software/moe/moe_es.html
• https://www.gnu.org/software/moe/manual/moe_manual.html
• https://lists.gnu.org/archive/html/bug-moe/2024-01/msg00000.html

El trabajo se acumula y debo dar con temas ligeros para el blog, como sueles ser los estéticos. Hoy os traigo los cursores Hatsune Miku, una forma diferente de interacionar con nuestro entorno de trabajo basado en una cantante virtual japonesa.

Cursores Hatsune Miku para tu PC, dale un toque exótico a tu escritorio

Mofificados de la mano y de la mente de Supermariofps os traigo una serie de cursores para nuestro PC que llevan por nombre Miku en honor a (Según la Wikipedia) Hatsune Miku, una cantante virtual creada para el software VOCALOID desarrollado por la empresa Yamaha Corporation, VOCALOID2, VOCALOID3 y VOCALOID4, así como para el programa desarrollado por Crypton Future Media, Piapro Studio.

La imagen de esta cantantes es una chica de antropomorfismo moe de 16 años es la que ha inspirado al creador original de los cursores (love0922c的小屋) y Supermariofps los ha adaptado y mejorado para entornos Linux.

Y como siempre digo, si os gusta este conjunto de cursores Hatsune Miku podéis «pagarlo» de muchas formas en la página de KDE Store, que estoy seguro que el desarrollador lo agradecer?: puntúale positivamente, hazle un comentario en la página o realiza una donación. Ayudar al desarrollo del Software Libre también se hace simplemente dando las gracias, ayuda mucho más de lo que os podéis imaginar, recordad la campaña I love Free Software Day 2017 de la Free Software Foundation donde se nos recordaba esta forma tan sencilla de colaborar con el gran proyecto del Software Libre y que en el blog dedicamos un artículo.

Más información: KDE Store

Cómo cambiar el tema de los cursores en Plasma

Al igual que con los iconos hay varias formas de cambiar el tema de cursores en Plasma, pero la más fácil es:

• Abrir las Preferencias del Sistema
• Ir a la sección Tema de Cursor
• En esta ventana pinchar en «Obtener nuevos temas»
• Buscar Hatsune Miku, seleccionar el estilo y dar a instalar.
• Seleccionar el tema y aplicar.

Si tenéis dificultad, simplemente se debe descargar a tu disco duro y extraer el tema en «/usr/share/icons» o «~/.icons».

Rápido, sencillo y efectivo, como la mayoría de cosas en en el escritorio Plasma de la Comunidad KDE.

La entrada Cursores Hatsune Miku para tu PC, dale un toque exótico a tu escritorio se publicó primero en KDE Blog.

The openSUSE Project is asking interested people to submit a call for hosts for the openSUSE Conference 2025.

This event is a cornerstone of the openSUSE community and aims to bring together a diverse group of users, developers and enthusiasts to share, learn and collaborate. The aim is not only to strengthen the existing community but also to welcome new members into the fold.

Having the conference in different locations allows the project to be more accessible to people and can help with increasing awareness about the openSUSE Project and open source. While the project is unable to commit to a host being selected based on the project’s available funds, participants in the community encourage people/groups to provide a submission. This will let members of the community discover areas where the project can have a conference if funding allows it.

What We Are Looking For

Hosting the openSUSE Conference is an opportunity to showcase your community and city. The project seeks passionate teams who can address the following key criteria in their submissions:

• New Attendees: Strategies to attract and engage new participants.
• Accessibility: Ensuring the venue and events are accessible to all.
• Community Involvement: Hosts must attend community meetings and provide regular updates if selected.
• Cost Efficiency: Detailed budget plan showing the total cost to run the event.
• Community Growth Goal: A plan to make the conference as successful as previous ones in gaining new members.
• Engaging Educational Institutions: Technical universities and educational bodies willing to host an openSUSE Conference is an ideal demographic for a submission.
• Bidding Process: Similar to the Debian Conference Bidding Process proposals will be submitted via openSUSE Wiki pages. There is a potential that it can be followed by a community voting process.
• Submission Period: Please refer to the openSUSE Conference wiki for detailed timeline and submission deadline.
• Season Flexibility: The event can be planned for any season, allowing flexibility for the hosts.

How to Submit Your Proposal

• Prepare Your Proposal: Detailing how you’ll address the above criteria.
• Submit on openSUSE Wiki: Create a dedicated page for your bid on the openSUSE Wiki and use the template provided at en.opensuse.org/openSUSE:Call_for_hosts to assist with developing the proposal.
• Community Voting: The final selection will involve a voting process by the openSUSE community.

Why Host the openSUSE Conference?

Hosting the openSUSE Conference can spotlight your local community. It’s an opportunity to contribute to the growth of the project.

More Information and Submission Guidelines

Visit the conference checklist for more information on guidelines to help host an openSUSE Conference.

The openSUSE Project is asking interested people to submit a call for hosts for the openSUSE Conference 2025.

This event is a cornerstone of the openSUSE community and aims to bring together a diverse group of users, developers and enthusiasts to share, learn and collaborate. The aim is not only to strengthen the existing community but also to welcome new members into the fold.

Having the conference in different locations allows the project to be more accessible to people and can help with increasing awareness about the openSUSE Project and open source. While the project is unable to commit to a host being selected based on the project’s available funds, participants in the community encourage people/groups to provide a submission. This will let members of the community discover areas where the project can have a conference if funding allows it.

What We Are Looking For

Hosting the openSUSE Conference is an opportunity to showcase your community and city. The project seeks passionate teams who can address the following key criteria in their submissions:

• New Attendees: Strategies to attract and engage new participants.
• Accessibility: Ensuring the venue and events are accessible to all.
• Community Involvement: Hosts must attend community meetings and provide regular updates if selected.
• Cost Efficiency: Detailed budget plan showing the total cost to run the event.
• Community Growth Goal: A plan to make the conference as successful as previous ones in gaining new members.
• Engaging Educational Institutions: Technical universities and educational bodies willing to host an openSUSE Conference is an ideal demographic for a submission.
• Bidding Process: Similar to the Debian Conference Bidding Process proposals will be submitted via openSUSE Wiki pages. There is a potential that it can be followed by a community voting process.
• Submission Period: Please refer to the openSUSE Conference wiki for detailed timeline and submission deadline.
• Season Flexibility: The event can be planned for any season, allowing flexibility for the hosts.

How to Submit Your Proposal

• Prepare Your Proposal: Detailing how you’ll address the above criteria.
• Submit on openSUSE Wiki: Create a dedicated page for your bid on the openSUSE Wiki and use the template provided at en.opensuse.org/openSUSE:Call_for_hosts to assist with developing the proposal.
• Community Voting: The final selection will involve a voting process by the openSUSE community.

Why Host the openSUSE Conference?

Hosting the openSUSE Conference can spotlight your local community. It’s an opportunity to contribute to the growth of the project.

More Information and Submission Guidelines

Visit the conference checklist for more information on guidelines to help host an openSUSE Conference.

The [openSUSE Project(https://www.opensuse.org/) is asking interested people to submit a call for hosts for the openSUSE Conference 2025. This event is a cornerstone of the openSUSE community and aims to bring together a diverse group of users, developers and enthusiasts to share, learn and collaborate. The aim is not only to strengthen the existing community but also to welcome new members into the fold.

Having the conference in different locations allows the project to be more accessible to people and can help with increasing awareness about the openSUSE Project and open source. While the project is unable to commit to a host being selected based on the project’s available funds, participants in the community encourage people/groups to provide a submission. This will let members of the community discover areas where the project can have a conference if funding allows it.

What We Are Looking For

Hosting the openSUSE Conference is an opportunity to showcase your community and city. The project seeks passionate teams who can address the following key criteria in their submissions:

• New Attendees: Strategies to attract and engage new participants.
• Accessibility: Ensuring the venue and events are accessible to all.
• Community Involvement: Hosts must attend community meetings and provide regular updates if selected.
• Cost Efficiency: Detailed budget plan showing the total cost to run the event.
• Community Growth Goal: A plan to make the conference as successful as previous ones in gaining new members.
• Engaging Educational Institutions: Technical universities and educational bodies willing to host an openSUSE Conference is an ideal demographic for a submission.
• Bidding Process: Similar to the Debian Conference Bidding Process proposals will be submitted via openSUSE Wiki pages. There is a potential that it can be followed by a community voting process.
• Submission Period: Please refer to the openSUSE Conference wiki for detailed timeline and submission deadline.
• Season Flexibility: The event can be planned for any season, allowing flexibility for the hosts.

How to Submit Your Proposal

• Prepare Your Proposal: Detailing how you’ll address the above criteria.
• Submit on openSUSE Wiki: Create a dedicated page for your bid on the openSUSE Wiki and use the template provided at en.opensuse.org/openSUSE:Call_for_hosts to assist with developing the proposal.
• Community Voting: The final selection will involve a voting process by the openSUSE community.

Why Host the openSUSE Conference?

Hosting the openSUSE Conference can spotlight your local community. It’s an opportunity to contribute to the growth of the project.

More Information and Submission Guidelines

Visit the conference checklist for more information on guidelines to help host an openSUSE Conference.