[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] Software versions in my production chroot
From: |
Greg Chicares |
Subject: |
Re: [lmi] Software versions in my production chroot |
Date: |
Thu, 18 Nov 2021 01:58:46 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 |
On 11/15/21 9:45 PM, Vadim Zeitlin wrote:
> On Mon, 15 Nov 2021 21:23:03 +0000 Greg Chicares <gchicares@sbcglobal.net>
> wrote:
[...anomalous results in an anomalously-maintained chroot...]
> GC> This situation has arisen through a reluctance to upgrade often.
>
> It's not just that, it's also the fact that you seem to have never done a
> full upgrade (as in "apt full-upgrade" or "apt dist-upgrade") at all. Which
> means that you have a highly hybridized system
TL;DR: I find no anomaly in a dist-upgraded bullseye chroot,
so we're all done here, and xvfb is working just fine.
In more detail: Remembering that I had a spare bullseye chroot,
I upgraded it:
$schroot --chroot=chroot:lmi_bullseye_3 --user=root
#apt-get update
#apt-get dist-upgrade
#apt-get autoremove
and then installed packages recently added to the 'lmi_setup_20.sh' list:
#apt-get install xvfb x11-apps clang
and re-ran 'dist-upgrade' just to show everything's clean:
#apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Then, reentering that chroot as a normal user:
$cd /opt/lmi/src/lmi
$git pull
$env |grep SCHROOT_CHROOT_NAME
SCHROOT_CHROOT_NAME=lmi_bullseye_3
The non-xvfb GUI test runs exactly as expected:
$time /opt/lmi/src/lmi/gui_test.sh
NOTE: starting the test suite
SUCCESS: 21 tests successfully completed.
NOTE: 4 tests were skipped
/opt/lmi/src/lmi/gui_test.sh 22.39s user 8.33s system 71% cpu 42.703 total
and the same test runs as expected under xvfb as well:
$time xvfb-run /opt/lmi/src/lmi/gui_test.sh
NOTE: starting the test suite
SUCCESS: 21 tests successfully completed.
NOTE: 4 tests were skipped
X connection to :99 broken (explicit kill or server shutdown).
xvfb-run /opt/lmi/src/lmi/gui_test.sh 27.19s user 11.76s system 37% cpu
1:43.70 total
X connection to :99 broken (explicit kill or server shutdown).
Aside from filtering out that "connection...broken" message
and adding a headless GUI test to the nychthemeral-test script,
we're all done.
- Re: [lmi] Headless GUI tests, Greg Chicares, 2021/11/12
- Re: [lmi] Headless GUI tests, Vadim Zeitlin, 2021/11/13
- Message not available
- Re: [lmi] Headless GUI tests, Greg Chicares, 2021/11/13
- Message not available
- Re: [lmi] Headless GUI tests, Greg Chicares, 2021/11/15
- Re: [lmi] Headless GUI tests, Vadim Zeitlin, 2021/11/15
- Message not available
- [lmi] Software versions in my production chroot [Was: Headless GUI tests], Greg Chicares, 2021/11/15
- Re: [lmi] Software versions in my production chroot, Vadim Zeitlin, 2021/11/15
- Message not available
- Re: [lmi] Software versions in my production chroot,
Greg Chicares <=
- Re: [lmi] Headless GUI tests on corporate server, Greg Chicares, 2021/11/13
- Re: [lmi] Headless GUI tests on corporate server, Vadim Zeitlin, 2021/11/13
- Message not available
- Re: [lmi] Headless GUI tests on corporate server, Greg Chicares, 2021/11/13
- Re: [lmi] Headless GUI tests on corporate server, Vadim Zeitlin, 2021/11/13
- [lmi] Xvfb and xvfb-run defaults differ [Was: Headless GUI tests on corporate server], Greg Chicares, 2021/11/14