From: Julien Grall <julien.grall@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [linux-3.14 test] 63336: regressions - FAIL
Date: Wed, 28 Oct 2015 18:12:03 +0000 [thread overview]
Message-ID: <56310FF3.6090605@citrix.com> (raw)
In-Reply-To: <osstest-63336-mainreport@xen.org>
Hi,
On 28/10/15 17:31, osstest service owner wrote:
> flight 63336 linux-3.14 real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/63336/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-armhf-pvops 5 kernel-build fail REGR. vs. 62648
> + make -j4 INSTALL_PATH=/home/osstest/build.63336.build-armhf-pvops/dist/boot INSTALL_MOD_PATH=/home/osstest/build.63336.build-armhf-pvops/dist modules_install dtbs_install
> make: *** No rule to make target `dtbs_install'. Stop.
> make: *** Waiting for unfinished jobs....
This is not a Linux regression but a bug introduced in osstest
by d4dba6183d616b1d4f9826834318db48eb8ec5d6 "ts-kernel-build:
Include dtbs in dist file"
As said by the commit message the target dtbs_install has
been introduced post-3.14. It also says that we only test
3.16 and onwards on ARM. However this job seems to prove
the contrary.
So shall we disable 3.14 job for ARM for once and all?
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-10-28 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 17:31 [linux-3.14 test] 63336: regressions - FAIL osstest service owner
2015-10-28 18:12 ` Julien Grall [this message]
2015-11-02 10:17 ` Ian Campbell
2015-11-02 11:09 ` Julien Grall
2015-11-17 10:58 ` [PATCH OSSTEST v1] make-flight: Stop testing ARM for linux-3.14 flights Ian Campbell
2015-11-17 11:56 ` Ian Jackson
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=56310FF3.6090605@citrix.com \
--to=julien.grall@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.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.