[opensuse-factory] Status: Tests

newer
[opensuse-factory] Searching for...

Stephan Kulow

29 Jul 2014 29 Jul '14

08:35

Hi, lxde tests fail, e.g.: https://openqa.opensuse.org/tests/15587 xfce tests fail, e.g.: https://openqa.opensuse.org/tests/15588 btrfs on lvm crashes, e.g.: https://openqa.opensuse.org/tests/15588 dual_windows8 tests fail, e.g.: https://openqa.opensuse.org/tests/15550 kde/kwin crashes still more often than it should on kvm: https://openqa.opensuse.org/tests/15550 yast update from 12.3 fails: https://openqa.opensuse.org/tests/15571 console font on live cds hosed: https://openqa.opensuse.org/tests/15518 We need people to look into all of these if we want to get nearer a 13.2 Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Show replies by date

Guido Berhoerster

29 Jul 29 Jul

08:59

* Stephan Kulow [2014-07-29 10:35]:

...

xfce tests fail, e.g.: https://openqa.opensuse.org/tests/15588

The failures seem to be caused by the lack of a lightdm greeter due to the broken update-desktop-files. You need to rebuild lightdm-gtk-greeter or better do a full Factory rebuild since other packages might have been silently corrupted as well. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Stephan Kulow

09:05

On 29.07.2014 10:59, Guido Berhoerster wrote:

...

* Stephan Kulow [2014-07-29 10:35]:

...
xfce tests fail, e.g.: https://openqa.opensuse.org/tests/15588

The failures seem to be caused by the lack of a lightdm greeter due to the broken update-desktop-files. You need to rebuild lightdm-gtk-greeter or better do a full Factory rebuild since other packages might have been silently corrupted as well.

I retriggered the package - I won't do a full rebuild because of one possible bug. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Stephan Kulow

31 Jul 31 Jul

05:14

Am 29.07.2014 10:59, schrieb Guido Berhoerster:

...

* Stephan Kulow [2014-07-29 10:35]:

...
xfce tests fail, e.g.: https://openqa.opensuse.org/tests/15588

The failures seem to be caused by the lack of a lightdm greeter due to the broken update-desktop-files. You need to rebuild lightdm-gtk-greeter or better do a full Factory rebuild since other packages might have been silently corrupted as well.

xfce tests were fixed by the rebuild. The rebuild test results in a black window thought. lxde seems to have another problem. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Guido Berhoerster

07:36

* Stephan Kulow [2014-07-31 07:14]:

...

Am 29.07.2014 10:59, schrieb Guido Berhoerster:

...
* Stephan Kulow [2014-07-29 10:35]:

...
xfce tests fail, e.g.: https://openqa.opensuse.org/tests/15588

The failures seem to be caused by the lack of a lightdm greeter due to the broken update-desktop-files. You need to rebuild lightdm-gtk-greeter or better do a full Factory rebuild since other packages might have been silently corrupted as well.

xfce tests were fixed by the rebuild. The rebuild test results in a black window thought.

No, the greeter works fine now. What fails is the "reboot" test because it is broken, it sends ctrl-alt-delete which locks the screen (hence the black screen) and then seems to expect the kde logout screen. Instead it should send alt-f4 to an empty desktop in order to get to the logout dialog, where do I send corrections now? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Max Lin

07:51

On 07/31/2014 03:36 PM, Guido Berhoerster wrote:

...

* Stephan Kulow [2014-07-31 07:14]:

...
Am 29.07.2014 10:59, schrieb Guido Berhoerster:

...
* Stephan Kulow [2014-07-29 10:35]:

...
xfce tests fail, e.g.: https://openqa.opensuse.org/tests/15588

The failures seem to be caused by the lack of a lightdm greeter due to the broken update-desktop-files. You need to rebuild lightdm-gtk-greeter or better do a full Factory rebuild since other packages might have been silently corrupted as well.

xfce tests were fixed by the rebuild. The rebuild test results in a black window thought.

No, the greeter works fine now. What fails is the "reboot" test because it is broken, it sends ctrl-alt-delete which locks the screen (hence the black screen) and then seems to expect the kde logout screen. Instead it should send alt-f4 to an empty desktop in order to get to the logout dialog, where do I send corrections now?

https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/x11te... Best regards, Max -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Guido Berhoerster

08:35

* Max Lin [2014-07-31 09:51]:

...

On 07/31/2014 03:36 PM, Guido Berhoerster wrote:

...
* Stephan Kulow [2014-07-31 07:14]:

...
Am 29.07.2014 10:59, schrieb Guido Berhoerster:

...
* Stephan Kulow [2014-07-29 10:35]:

...
xfce tests fail, e.g.: https://openqa.opensuse.org/tests/15588

