Your message dated Thu, 17 Jan 2019 14:11:30 +0000
with message-id 
<1547734290.2316275.1637109944.09160...@webmail.messagingengine.com>
and subject line Re: Bug#919531: lintian: "Could not determine what you meant 
by: tag:foo"
has caused the Debian Bug report #919531,
regarding lintian: "Could not determine what you meant by: tag:foo"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
919531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919531
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lintian
Version: 2.5.121
Severity: normal
X-Debbugs-Cc: Felix Lechner <[email protected]>

Hi Felix,

Another test regression I'm afraid...

This works:

    $ debian/rules runtests onlyrun=tag:wrong-path-for-interpreter
    .... running tests ....
    mkdir -p "/home/lamby/git/debian/lintian/lintian/debian/test-out"
    t/runtests -k -j 9 t 
"/home/lamby/git/debian/lintian/lintian/debian/test-out" 
tag:wrong-path-for-interpreter
    Host architecture is amd64.
    Latest policy version is 4.3.0 from Sun, 23 Dec 2018 10:17:55 +0000
    Using compat level 11 as a default for packages built with debhelper.
    Harness modified on Wed, 16 Jan 2019 22:45:20 +0000
    Lintian modified on Wed, 16 Jan 2019 22:45:45 +0000

    Environment:
        DEB_HOST_ARCH=amd64
        DEFAULT_DEBHELPER_COMPAT=11
        DUMP_LOGS=yes
        HARNESS_EPOCH=1547678720
        IPCRUNDEBUG=none
        
LINTIAN_DPLINT_FRONTEND=/home/lamby/git/debian/lintian/lintian/frontend/dplint
        LINTIAN_EPOCH=1547678745
        LINTIAN_FRONTEND=/home/lamby/git/debian/lintian/lintian/frontend/lintian
        LINTIAN_ROOT=/home/lamby/git/debian/lintian/lintian
        LINTIAN_TEST_INSTALLED=no
        LINTIAN_TEST_ROOT=/home/lamby/git/debian/lintian/lintian
        NO_PKG_MANGLE=true
        
PATH=/home/lamby/git/debian/lintian/lintian/t/helpers/bin:/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/lamby/.bashhub/bin
        POLICY_EPOCH=1545560275
        POLICY_VERSION=4.3.0
        TEST2_ACTIVE=1
        TEST_ACTIVE=1

    Preparing 3 work directories.

    t/harness/check-result.t ...................................... ok      
    t/harness/no-watch-file-in-native.t ........................... ok      
    t/harness/watch-file-in-non-native.t .......................... ok      
    debian/test-out/tests/scripts-control-interpreters/generic.t .. ok      
    t/harness/logged-prepare.t .................................... ok      
    debian/test-out/tests/legacy-scripts/generic.t ................ ok      
    debian/test-out/tests/scripts-interpreters/generic.t .......... ok
    All tests successful.
    Files=7, Tests=35,  0 wallclock secs ( 0.04 usr  0.01 sys +  1.77 cusr  
0.26 csys =  2.08 CPU)
    Result: PASS

… but this does not:

    $ debian/rules runtests 
onlyrun=tag:package-contains-real-file-outside-of-usr 
    .... running tests ....
    mkdir -p "/home/lamby/git/debian/lintian/lintian/debian/test-out"
    t/runtests -k -j 9 t 
"/home/lamby/git/debian/lintian/lintian/debian/test-out" 
tag:package-contains-real-file-outside-of-usr
    Host architecture is amd64.
    Latest policy version is 4.3.0 from Sun, 23 Dec 2018 10:17:55 +0000
    Using compat level 11 as a default for packages built with debhelper.
    Harness modified on Wed, 16 Jan 2019 22:45:20 +0000
    Lintian modified on Wed, 16 Jan 2019 22:45:45 +0000

    Environment:
        DEB_HOST_ARCH=amd64
        DEFAULT_DEBHELPER_COMPAT=11
        DUMP_LOGS=yes
        HARNESS_EPOCH=1547678720
        IPCRUNDEBUG=none
        
LINTIAN_DPLINT_FRONTEND=/home/lamby/git/debian/lintian/lintian/frontend/dplint
        LINTIAN_EPOCH=1547678745
        LINTIAN_FRONTEND=/home/lamby/git/debian/lintian/lintian/frontend/lintian
        LINTIAN_ROOT=/home/lamby/git/debian/lintian/lintian
        LINTIAN_TEST_INSTALLED=no
        LINTIAN_TEST_ROOT=/home/lamby/git/debian/lintian/lintian
        NO_PKG_MANGLE=true
        
PATH=/home/lamby/git/debian/lintian/lintian/t/helpers/bin:/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/lamby/.bashhub/bin
        POLICY_EPOCH=1545560275
        POLICY_VERSION=4.3.0
        TEST2_ACTIVE=1
        TEST_ACTIVE=1


    t/harness/check-result.t .............. ok                              
    t/harness/no-watch-file-in-native.t ... ok                              
    t/harness/watch-file-in-non-native.t .. ok                              
    t/harness/logged-prepare.t ............ ok     
    All tests successful.
    Files=4, Tests=32,  1 wallclock secs ( 0.02 usr  0.01 sys +  0.55 cusr  
0.09 csys =  0.67 CPU)
    Result: PASS

    Could not determine what you meant by:

        tag:package-contains-real-file-outside-of-usr

    To select your tests, please use an appropriate argument with a
    selector like:

        'suite:', 'test:', 'check:', 'tag:', or 'script:'

    You can also use 'harness:', which runs only the internal tests
    for the harness.

    $ echo $?

Note that:

 * This second tag only exists in Git.

 * The UNIX exit code is wrong or at least grossly misleading.


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      [email protected] / chris-lamb.co.uk
       `-

--- End Message ---
--- Begin Message ---
Hi Felix,

> Please see this MR for a fix:
> https://salsa.debian.org/lintian/lintian/merge_requests/129

Oh! It wasn't really a bug in the test runner after all; it was me
failing at filling out the `desc`. I'm going to go-ahead and close
this directly now...

Thanks. :)


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      [email protected] 🍥 chris-lamb.co.uk
       `-

--- End Message ---

Reply via email to