From: Stephen Smalley <sds@tycho.nsa.gov>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Paul Moore <paul@paul-moore.com>, SElinux list <selinux@vger.kernel.org>
Subject: Re: [PATCH] selinux-testsuite: apply perltidy to infiniband test scripts
Date: Thu, 19 Sep 2019 08:17:14 -0400 [thread overview]
Message-ID: <2ac5eb4d-b44f-bbe2-58fd-8a9c1758e4b9@tycho.nsa.gov> (raw)
In-Reply-To: <CAFqZXNuZ00pFj_vyzJ3W3x2Fbs=NA+NDMCUR9fwpaerUfRU-pQ@mail.gmail.com>
On 9/19/19 3:43 AM, Ondrej Mosnacek wrote:
> On Wed, Sep 18, 2019 at 2:55 PM Stephen Smalley <sds@tycho.nsa.gov> wrote:
>> The infiniband test scripts weren't compliant with perltidy so
>> make check-syntax was failing. Fix it.
>
> Unfortunately there is some disconnect between the perltidy version
> available in the Travis CI environment and the newer versions
> available in more recent distributions... See this commit in the
> audit-testsuite [1] - the decision is to follow the Travis format as
> the common "standard" (there is really no better way until we patch
> the Travis script to install newer peritidy somehow...).
Ok, I reverted this change. Wondering if this could be controlled
through any of the perltidy options, or fixed by using a newer image
e.g. bionic.
> Just in case you don't know, anyone can easily enable Travis CI on
> their GitHub fork - just go to https://travis-ci.org/, log in with
> your GitHub account, and switch the corresponding project to enabled.
> That way you can just push a branch to your fork, it will be tested
> and you will get a report to (just) your mailbox. I.e. you can do the
> canonical syntax check without opening a PR against the upstream repo.
>
> [1] https://github.com/linux-audit/audit-testsuite/commit/7ff3e434bc243e667ebb26a22b64176e662fddec
>
>>
>> Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
>> ---
>> tests/infiniband_endport/test | 2 +-
>> tests/infiniband_pkey/test | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/tests/infiniband_endport/test b/tests/infiniband_endport/test
>> index 0021e0d69af4..f071fbc18cf8 100755
>> --- a/tests/infiniband_endport/test
>> +++ b/tests/infiniband_endport/test
>> @@ -40,7 +40,7 @@ ok( $result, 0 );
>>
>> foreach (@denied_device_port) {
>> @dev_port_pair = split( / /, $_ );
>> - $result = system
>> + $result = system
>> "runcon -t test_ibendport_manage_subnet_t smpquery PKeyTable -C $dev_port_pair[0] -P $dev_port_pair[1] -D 1 2>/dev/null";
>>
>> if ( $result >> 8 eq 0 ) {
>> diff --git a/tests/infiniband_pkey/test b/tests/infiniband_pkey/test
>> index 3ee4d13c8ffe..382c25913ca0 100755
>> --- a/tests/infiniband_pkey/test
>> +++ b/tests/infiniband_pkey/test
>> @@ -32,7 +32,7 @@ close($f);
>>
>> # The gid sysfs shows a fully expanded ipv6 address, just take the
>> # top half.
>> -@tmp = unpack( '(a20)*', $gid );
>> +@tmp = unpack( '(a20)*', $gid );
>> $subnet_prefix = $tmp[0] . ":";
>>
>> @labeled_pkeys = split( /,/, $conf{SELINUX_INFINIBAND_TEST_LABELED_PKEYS} );
>> --
>> 2.21.0
>>
>
next prev parent reply other threads:[~2019-09-19 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 12:55 [PATCH] selinux-testsuite: apply perltidy to infiniband test scripts Stephen Smalley
2019-09-19 7:43 ` Ondrej Mosnacek
2019-09-19 12:17 ` Stephen Smalley [this message]
2019-09-19 12:47 ` Ondrej Mosnacek
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=2ac5eb4d-b44f-bbe2-58fd-8a9c1758e4b9@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).