The failures seem to be caused by the lack of a lightdm greeter due to the broken update-desktop-files. You need to rebuild lightdm-gtk-greeter or better do a full Factory rebuild since other packages might have been silently corrupted as well.

xfce tests were fixed by the rebuild. The rebuild test results in a black window thought.

No, the greeter works fine now. What fails is the "reboot" test because it is broken, it sends ctrl-alt-delete which locks the screen (hence the black screen) and then seems to expect the kde logout screen. Instead it should send alt-f4 to an empty desktop in order to get to the logout dialog, where do I send corrections now?

https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/x11te...

Thanks, so the breakage was introduced in https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/8ef8c6b4c8... which changes a bunch of stuff and gives no meaningful explanation, I guess I can partially revert the Xfce changes. I'd like to keep the screenshot check of the logout dialog, how can I define the reference image later? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Stephan Kulow

08:55

On 31.07.2014 10:35, Guido Berhoerster wrote:

...

* Max Lin [2014-07-31 09:51]:

...
On 07/31/2014 03:36 PM, Guido Berhoerster wrote:

...
* Stephan Kulow [2014-07-31 07:14]:

...
Am 29.07.2014 10:59, schrieb Guido Berhoerster:

...
* Stephan Kulow [2014-07-29 10:35]:

...
xfce tests fail, e.g.: https://openqa.opensuse.org/tests/15588

The failures seem to be caused by the lack of a lightdm greeter due to the broken update-desktop-files. You need to rebuild lightdm-gtk-greeter or better do a full Factory rebuild since other packages might have been silently corrupted as well.

xfce tests were fixed by the rebuild. The rebuild test results in a black window thought.

No, the greeter works fine now. What fails is the "reboot" test because it is broken, it sends ctrl-alt-delete which locks the screen (hence the black screen) and then seems to expect the kde logout screen. Instead it should send alt-f4 to an empty desktop in order to get to the logout dialog, where do I send corrections now?

https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/x11te...

Thanks, so the breakage was introduced in https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/8ef8c6b4c8... which changes a bunch of stuff and gives no meaningful explanation, I guess I can partially revert the Xfce changes. I'd like to keep the screenshot check of the logout dialog, how can I define the reference image later?

I can make you operator on openqa.opensuse.org - then you can create them directly in the web frontend. But I don't see a login from you. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Stephan Kulow

29 Jul 29 Jul

09:10

On 29.07.2014 10:35, Stephan Kulow wrote:

...

Hi,

lxde tests fail, e.g.: https://openqa.opensuse.org/tests/15587

xfce tests fail, e.g.: https://openqa.opensuse.org/tests/15588

btrfs on lvm crashes, e.g.: https://openqa.opensuse.org/tests/15588

dual_windows8 tests fail, e.g.: https://openqa.opensuse.org/tests/15550

kde/kwin crashes still more often than it should on kvm: https://openqa.opensuse.org/tests/15550 https://openqa.opensuse.org/tests/15568/modules/first_boot/steps/2

is the correct link. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andrey Borzenkov

09:37

On Tue, Jul 29, 2014 at 12:35 PM, Stephan Kulow wrote:

...

dual_windows8 tests fail, e.g.: https://openqa.opensuse.org/tests/15550

It may be due to Fast Boot enabled in Windows 8 by default (effectively it performs hibernation instead of power off). If test is using Windows image, full shutdown should probably be performed before imaging it (shutdown /s /t 0).

...

console font on live cds hosed: https://openqa.opensuse.org/tests/15518

Looks like console was not put into UTF-8 mode. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Stephan Kulow

09:41

On 29.07.2014 11:37, Andrey Borzenkov wrote:

...

On Tue, Jul 29, 2014 at 12:35 PM, Stephan Kulow wrote:

...
dual_windows8 tests fail, e.g.: https://openqa.opensuse.org/tests/15550

It may be due to Fast Boot enabled in Windows 8 by default (effectively it performs hibernation instead of power off). If test is using Windows image, full shutdown should probably be performed before imaging it (shutdown /s /t 0). The windows image didn't change since Nov 13 and the test worked in June.

Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Arvin Schnell

09:42

On Tue, Jul 29, 2014 at 01:37:09PM +0400, Andrey Borzenkov wrote:

...

On Tue, Jul 29, 2014 at 12:35 PM, Stephan Kulow wrote:

...
dual_windows8 tests fail, e.g.: https://openqa.opensuse.org/tests/15550

It may be due to Fast Boot enabled in Windows 8 by default (effectively it performs hibernation instead of power off). If test is using Windows image, full shutdown should probably be performed before imaging it (shutdown /s /t 0).

