From mboxrd@z Thu Jan 1 00:00:00 1970 From: SZ.Lin@moxa.com (=?utf-8?B?U1ogTGluICjmnpfkuIrmmbop?=) Date: Thu, 7 Nov 2019 09:17:44 +0000 Subject: [cip-dev] CIP IRC weekly meeting today In-Reply-To: References: Message-ID: To: cip-dev@lists.cip-project.org List-Id: cip-dev.lists.cip-project.org Hi Iwamatsu-san, > From: nobuhiro1.iwamatsu at toshiba.co.jp > > Hi SZ, > > I may be late or unable to join meeting. Thank you for your heads up, I've listed your comments in the IRC meeting. SZ > > > * Action item > > 1. Provide the cases to cip-testing to build up the test environment - > > Iwamatsu-san > Merged by Chris. Please close this A.I. Thanks for Chris. > https://gitlab.com/cip-project/cip-testing/linux-cip-ci/merge_requests/24 > > > 2. Test LTS (pre)releases directly - patersonc 3. Ask KernelCI for > > recommendations on what tests to run - patersonc 4. Create a > > way/process to run LTP only for release tests - patersonc 5. > > Investigate the RT test tools - Pavel 6. Combine rootfilesystem with > > kselftest binary - Iwamatsu-san > > This is WIP. Please keep. > > > 7. Document a process on how to add tests to the CIP test setup - > > patersonc 8. Split out non-Kernel config sections from gitlab-ci.yml - > > patersonc 9. Do we want to go with the current approach where GitLab > > CI is run ?out of tree?- Kernel team > We discussion by Mail now. Some opinions come from Chris. > > > * Kernel maintenance updates > I reviewed v4.4.198. > > Best regards, > Nobuhiro > > > -----Original Message----- > > From: cip-dev-bounces at lists.cip-project.org > > [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of SZ Lin (? > > ??) > > Sent: Thursday, November 7, 2019 10:56 AM > > To: cip-dev at lists.cip-project.org > > Subject: [cip-dev] CIP IRC weekly meeting today > > > > Hi all, > > > > Kindly be reminded to attend the weekly meeting through IRC to discuss > > technical topics with CIP kernel today. > > > > *Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 > > starting from the first week of Apr. according to TSC meeting* > > https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019 > > > &month=11&day=7&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=1 > 36&p5=37 > > &p6=248 > > > > US-West US-East?? UK???? DE???? TW???? JP > > 01:00??? 04:00?? 09:00?? 10:00?? 17:00?? 18:00 > > > > Channel: > > * irc:chat.freenode.net:6667/cip > > > > Last week's meeting minutes: > > https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-24-09. > > 00.html > > > > Agenda: > > > > * Action item > > 1. Provide the cases to cip-testing to build up the test environment - > > Iwamatsu-san 2. Test LTS (pre)releases directly - patersonc 3. Ask > > KernelCI for recommendations on what tests to run - patersonc 4. > > Create a way/process to run LTP only for release tests - patersonc 5. > > Investigate the RT test tools - Pavel 6. Combine rootfilesystem with > > kselftest binary > > - Iwamatsu-san 7. Document a process on how to add tests to the CIP > > test setup - patersonc 8. Split out non-Kernel config sections from > > gitlab-ci.yml - patersonc 9. Do we want to go with the current > > approach where GitLab CI is run ?out of tree?- Kernel team > > > > * Kernel maintenance updates > > * Kernel testing > > * CIP Core > > * Software update > > * AOB > > > > The meeting will take 30 min, although it can be extended to an hour > > if it makes sense and those involved in the topics can stay. > > Otherwise, the topic will be taken offline or in the next meeting. > > > > Best regards, > > > > SZ Lin, Moxa. > > _______________________________________________ > > cip-dev mailing list > > cip-dev at lists.cip-project.org > > https://lists.cip-project.org/mailman/listinfo/cip-dev