http://bugzilla.opensuse.org/show_bug.cgi?id=1077600 http://bugzilla.opensuse.org/show_bug.cgi?id=1077600#c3 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freek@opensuse.org, | |kvm-bugs@forge.provo.novell | |.com, matz@suse.com, | |rguenther@suse.com Hardware|Other |aarch64 Flags| |needinfo?(freek@opensuse.or | |g) --- Comment #3 from Dr. Werner Fink --- AFAICS that is aarch64 only (bug settings corrected) ... if this is true than the question rises if this is an emulated system (VM/qemu-arch64) or a real iron/hardware system based on aarch64 ... next is it could be a gcc problem as well as I had seen last time a lot of build error for aarch64 not only with ncurses but also with other packages I'm maintaining. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1077600 http://bugzilla.opensuse.org/show_bug.cgi?id=1077600#c5 Freek de Kruijf changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(freek@opensuse.or | |g) | --- Comment #5 from Freek de Kruijf --- (In reply to Dr. Werner Fink from comment #3)

AFAICS that is aarch64 only (bug settings corrected) ... if this is true than the question rises if this is an emulated system (VM/qemu-arch64) or a real iron/hardware system based on aarch64 ... next is it could be a gcc problem as well as I had seen last time a lot of build error for aarch64 not only with ncurses but also with other packages I'm maintaining.

On https://build.opensuse.org/package/show/Base:System/ncurses I see you recently fixed something and the build for aarch64 has succeeded. So a reschedule for the OpenQA test might be desirable. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1077600 http://bugzilla.opensuse.org/show_bug.cgi?id=1077600#c6 --- Comment #6 from Dr. Werner Fink --- (In reply to Freek de Kruijf from comment #5)

(In reply to Dr. Werner Fink from comment #3)

...

AFAICS that is aarch64 only (bug settings corrected) ... if this is true than the question rises if this is an emulated system (VM/qemu-arch64) or a real iron/hardware system based on aarch64 ... next is it could be a gcc problem as well as I had seen last time a lot of build error for aarch64 not only with ncurses but also with other packages I'm maintaining.

On https://build.opensuse.org/package/show/Base:System/ncurses I see you recently fixed something and the build for aarch64 has succeeded. So a reschedule for the OpenQA test might be desirable.

This does not fix the missing space key ... right? Beside this as pacakge maintainer I've no influence on how fast new ncurses will reach Tumbleweed ;) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1077600 http://bugzilla.opensuse.org/show_bug.cgi?id=1077600#c8 --- Comment #8 from Dr. Werner Fink --- (In reply to Freek de Kruijf from comment #7)

(In reply to Dr. Werner Fink from comment #6)

...

This does not fix the missing space key ... right? Beside this as pacakge maintainer I've no influence on how fast new ncurses will reach Tumbleweed ;)

I don't know. I only noticed that the command clear did not exist, which comes from the ncurses project. The missing space remark comes from Alexander. Was there a missing space in ncurses?

The program /usr/bin/clear is explicit part of ncurses-utils, that is if this program would not be build then the build does simply fail .... the missing space key if that there is no keyboard with that key. In other words, if package ncurses-utils exists on the QA build 20180113 then this is not an error of the package but an error of not be installed on the test scheme for arch64 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1077600 http://bugzilla.opensuse.org/show_bug.cgi?id=1077600#c10 --- Comment #10 from Freek de Kruijf --- (In reply to Alexander Graf from comment #9)

The missing "clear" command is not an issue IIUC - it happens on all OpenQA runs. The problem is that the line after was mistyped. Instead of "|" it was typing ">".

See the following log entry in autoinst.txt:

[2018-01-23T14:40:51.0797 CET] [debug] <<< testapi::type_string(string='(/bin/bash -eox pipefail /tmp/scriptXUeAZ.sh ; echo SCRIPT_FINISHEDXUeAZ-$?-)| tee /dev/ttyAMA0 ', max_interval=250, wait_screen_changes=0, wait_still_screen=0)

and compare it to the graphical output you see before/after the failure.

OK. So when will there be a reschedule of the test. -- You are receiving this mail because: You are on the CC list for the bug.