The windows partition should be a image that wasn't changed for a long time. Maybe the output of the ntfsresize program has changed so that YaST cannot detect the status. Need YaST logs to check that. Regards, Arvin -- Arvin Schnell, Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Stephan Kulow

09:44

On 29.07.2014 11:42, Arvin Schnell wrote:

...

On Tue, Jul 29, 2014 at 01:37:09PM +0400, Andrey Borzenkov wrote:

...
On Tue, Jul 29, 2014 at 12:35 PM, Stephan Kulow wrote:

...
dual_windows8 tests fail, e.g.: https://openqa.opensuse.org/tests/15550

It may be due to Fast Boot enabled in Windows 8 by default (effectively it performs hibernation instead of power off). If test is using Windows image, full shutdown should probably be performed before imaging it (shutdown /s /t 0).

The windows partition should be a image that wasn't changed for a long time.

Maybe the output of the ntfsresize program has changed so that YaST cannot detect the status. Need YaST logs to check that.

You can get them from the above URL. The last update to ntfs-3g was in april though. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Arvin Schnell

09:54

On Tue, Jul 29, 2014 at 11:44:51AM +0200, Stephan Kulow wrote:

...

On 29.07.2014 11:42, Arvin Schnell wrote:

...
On Tue, Jul 29, 2014 at 01:37:09PM +0400, Andrey Borzenkov wrote:

...
On Tue, Jul 29, 2014 at 12:35 PM, Stephan Kulow wrote:

...
dual_windows8 tests fail, e.g.: https://openqa.opensuse.org/tests/15550

It may be due to Fast Boot enabled in Windows 8 by default (effectively it performs hibernation instead of power off). If test is using Windows image, full shutdown should probably be performed before imaging it (shutdown /s /t 0).

The windows partition should be a image that wasn't changed for a long time.

Maybe the output of the ntfsresize program has changed so that YaST cannot detect the status. Need YaST logs to check that.

You can get them from the above URL. The last update to ntfs-3g was in april though.

The system is EFI so a GPT is needed but the disk has a MSDOS PT. The message about resize problems seems wrong. Regards, Arvin -- Arvin Schnell, Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Jiri Slaby

31 Jul 31 Jul

09:14

On 07/29/2014, 11:54 AM, Arvin Schnell wrote:

...

On Tue, Jul 29, 2014 at 11:44:51AM +0200, Stephan Kulow wrote:

...
On 29.07.2014 11:42, Arvin Schnell wrote:

...
On Tue, Jul 29, 2014 at 01:37:09PM +0400, Andrey Borzenkov wrote:

...
On Tue, Jul 29, 2014 at 12:35 PM, Stephan Kulow wrote:

...
dual_windows8 tests fail, e.g.: https://openqa.opensuse.org/tests/15550

It may be due to Fast Boot enabled in Windows 8 by default (effectively it performs hibernation instead of power off). If test is using Windows image, full shutdown should probably be performed before imaging it (shutdown /s /t 0).

The windows partition should be a image that wasn't changed for a long time.

Maybe the output of the ntfsresize program has changed so that YaST cannot detect the status. Need YaST logs to check that.

You can get them from the above URL. The last update to ntfs-3g was in april though.

The system is EFI so a GPT is needed but the disk has a MSDOS PT.

Correct. Did you start using EFI-capable VM lately? You should perhaps convert the win8 disk to EFI then. I don't know why GPT is required by yast-storage though (maybe it isn't?). regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Stephan Kulow

09:26

On 31.07.2014 11:14, Jiri Slaby wrote:

...

On 07/29/2014, 11:54 AM, Arvin Schnell wrote:

...
On Tue, Jul 29, 2014 at 11:44:51AM +0200, Stephan Kulow wrote:

...
On 29.07.2014 11:42, Arvin Schnell wrote:

...
On Tue, Jul 29, 2014 at 01:37:09PM +0400, Andrey Borzenkov wrote:

...
On Tue, Jul 29, 2014 at 12:35 PM, Stephan Kulow wrote:

...
dual_windows8 tests fail, e.g.: https://openqa.opensuse.org/tests/15550

It may be due to Fast Boot enabled in Windows 8 by default (effectively it performs hibernation instead of power off). If test is using Windows image, full shutdown should probably be performed before imaging it (shutdown /s /t 0).

The windows partition should be a image that wasn't changed for a long time.

Maybe the output of the ntfsresize program has changed so that YaST cannot detect the status. Need YaST logs to check that.

You can get them from the above URL. The last update to ntfs-3g was in april though.

The system is EFI so a GPT is needed but the disk has a MSDOS PT.

Correct. Did you start using EFI-capable VM lately? You should perhaps convert the win8 disk to EFI then.

