Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] TestFileCapabilities is broken
Date: Sun, 14 Oct 2018 16:26:32 +0200	[thread overview]
Message-ID: <20181014142632.GJ31509@scaer> (raw)
In-Reply-To: <20181014152543.2cf6c0b2@windsurf>

Thomas, All,

On 2018-10-14 15:25 +0200, Thomas Petazzoni spake thusly:
> The TestFileCapabilities test of our test suite is failing, with:
> 
> ======================================================================
> FAIL: test_run (tests.core.test_file_capabilities.TestFileCapabilities)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/builds/buildroot.org/buildroot/support/testing/tests/core/test_file_capabilities.py", line 44, in test_run
>     self.assertIn("cap_kill", output[0])
> AssertionError: 'cap_kill' not found in '/usr/sbin/getcap'
> 
> I did a local build, and I can reproduce the issue. What we do is we
> run "getcap -v /usr/sbin/getcap" on the target, and it returns just:
> 
> # getcap -v /usr/sbin/getcap 
> /usr/sbin/getcap
> 
> And not any of the extended attributes that getcap is supposed to have.
> I had a quick look, and makedevs gets run with a correct device table
> when generating the common tarball. I don't know when extended
> attributes are lost.
> 
> Could you have a look ?

So, I also did a test build here, and it indeed fails for me too. At
first glance, our mksquashfs has support for extended attributes:

    $ ./tests/TestFileCapabilities/host/bin/mksquashfs -h
    [...]
    -no-xattrs              don't store extended attributes
    -xattrs                 store extended attributes (default)
    [...]

Further investigation postponed, for cause of a visitor... ;-]

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-10-14 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-14 13:25 [Buildroot] TestFileCapabilities is broken Thomas Petazzoni
2018-10-14 14:26 ` Yann E. MORIN [this message]
2018-10-14 14:47   ` Ricardo Martincoski
2018-10-21  9:17     ` Yann E. MORIN

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=20181014142632.GJ31509@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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