All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
	Jan Kratochvil <jkratoch@redhat.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Milian Wolff <milian.wolff@kdab.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Taeung Song <treeze.taeung@gmail.com>,
	Wang Nan <wangnan0@huawei.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/7] perf/core improvements and fixes
Date: Thu, 26 Nov 2015 10:09:26 +0100	[thread overview]
Message-ID: <20151126090926.GC8822@krava.brq.redhat.com> (raw)
In-Reply-To: <20151126081236.GB20999@gmail.com>

On Thu, Nov 26, 2015 at 09:12:37AM +0100, Ingo Molnar wrote:

SNIP

> fixdep: error opening depfile: ./.plugin_hrtimer.o.d: No such file or directory
> /home/mingo/tip/tools/build/Makefile.build:77: recipe for target 
> 'plugin_hrtimer.o' failed
> make[3]: *** [plugin_hrtimer.o] Error 2
> Makefile:189: recipe for target 'plugin_hrtimer-in.o' failed
> make[2]: *** [plugin_hrtimer-in.o] Error 2
> Makefile.perf:414: recipe for target 'libtraceevent_plugins' failed
> make[1]: *** [libtraceevent_plugins] Error 2
> make[1]: *** Waiting for unfinished jobs....
>   CC       plugin_kvm.o
>   CC       builtin-sched.o
>   CC       plugin_mac80211.o
>   LD       plugin_kmem-in.o
>   CC       util/help.o
> 
> Can you reproduce it by adding 'sleep 1' (or 'sleep 2') to the end of 
> util/PERF-VERSION-GEN? (See the patch attached further below.)
> 
> The failure is sporadic even with the 'sleep 1' hack - I get a build failure 1 out 
> of 3 times maybe:
> 
> triton:~/tip/tools/perf> while : ; do echo -n "$(date) "; make clean install >/tmp/FAIL.log 2>&1 && echo pass || { echo 'FAIL!'; break; } done
> Thu Nov 26 09:07:12 CET 2015 pass
> Thu Nov 26 09:07:23 CET 2015 FAIL!
> 
> Interestingly it does not reproduce if I use '>FAIL.log' - I need to output the 
> log into tmpfs - maybe the extra VFS synchronization if logging to the same 
> filesystem where the build occurs hides the race?
> 
> With V=1 it takes a lot longer to reproduce:
> 
> triton:~/tip/tools/perf> while : ; do echo -n "$(date) "; make clean install V=1 >/tmp/FAIL.log 2>&1 && echo pass || { echo 'FAIL!'; break; } done
> Thu Nov 26 09:08:08 CET 2015 pass
> Thu Nov 26 09:08:20 CET 2015 pass
> Thu Nov 26 09:08:32 CET 2015 pass
> Thu Nov 26 09:08:43 CET 2015 pass
> Thu Nov 26 09:08:55 CET 2015 pass
> Thu Nov 26 09:09:06 CET 2015 pass
> Thu Nov 26 09:09:17 CET 2015 pass
> Thu Nov 26 09:09:29 CET 2015 pass
> Thu Nov 26 09:09:41 CET 2015 FAIL!

so far no luck on my side.. from quick check over the fail log
it seems the patch I sent yesterday could help:

http://lkml.iu.edu/hypermail/linux/kernel/1511.3/00186.html

I'll have more detailed check on your fail log,

thanks,
jirka

  reply	other threads:[~2015-11-26  9:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 21:53 [GIT PULL 0/7] perf/core improvements and fixes Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 1/7] perf callchain: Move initial entry call into get_entries function Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 2/7] perf callchain: Add order support for libunwind DWARF unwinder Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 3/7] perf test: Add callchain order setup for DWARF unwinder test Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 4/7] perf callchain: Add order support for libdw DWARF unwinder Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 5/7] perf tools: Add 'perf config' command Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 6/7] perf config: Add initial man page Arnaldo Carvalho de Melo
2015-11-23 21:53 ` [PATCH 7/7] perf callchain: Add missing parent_val initialization Arnaldo Carvalho de Melo
2015-11-24  8:10 ` [GIT PULL 0/7] perf/core improvements and fixes Ingo Molnar
2015-11-24  8:28   ` Jiri Olsa
2015-11-24  8:42     ` Ingo Molnar
2015-11-24  9:26       ` Jiri Olsa
2015-11-24  9:47         ` Jiri Olsa
2015-11-26 11:00           ` Ingo Molnar
2015-11-26 12:47             ` Jiri Olsa
2015-11-26  7:56         ` Ingo Molnar
2015-11-26  8:12           ` Ingo Molnar
2015-11-26  9:09             ` Jiri Olsa [this message]
2015-11-24 10:28   ` Jiri Olsa
2015-11-26  8:13   ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2017-04-13 19:35 Arnaldo Carvalho de Melo
2017-04-14 16:07 ` Arnaldo Carvalho de Melo
2017-04-17  8:15   ` Ingo Molnar
2015-06-12  2:15 Arnaldo Carvalho de Melo
2015-06-12  8:09 ` Ingo Molnar
2015-04-10 21:40 Arnaldo Carvalho de Melo
2015-04-11  6:33 ` Ingo Molnar
2014-06-23  7:59 Jiri Olsa
2014-06-25  5:44 ` Ingo Molnar
2014-04-28 11:59 Jiri Olsa
2014-04-29  6:42 ` Ingo Molnar
2013-11-07 15:04 Arnaldo Carvalho de Melo
2013-11-07 15:26 ` Ingo Molnar
2012-06-27 19:20 Arnaldo Carvalho de Melo
2012-06-29 13:12 ` Ingo Molnar
2012-07-02  8:01   ` Dmitry Antipov
2012-03-05 15:55 Arnaldo Carvalho de Melo
2012-03-05 16:02 ` Ingo Molnar

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=20151126090926.GC8822@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=jkratoch@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=milian.wolff@kdab.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=treeze.taeung@gmail.com \
    --cc=wangnan0@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.