From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] tst_device: add new tst_dev_sync
Date: Thu, 9 Jan 2020 09:46:27 +0100 [thread overview]
Message-ID: <20200109084627.GA19145@dell5510> (raw)
In-Reply-To: <5518d8cd-7d35-8c65-e881-5f49c73dc379@cn.fujitsu.com>
Hi Xu,
> > I guess we should work on travis CI integration so we don't have to push it to
> > travis manually [1].
> Do we have a tool or a function that
> when this pushing patch complie succeeded, then merge successfully or reject
> auto because of fail. Like gerrit.
Well, we have patchwork and his REST API [2] (IMHO lightweight than gerrit, but
needs to be setup). More info is at #599 [2].
> Or, pushing patch compiler on travis CI first, then merged into ltp master.
> If not, it seems that we can only try on our own ltp fork(Usually, I do it
> when I write a new case or cleanup)
That's what I want to automate. It will probably needs some special github account,
but we have it for travis anyway.
Kind regards,
Petr
[1] https://github.com/linux-test-project/ltp/issues/599
[2] https://patchwork.readthedocs.io/en/latest/api/rest/
next prev parent reply other threads:[~2020-01-09 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 7:13 [LTP] [PATCH] tst_device: add new tst_dev_sync Li Wang
2020-01-07 10:11 ` Cyril Hrubis
2020-01-08 10:46 ` Li Wang
2020-01-08 11:25 ` Petr Vorel
2020-01-08 11:30 ` Petr Vorel
2020-01-08 11:35 ` Cyril Hrubis
2020-01-08 11:39 ` Li Wang
2020-01-08 11:41 ` Cyril Hrubis
2020-01-08 11:45 ` Petr Vorel
2020-01-09 6:59 ` Li Wang
2020-01-09 8:06 ` Petr Vorel
2020-01-09 9:49 ` Cyril Hrubis
2020-01-09 10:10 ` Petr Vorel
2020-01-09 7:37 ` Yang Xu
2020-01-09 8:46 ` Petr Vorel [this message]
2020-01-09 9:56 ` Yang Xu
2020-01-09 10:05 ` Petr Vorel
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=20200109084627.GA19145@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox