[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#26211: [PATCH] gnu: networkmanager-qt: Disable a failing test.
From: |
Ludovic Courtès |
Subject: |
bug#26211: [PATCH] gnu: networkmanager-qt: Disable a failing test. |
Date: |
Sat, 25 Mar 2017 15:17:13 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Hi Hartmut,
Hartmut Goebel <address@hidden> skribis:
> The error-message was: "D-Bus library appears to be incorrectly set up;
> failed to read machine uuid: Failed to open '/etc/machine-id':
> No such file or directory".
The output is:
--8<---------------cut here---------------start------------->8---
starting phase `check'
process 2014: D-Bus library appears to be incorrectly set up; failed to read
machine uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
Test project /tmp/guix-build-networkmanager-qt-5.28.0.drv-0/build
Start 1: managertest
1/25 Test #1: managertest ...................... Passed 0.01 sec
Start 2: settingstest
2/25 Test #2: settingstest ..................... Passed 0.01 sec
Start 3: activeconnectiontest
3/25 Test #3: activeconnectiontest .............***Failed 0.81 sec
Start 4: 8021xsettingtest
[...]
96% tests passed, 1 tests failed out of 25
Total Test time (real) = 0.97 sec
The following tests FAILED:
3 - activeconnectiontest (Failed)
Errors while running CTest
phase `check' failed after 1.0 seconds
--8<---------------cut here---------------end--------------->8---
So the failure is the ‘activeconnectiontest’ test, not the D-Bus thing.
Outside the chroot build environment (and outside of ‘guix environment
-C’), this test passes.
When running “ctest --verbose”, we see:
--8<---------------cut here---------------start------------->8---
3: Test command:
/tmp/guix-build-networkmanager-qt-5.28.0.drv-0/build/autotests/activeconnectiontest
3: Test timeout computed to be: 9.99988e+06
3: ********* Start testing of ActiveConnectionTest *********
3: Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 4.9.4)
3: QWARN : ActiveConnectionTest::initTestCase() networkmanager-qt: void
NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&)
Unhandled property "Devices"
3: QWARN : ActiveConnectionTest::initTestCase() networkmanager-qt: virtual
void NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "Carrier"
3: QWARN : ActiveConnectionTest::initTestCase() networkmanager-qt: virtual
void NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "HwAddress"
3: QWARN : ActiveConnectionTest::initTestCase() networkmanager-qt: virtual
void NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "PermHwAddress"
3: QWARN : ActiveConnectionTest::initTestCase() networkmanager-qt: virtual
void NetworkManager::DevicePrivate::propertyChanged(const QString&, const
QVariant&) Unhandled property "Speed"
3: PASS : ActiveConnectionTest::initTestCase()
3: FAIL! : ActiveConnectionTest::testActiveConnection() Compared values are
not the same
3: Actual (activeConnectionStateChangedSpy.count()): 0
3: Expected (1) : 1
3: Loc:
[/tmp/guix-build-networkmanager-qt-5.28.0.drv-0/networkmanager-qt-5.28.0/autotests/activeconnectiontest.cpp(118)]
3: PASS : ActiveConnectionTest::cleanupTestCase()
3: Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 805ms
3: ********* Finished testing of ActiveConnectionTest *********
3/25 Test #3: activeconnectiontest .............***Failed 0.81 sec
--8<---------------cut here---------------end--------------->8---
We can get more details as explained at
<http://doc.qt.io/qt-5/qtest-overview.html> by running:
dbus-launch
/tmp/guix-build-networkmanager-qt-5.28.0.drv-0/build/autotests/activeconnectiontest
-vs
That didn’t really help me though. The strace output shows nothing
obvious either (such uses code looking for actual network interfaces via
/proc/net/dev or using ioctls); it seems the code has complete mocks for
network interfaces and shouldn’t depend on the real network interfaces.
Could be maybe seek advice from upstream?
HTH,
Ludo’.