All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: lkp@lists.01.org
Subject: Re: Test monitoring on custom github repo
Date: Fri, 25 Jan 2019 16:47:00 +0800	[thread overview]
Message-ID: <a5098fcb-f9eb-0fb0-029a-b7b7bb7a6866@intel.com> (raw)
In-Reply-To: <CAJcbSZGcg8TbQ_+B4RBn4oXF2zqYDWEqquWrE60PnM0FQ4uw_g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]

Hi Thomas,

The github repo is in our monitor list. but we met some problems and the 
robot didn't work in the couple past days.

Best Regards,
Rong Chen

On 1/25/19 1:30 AM, Thomas Garnier wrote:
> Hey,
>
> I pushed changes in the couple past days and didn't see any LKP robot 
> picking it up. In particular, this branch: 
> https://github.com/thgarnie/linux/commits/kaslr_pie_v6_prepare
>
> Is that expected?
>
> Thanks,
>
> On Thu, Dec 14, 2017 at 5:30 AM Thomas Garnier <thgarnie@google.com 
> <mailto:thgarnie@google.com>> wrote:
>
>     Yes please, thanks!
>
>     On Dec 13, 2017 9:12 PM, "Ye Xiaolong" <xiaolong.ye@intel.com
>     <mailto:xiaolong.ye@intel.com>> wrote:
>
>         On 12/13, Thomas Garnier wrote:
>         >Hi,
>         >
>         >I am working on KASLR (PIE for x86_64). I previously used
>         Kees (CCed)
>         >branches for lkp bot testing but someone told be I could ask
>         you to add a
>         >custom github path to monitor all branches on it.
>         >
>         >I pushed my changes to: https://github.com/thgarnie/linux
>         (kasrl_pie_v2
>         >right now)
>         >
>         >Can you add it? Anything I need to do?
>
>         Sure, I'll add your github repo to 0day's monitor list, Do you
>         want build test
>         for all branches in it?
>
>         Thanks,
>         Xiaolong
>
>         >
>         >Thanks,
>         >--
>         >Thomas
>
>         >_______________________________________________
>         >LKP mailing list
>         >LKP(a)lists.01.org <mailto:LKP@lists.01.org>
>         >https://lists.01.org/mailman/listinfo/lkp
>
>
>
> -- 
> Thomas
>
> _______________________________________________
> LKP mailing list
> LKP(a)lists.01.org
> https://lists.01.org/mailman/listinfo/lkp

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4528 bytes --]

      reply	other threads:[~2019-01-25  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 22:40 Test monitoring on custom github repo Thomas Garnier
2017-12-14  5:12 ` Ye Xiaolong
2017-12-14 13:30   ` Thomas Garnier
2019-01-24 17:30     ` Thomas Garnier
2019-01-25  8:47       ` Rong Chen [this message]

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=a5098fcb-f9eb-0fb0-029a-b7b7bb7a6866@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=lkp@lists.01.org \
    /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.