I don't know why GPT is required by yast-storage though (maybe it isn't?).

The win8 hard drive is only used in dual_windows8 test - and it has always been an EFI test. I don't know how you find out about the disk's partitioning. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Stephan Kulow

09:33

On 31.07.2014 11:26, Stephan Kulow wrote:

...

On 31.07.2014 11:14, Jiri Slaby wrote:

...
On 07/29/2014, 11:54 AM, Arvin Schnell wrote:

...
On Tue, Jul 29, 2014 at 11:44:51AM +0200, Stephan Kulow wrote:

...
On 29.07.2014 11:42, Arvin Schnell wrote:

...
On Tue, Jul 29, 2014 at 01:37:09PM +0400, Andrey Borzenkov wrote:

...
On Tue, Jul 29, 2014 at 12:35 PM, Stephan Kulow wrote: > > dual_windows8 tests fail, e.g.: > https://openqa.opensuse.org/tests/15550 >

It may be due to Fast Boot enabled in Windows 8 by default (effectively it performs hibernation instead of power off). If test is using Windows image, full shutdown should probably be performed before imaging it (shutdown /s /t 0).

The windows partition should be a image that wasn't changed for a long time.

Maybe the output of the ntfsresize program has changed so that YaST cannot detect the status. Need YaST logs to check that.

You can get them from the above URL. The last update to ntfs-3g was in april though.

The system is EFI so a GPT is needed but the disk has a MSDOS PT.

Correct. Did you start using EFI-capable VM lately? You should perhaps convert the win8 disk to EFI then.

I don't know why GPT is required by yast-storage though (maybe it isn't?).

The win8 hard drive is only used in dual_windows8 test - and it has always been an EFI test. I don't know how you find out about the disk's partitioning.

OK, I just checked and it wasn't an EFI test. So I wonder how the EFI boot came into play. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Josef Reidinger

30 Jul 30 Jul

07:50

On Tue, 29 Jul 2014 10:35:26 +0200 Stephan Kulow wrote:

...

Hi,

yast update from 12.3 fails: https://openqa.opensuse.org/tests/15571

Problem with missing updates is that product defines external sources and tries to read repositories from http://download.opensuse.org/YaST/Repos/openSUSE_Factory_Servers.xml but this XML do not exists. So create such file or external sources lives at different location then change it please at https://github.com/yast/skelcd-control-openSUSE/blob/master/control/control.... If you need any help with it, you can reach us on freenode#yast Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hans-Peter Jansen

08:29

On Mittwoch, 30. Juli 2014 09:50:27 Josef Reidinger wrote:

...

On Tue, 29 Jul 2014 10:35:26 +0200

Stephan Kulow wrote:

...
Hi,

yast update from 12.3 fails: https://openqa.opensuse.org/tests/15571

Problem with missing updates is that product defines external sources and tries to read repositories from http://download.opensuse.org/YaST/Repos/openSUSE_Factory_Servers.xml but this XML do not exists.

So create such file or external sources lives at different location then change it please at https://github.com/yast/skelcd-control-openSUSE/blob/master/control/control. openSUSE.xml#L126

Shouldn't yast handle missing external references gracefully? Imagine disconnected scenarios.. Pete

...

If you need any help with it, you can reach us on freenode#yast

Josef

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Josef Reidinger

08:34

On Wed, 30 Jul 2014 10:29:55 +0200 Hans-Peter Jansen wrote:

...

On Mittwoch, 30. Juli 2014 09:50:27 Josef Reidinger wrote:

...
On Tue, 29 Jul 2014 10:35:26 +0200

Stephan Kulow wrote:

...
Hi,

yast update from 12.3 fails: https://openqa.opensuse.org/tests/15571

Problem with missing updates is that product defines external sources and tries to read repositories from http://download.opensuse.org/YaST/Repos/openSUSE_Factory_Servers.xml but this XML do not exists.

So create such file or external sources lives at different location then change it please at https://github.com/yast/skelcd-control-openSUSE/blob/master/control/control. openSUSE.xml#L126

Shouldn't yast handle missing external references gracefully?

Imagine disconnected scenarios..

Pete

Hi Pete, YaST handle disconnected scenario. If it get no answer, then it do no try external repositories, but here it get 404 and xml answer, so it report it as it is indication of problem. Josef

...

...
If you need any help with it, you can reach us on freenode#yast

Josef

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

3564

Age (days ago)

3566

Last active (days ago)

List overview

Download

19 comments

8 participants

participants (8)

Andrey Borzenkov
Arvin Schnell
Guido Berhoerster
Hans-Peter Jansen
Jiri Slaby
Josef Reidinger
Max Lin
Stephan Kulow

[opensuse-factory] Status: Tests

tags

participants (8)