From: Philip Li <philip.li@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Richard Weinberger <richard@nod.at>, <oe-kbuild-all@lists.linux.dev>
Subject: Re: [rw-misc:embedded_go_prog 1/1] /bin/bash: line 1: go: command not found
Date: Wed, 19 Jul 2023 09:31:26 +0800 [thread overview]
Message-ID: <ZLc87pVzmxZeNzGW@rli9-mobl> (raw)
In-Reply-To: <202307180806.prgq1hPx-lkp@intel.com>
On Tue, Jul 18, 2023 at 08:58:56AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/rw/misc.git embedded_go_prog
> head: 58a51666e0ed2b23253048b0616ee5879361cc4a
> commit: 58a51666e0ed2b23253048b0616ee5879361cc4a [1/1] misc: Add demo driver for user mode driver usage
> config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20230718/202307180806.prgq1hPx-lkp@intel.com/config)
> compiler: sparc64-linux-gcc (GCC) 12.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20230718/202307180806.prgq1hPx-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202307180806.prgq1hPx-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> /bin/bash: line 1: go: command not found
Hi Richard, kindly ignore this report, it's our environment problem.
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
next prev parent reply other threads:[~2023-07-19 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 0:58 [rw-misc:embedded_go_prog 1/1] /bin/bash: line 1: go: command not found kernel test robot
2023-07-19 1:31 ` Philip Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-18 0:17 kernel test robot
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=ZLc87pVzmxZeNzGW@rli9-mobl \
--to=philip.li@intel.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard@nod.at \
/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.