Hi Andy, I *think* the CI people probably need to handle this, since it's part of their test set up.
Paul, Milo: Any ideas? Thanks Dave On 14 May 2013, at 01:16, Andy Green <[email protected]> wrote: > Hi Dave - > > I'm supremely uninterested in these reports for the dead TI trees... do you > know how can I remove my email from notifications for them? > > There are three trees in CI tests that will never get updated again afaik > that keep spamming me. > > It might be an idea to link to the page where you can adjust notifications, > on any notification. > > -Andy > > > -------- Original Message -------- > Subject: Build failed in Jenkins: LT-TI-working-tree-3.4_panda-es-omap4plus > #250 > Date: Tue, 14 May 2013 00:14:07 +0000 (UTC) > From: [email protected] > To: [email protected], [email protected], [email protected], > [email protected] > > See > <https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus/250/> > > ------------------------------------------ > Started by timer > [EnvInject] - Loading node environment variables. > Building remotely on Precise-64 3exec (i-5033053c) in workspace > <https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus/ws/> > Checkout:LT-TI-working-tree-3.4_panda-es-omap4plus / > <https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus/ws/> > - hudson.remoting.Channel@10a7a7:Precise-64 3exec (i-5033053c) > Using strategy: Default > Last Built Revision: Revision edb2dff2ab14d66f123d43a18b2b27cecf598cdf > (origin/tilt-3.4) > Cloning the remote Git repository > Cloning repository git://git.linaro.org/landing-teams/working/ti/kernel.git > git --version > git version 1.7.9.5 > Fetching upstream changes from origin > Commencing build of Revision edb2dff2ab14d66f123d43a18b2b27cecf598cdf > (origin/tilt-3.4) > Checking out Revision edb2dff2ab14d66f123d43a18b2b27cecf598cdf > (origin/tilt-3.4) > [copy-to-slave] Copying 'builddeb', excluding nothing, from > 'file:/var/lib/jenkins/userContent/' on the master to > '<https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus/ws/'> > on 'Precise-64 3exec (i-5033053c)'. > [LT-TI-working-tree-3.4_panda-es-omap4plus] $ /bin/sh -xe > /tmp/hudson2373270767559071380.sh > + rm -rf lci-build-tools > + export hwpack_type=panda > + export board_types=panda-es > + export kernel_config=omap4plus_defconfig > + export kernel_flavour=omap > + export > git_web_url=http://git.linaro.org/git-ro/landing-teams/working/ti/kernel.git > + export lava_test_plan=ltp,pwrmgmt,lt_ti_lava > + export > toolchain_url=http://releases.linaro.org/12.08/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_linux.tar.bz2 > + bzr branch lp:linaro-ci lci-build-tools > You have not informed bzr of your Launchpad ID, and you must do this to > write to Launchpad or access private data. See "bzr help launchpad-login". > Branched 148 revisions. > + ./lci-build-tools/jenkins_kernel_build_inst > + test -z omap > + test -z '' > + rootfs_type=nano-lava > + test -z http://git.linaro.org/git-ro/landing-teams/working/ti/kernel.git > + test -z panda > + test -z '' > + submit_job=1 > + test -z ltp,pwrmgmt,lt_ti_lava > + test -z > http://releases.linaro.org/12.08/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_linux.tar.bz2 > + wget -cq > http://releases.linaro.org/12.08/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_linux.tar.bz2 > Build step 'Execute shell' marked build as failure > > _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
