From: jeffrin@rajagiritech.edu.in (Jeffrin Thalakkottoor)
Subject: possible BUG: selftests: proc-loadavg-001 failed during kernel testing
Date: Sun, 22 Apr 2018 02:11:05 +0530 [thread overview]
Message-ID: <CAG=yYwnsP5w6hKqsp0Q3_DZO3JZmtStGwnXNZN9zjPuFe8fOeA@mail.gmail.com> (raw)
Message-ID: <20180421204105.dobiA82OE-YjaXXD-lOU6fAgzfuwfOwVq0iXJ2Hni3U@z> (raw)
This problem is fixed now.
$sudo make -C tools/testing/selftests/proc run_tests
[sudo] password for jeffrin:
make: Entering directory
'/home/jeffrin/upstream-kernel/linux/tools/testing/selftests/proc'
TAP version 13
selftests: proc-loadavg-001
========================================
ok 1..1 selftests: proc-loadavg-001 [PASS]
Please add me in changelog if i was useful.
On Sat, Apr 21, 2018 at 8:41 PM, Jeffrin Thalakkottoor
<jeffrin@rajagiritech.edu.in> wrote:
> hello,
>
> selftests: proc-loadavg-001
> ========================================
> not ok 1..1 selftests: proc-loadavg-001 [FAIL]
>
> To reproduce :
> make -C tools/testing/selftests/proc run_tests
>
> Linux debian 4.17.0-rc1+ #3 SMP Sat Apr 21 03:41:44 IST 2018 x86_64 GNU/Linux
>
> GNU Make 4.2.1
> Binutils 2.30
> Util-linux 2.31.1
> Mount 2.31.1
> Linux C Library 2.27
> Dynamic linker (ldd) 2.27
> readlink: missing operand
> Try 'readlink --help' for more information.
> Procps 3.3.14
> Kbd 2.0.4
> Console-tools 2.0.4
> Sh-utils 8.28
> Udev 238
>
>
>
> --
> software engineer
> rajagiri school of engineering and technology
--
software engineer
rajagiri school of engineering and technology
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-04-21 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 20:41 jeffrin [this message]
2018-04-21 20:41 ` possible BUG: selftests: proc-loadavg-001 failed during kernel testing Jeffrin Thalakkottoor
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='CAG=yYwnsP5w6hKqsp0Q3_DZO3JZmtStGwnXNZN9zjPuFe8fOeA@mail.gmail.com' \
--to=jeffrin@rajagiritech.edu.in \
/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).