Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 525896 - app-portage/layman-2.2.0-r7 fails tests
Summary: app-portage/layman-2.2.0-r7 fails tests
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Third-Party Tools (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Layman Overlay Manager project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-19 19:33 UTC by tka
Modified: 2016-05-10 04:40 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tka 2014-10-19 19:33:22 UTC
This seems to be related to the commit message:
*layman-2.2.0-r5

  18 Oct 2014; Devan Franchini <twitch153@gentoo.org> +layman-2.2.0-r5.ebuild,
  -layman-2.2.0-r4.ebuild, files/layman-2.2.0-removes-doctest-remnants.patch:
  Removes dtest.py in src_prepare() instead of patch, bug #525806


>>> Test phase: app-portage/layman-2.2.0-r5
 * python3_3: running distutils-r1_run_phase python_test
 * python2_7: running distutils-r1_run_phase python_test
/usr/bin/python2.7: can't open file 'layman/tests/dtest.py': [Errno 2] No such file or directory
 * ERROR: app-portage/layman-2.2.0-r5::gentoo failed (test phase):
 *   test suite 'layman/tests/dtest.py' failed
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_test
 *   environment, line 4344:  Called distutils-r1_src_test
 *   environment, line 1416:  Called _distutils-r1_run_foreach_impl 'python_test'
/usr/bin/python3.3: can't open file 'layman/tests/dtest.py': [Errno 2] No such file or directory
 * ERROR: app-portage/layman-2.2.0-r5::gentoo failed (test phase):
 *   environment, line  292:  Called python_parallel_foreach_impl 'distutils-r1_run_phase' 'python_test'
 *   test suite 'layman/tests/dtest.py' failed
 * 
 * Call stack:
 *   environment, line 4099:  Called multibuild_parallel_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_test'
 *     ebuild.sh, line   93:  Called src_test
 *   environment, line 3097:  Called multibuild_foreach_variant '_multibuild_parallel' '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_test'
 *   environment, line 4344:  Called distutils-r1_src_test
 *   environment, line 3040:  Called _multibuild_run '_multibuild_parallel' '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_test'
 *   environment, line 1416:  Called _distutils-r1_run_foreach_impl 'python_test'
 *   environment, line 3038:  Called _multibuild_parallel '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_test'
 *   environment, line  292:  Called python_parallel_foreach_impl 'distutils-r1_run_phase' 'python_test'
 *   environment, line 3088:  Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'python_test'
 *   environment, line 4099:  Called multibuild_parallel_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_test'
 *   environment, line  726:  Called distutils-r1_run_phase 'python_test'
 *   environment, line 3097:  Called multibuild_foreach_variant '_multibuild_parallel' '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_test'
 *   environment, line 1351:  Called python_test
 *   environment, line 4152:  Called die
 *   environment, line 3040:  Called _multibuild_run '_multibuild_parallel' '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_test'
 * The specific snippet of code:
 *   environment, line 3038:  Called _multibuild_parallel '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_test'
 *   environment, line 3088:  Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'python_test'
 *   environment, line  726:  Called distutils-r1_run_phase 'python_test'
 *   environment, line 1351:  Called python_test
 *   environment, line 4152:  Called die
 * The specific snippet of code:
 *           PYTHONPATH="." "${PYTHON}" ${suite} || die "test suite '${suite}' failed";
 * 
 * If you need support, post the output of `emerge --info '=app-portage/layman-2.2.0-r5::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-portage/layman-2.2.0-r5::gentoo'`.
/usr/lib/portage/python3.3/isolated-functions.sh: line 195: wait: `test suite 'layman/tests/dtest.py' failed': not a pid or valid job spec
 * The complete build log is located at '/var/tmp/portage/app-portage/layman-2.2.0-r5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-portage/layman-2.2.0-r5/temp/environment'.
 * Working directory: '/var/tmp/portage/app-portage/layman-2.2.0-r5/work/layman-2.2.0'
 * S: '/var/tmp/portage/app-portage/layman-2.2.0-r5/work/layman-2.2.0'
 *           PYTHONPATH="." "${PYTHON}" ${suite} || die "test suite '${suite}' failed";
 * 
 * If you need support, post the output of `emerge --info '=app-portage/layman-2.2.0-r5::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-portage/layman-2.2.0-r5::gentoo'`.
/usr/lib/portage/python3.3/isolated-functions.sh: line 195: wait: `test suite 'layman/tests/dtest.py' failed': not a pid or valid job spec
 * The complete build log is located at '/var/tmp/portage/app-portage/layman-2.2.0-r5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-portage/layman-2.2.0-r5/temp/environment'.
 * Working directory: '/var/tmp/portage/app-portage/layman-2.2.0-r5/work/layman-2.2.0'
 * S: '/var/tmp/portage/app-portage/layman-2.2.0-r5/work/layman-2.2.0'
/usr/lib/portage/python3.3/isolated-functions.sh: line 226: kill: (19605) - No such process

>>> Failed to emerge app-portage/layman-2.2.0-r5, Log file:

Reproducible: Always
Comment 1 Patrick Lauer gentoo-dev 2015-01-17 09:56:36 UTC
+  17 Jan 2015; Patrick Lauer <patrick@gentoo.org> layman-2.2.0-r7.ebuild:
+  Fix #525896, tests now actually run and fail
Comment 2 Patrick Lauer gentoo-dev 2015-01-17 09:59:07 UTC
======================================================================
ERROR: test (__main__.AddDeleteEnableDisableFromDB)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "layman/tests/external.py", line 99, in test
    if False in conf_success:
TypeError: argument of type 'bool' is not iterable

======================================================================
FAIL: test (__main__.CLIArgs)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "layman/tests/external.py", line 276, in test
    self.assertEqual(sorted(a.keys()), test_keys)
AssertionError: Lists differ: ['auto_sync', 'bzr_addopts', '... != ['auto_sync', 'bzr_addopts', '...

First differing element 6:
check_official
clean_tar

First list contains 5 additional elements.
First extra element 66:
t/f_options

Diff is 1444 characters long. Set self.maxDiff to None to see it.

======================================================================
FAIL: test (__main__.MakeOverlayXML)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "layman/tests/external.py", line 453, in test
    self.assertEqual(xml.readlines()[9], test_line)
AssertionError: '  </repo>\n' != '    <source type="svn">https://overlays.gentoo.org/svn/dev/wrobel</source>\n'
-   </repo>
+     <source type="svn">https://overlays.gentoo.org/svn/dev/wrobel</source>


----------------------------------------------------------------------
Ran 13 tests in 0.807s

FAILED (failures=2, errors=1)
<?xml version="1.0" encoding="UTF-8"?>
<repositories xmlns="" version="1.0">
  <repo quality="experimental" status="unofficial">
    <name>squashfs-test-overlay</name>
    <description>XXXXXXXXXXX</description>
    <owner>
      <email>foo@example.org</email>
    </owner>
    <source type="squashfs">file:///chroot/tmpdir/portage/app-portage/layman-2.2.0-r7/temp/tmp204z5k</source>
  </repo>
</repositories>
        
 * Running mount... # /bin/mount -o loop -t squashfs /chroot/tmpdir/portage/app-portage/layman-2.2.0-r7/temp/tmp204z5k /chroot/tmpdir/portage/app-portage/layman-2.2.0-r7/temp/tmpe9_562/squashfs-test-overlay
 * Failure result returned from mount


[snip]

 * ERROR: app-portage/layman-2.2.0-r7::gentoo failed (test phase):
 *   test suite 'layman/tests/external.py' failed

So with py3 it fails, and it tries to use squashfs which relies on kernel support that maybe isn't there.
Comment 3 Devan Franchini (RETIRED) gentoo-dev 2015-01-25 03:42:33 UTC
Both of these issues have been fixed and on the repo's master branch. A new release of layman will be out soon, I've been pushing it back due to other work though.
Comment 4 Devan Franchini (RETIRED) gentoo-dev 2016-05-10 04:40:25 UTC
2.4.1 is out which resolves this issue, therefore, I'm resolving the bug.