All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Halstead <mhalstead@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/6] oe-selftest: extend virgl gtk test to also check the SDL option
Date: Fri, 8 Nov 2019 10:01:03 -0800	[thread overview]
Message-ID: <CADfgfoac9HKAzqsnGcPqDnCHTvqFQJH854uR3esmJnTkdRLYmg@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj8fQV9vaubTyYF2gzicP3U8w0bZP4Fne91bkRRzPP5hew@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]

On Fri, Nov 8, 2019 at 9:56 AM Alexander Kanavin <alex.kanavin@gmail.com>
wrote:

> On Fri, 8 Nov 2019 at 18:20, Michael Halstead <
> mhalstead@linuxfoundation.org> wrote:
>
>> > If you replace that with tigervnc (a modern, supported fork of
>> tightvnc), then the tests pass fine.
>> > https://tigervnc.org/
>> >
>>
>> TigerVNC is now installed from the standard repos where available.
>>
>> >
>> > As Fedora has already obsoleted tightvnc in favor of tigervnc, I think
>> we should do the same on all debian machines (debian provides both tightvnc
>> and tigervnc, but treats them as equal).
>> > https://src.fedoraproject.org/rpms/tightvnc/blob/master/f/dead.package
>> > I also checked that tightvnc is not available for opensuse either.
>>
>>
>> Server components of TigerVNC are in xorg-x11-Xvnc package which is
>> installed on all the openSUSE workers so I expect the VNC server there to
>> work. Please let me know if they do not.
>>
>>
>> On Ubuntu 16.04 and Debian 8 workers I've installed from
>> https://bintray.com/tigervnc/stable/tigervnc/1.9.0. This should allow
>> tests to complete. Installing packages outside of the distribution's
>> package manager might invalidate these as sanity tested distros. I'd
>> appreciate feedback about this.
>>
>
> Thanks a lot! There are two things to check:
> 1. Old instances of vnc may still be running and should be shut down (via
> 'vncserver -kill :1')
> 2. vncserver executable should point to tigervnc (if both tigervnc and
> tightvnc are installed - I don't know if you removed the tightvnc packages).
>

I removed tightvnc and all workers have been rebooted so we are good to go.

Any comment on using packages from outside of the distro's official
packaging?


>
> Otherwise everything should be ready for re-testing the patches. I can
> resend them if needed.
>
> Alex
>

[-- Attachment #2: Type: text/html, Size: 3021 bytes --]

  reply	other threads:[~2019-11-08 18:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31  9:36 [PATCH 1/6] runqemu: add options that enable virgl with the SDL frontend Alexander Kanavin
2019-10-31  9:36 ` [PATCH 2/6] selftest: skip virgl test on centos 7 entirely Alexander Kanavin
2019-10-31  9:36 ` [PATCH 3/6] oe-selftest: extend virgl gtk test to also check the SDL option Alexander Kanavin
2019-11-01 17:46   ` Ross Burton
2019-11-02 12:07     ` Alexander Kanavin
2019-11-02 22:29       ` Alexander Kanavin
2019-11-04 21:10         ` Alexander Kanavin
2019-11-08 17:20           ` Michael Halstead
2019-11-08 17:55             ` Alexander Kanavin
2019-11-08 18:01               ` Michael Halstead [this message]
2019-11-08 18:16                 ` Alexander Kanavin
2019-10-31  9:36 ` [PATCH 4/6] gcr: update to 3.34.0 Alexander Kanavin
2019-10-31  9:56   ` Andreas Müller
2019-10-31  9:58     ` Alexander Kanavin
2019-10-31 10:02       ` Andreas Müller
2019-10-31  9:36 ` [PATCH 5/6] btrfs-tools: update to 5.3 Alexander Kanavin
2019-10-31  9:36 ` [PATCH 6/6] libmodulemd-v1: update to 1.8.16 Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADfgfoac9HKAzqsnGcPqDnCHTvqFQJH854uR3esmJnTkdRLYmg@mail.gmail.com \
    --to=mhalstead@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.