From mboxrd@z Thu Jan 1 00:00:00 1970 From: Petr Vorel Date: Thu, 9 Jan 2020 09:46:27 +0100 Subject: [LTP] [PATCH] tst_device: add new tst_dev_sync In-Reply-To: <5518d8cd-7d35-8c65-e881-5f49c73dc379@cn.fujitsu.com> References: <20200107071324.29492-1-liwang@redhat.com> <20200107101119.GA22967@rei.lan> <20200108112537.GA22954@dell5510> <20200108113535.GA17272@rei.lan> <20200108114141.GB17272@rei.lan> <20200108114545.GA28867@dell5510> <5518d8cd-7d35-8c65-e881-5f49c73dc379@cn.fujitsu.com> Message-ID: <20200109084627.GA19145@dell5510> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it 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/