IRC logs for #cip for Thursday, 2019-07-04

*** OutBackDingo has quit IRC01:25
*** OutBackDingo has joined #cip01:28
*** alicef has quit IRC05:29
*** alicef has joined #cip05:36
*** rajm has joined #cip06:14
*** Yamamodo has joined #cip06:52
patersoncpave1: loud and clear07:09
*** Yamamodo has quit IRC07:15
*** Yamamodo has joined #cip07:28
*** Yamamodo has quit IRC07:53
*** Yamamodo has joined #cip07:56
*** Yamamodo has quit IRC08:18
*** tpollard has joined #cip08:20
*** Yamamodo has joined #cip08:21
*** Yamamodo has quit IRC08:43
*** kazu has joined #cip08:56
szlin#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Jul  4 09:00:06 2019 UTC and is due to finish in 60 minutes.  The chair is szlin. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brloggerThe meeting name has been set to 'cip_irc_weekly_meeting'09:00
*** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)"09:00
szlin#topic rollcall09:00
*** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
bwhhi09:00
szlinplease say hi if you're here09:00
kazuhi09:00
patersonchi09:00
iwamatsuhi09:00
fujita[m]hi09:00
*** vidda has joined #cip09:00
szlin#topic AI review09:00
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:01
szlin1. Provide the script for CIP kernel config collection - bwh09:01
szlin#link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002506.html09:01
szlinplease provide your comment or suggestion on it09:01
*** Yamamodo has joined #cip09:01
*** Yamamodo has left #cip09:01
szlinbwh: do you have any comment?09:01
*** Yamamodo has joined #cip09:01
Yamamodohi09:02
szlin2. List real time kernel questions to ask Daniel Wagner - szlin09:02
szlinI will send the mail before this week09:02
bwhszlin: I will merge those changes this week or next week09:02
szlinbwh: thank you.09:02
szlin3. Try updating CIP RT kernel to 4.19.50 - Pavel09:03
szlinSince pavel is not here today, I will send the email to him.09:03
szlin4. Work out a solution for LAVA master backups - patersonc09:03
szlinpatersonc: do you have any update?09:03
patersoncNope09:03
szlinok,I will keep it.09:04
szlin#topic Kernel maintenance updates09:04
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:04
szlinYamamodo and I are starting to review failed patches.09:04
szliniwamatsu: bwh do you have any update on kernel maintenance updates topic?09:05
bwhI don't09:05
iwamatsuszlin: last friday, I updated cip kernel 4.19.y (4.19.56-cip5)09:05
szliniwamatsu: thank you!09:06
*** pave1 has joined #cip09:06
pave1hi09:06
iwamatsuhi, pave109:06
szlinpave1: hi! you're just in time09:07
szlinpave1: do you have any update in kernel maintenance updates topic?09:07
pave1sorry for being late. I am travelling.09:07
pave1Yes. I did partial review of 4.19.57.09:07
szlinpave1: no worry, thank you.09:08
szlinany other comments?09:08
pave1Plus I am searching for suitable target for realtime testing.09:08
pave1Good news is that I am now able to do some testing.09:08
pave1Thats all from me.09:09
szlinpave1:thanks.09:09
szlin309:09
szlin209:09
szlin109:09
szlin#topic Kernel testing09:09
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:09
patersoncHello09:09
patersonc#info Mentor are currently adding a Siemens IPC 227E X86 board to lab-cip-mentor, hence it's currently offline.09:09
patersonc#info I've been continuing to improve the linux-cip-ci scripts. I should hopefully have it all completed by OSS-J.09:09
patersoncDiscussion points (1):09:09
patersonc1/1: Kernel maintainers: What do we want to do with the .gitlab-ci.yml files?09:10
patersoncAdd them to the main kernel.org repo?09:10
patersonc+ve Builds are easily triggered on changes09:10
patersonc+ve Each commit gets a pretty green tick09:10
patersonc-ve The kernel.org repo ends up with irrelevant .gitlab-ci.yml files09:10
patersonc-ve Kernel maintainers will need to merge updates to the gitlab ci files09:10
patersoncCreate a separate repo and use hooks to trigger builds? (untested, but I assume it'll work)09:10
patersonc+ve Keeps the kernel.org repo clean09:10
patersonc+ve Testing team can manage CI files independently09:10
patersonc-ve No pretty green ticks in GitLab09:10
patersonc-ve You have to go to a seperate repository to see what has been built/tested09:10
patersoncover to you...09:10
pave1I do not have strong opinion on that one.09:11
szlinpatersonc: I suggest you to email above items via cip-dev or cip-members09:11
szlinAfter all, some people didn't attend today's meeting09:11
patersoncszlin: Okay, but there is already a discussion on cip-dev based off a patch I submitted. No input from the maintainers though, just Danial and Jan09:12
szlinpatersonc: is that ok for you?09:12
patersoncDoes anyone in this meeting have an opinion?09:12
szlinpatersonc: I see.09:13
iwamatsupatersonc:  I want to keep kerne repo, if possible.09:13
szliniwamatsu: pave1 bwh ^  please provide your valuable opinion09:13
bwhI think I prefer the first option09:14
patersonciwamatsu: Is that the first option?09:14
patersoncThanks bwh09:14
pave1I'd say we can do whatever is easiest. We can always change things if it is problematic.09:14
szlinpave1: agree09:14
iwamatsupatersonc: Yes, first opinion.09:15
patersoncThank you all.09:15
pave1commiting changes from testing team should not be hard.09:15
szlinpatersonc: first option is " Add them to the main kernel.org repo"09:15
patersoncszlin: yep09:15
szlinany objection?09:16
patersoncpave1: Nope. I can just submit patches to cip-dev. Same process as any other patch09:16
szlin#agree Add .gitlab-ci.yml files to the main kernel.org repo09:16
szlinany other comments?09:16
szlin309:16
szlin209:16
szlin109:16
patersoncThank you all!09:16
szlinpatersonc: thank you for your proposal09:16
szlin#topic CIP Core09:17
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:17
kazuno technical updates in this week,09:17
kazuI'm still creating the document of package decision process,09:17
kazuI have to finish before the next TSC meeting09:17
szlinkazu: thank you09:17
szlinany other comments?09:17
kazusorry for the delay09:17
szlin309:18
szlin209:18
szlin109:18
szlin#topic Software update09:18
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:18
szlin== Quote from Suzuki ==09:18
szlinWe are preparing a software update demo for OSSJ.09:18
szlinWe had a meeting with Christian of Siemens and he shared a sample script09:18
szlinthat could manage the state of software update.09:18
kazuSuzuki-san sent the updates to cip-dev09:18
szlinSuzuki implemented the state management into the u-boot script of the demo09:18
szlinand now BeagleBone Black can switch back to old root filesystem if the update fails.09:18
szlinWe call it "rollback".09:18
szlinNow we can give the demo of raw image update only.09:19
szlinIf we can make it in time, we will give the demo of binary delta update using librsync.09:19
szlin== End ==09:19
szlinany other comments?09:19
szlin309:19
szlin209:19
szlin109:19
szlin#topic AOB09:19
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:19
szlinpave1: Jan sent the email to ask a question about rt version09:19
iwamatsupatersonc: Can you see https://lava.ciplatform.org/results/? I got 500 error.09:20
szlinpave1: #info https://lists.cip-project.org/pipermail/cip-dev/2019-June/002548.html09:20
pave1szlin thanks, I should be able to take a look later today.09:20
szlinpave1: thank you09:20
patersonciwamatsu: Grrr. That's happened a couple of times.09:20
patersonciwamatsu: Individual test job results can usually still be seen.09:21
szlinany other business?09:21
szlin309:21
szlin209:21
szlin109:21
patersoncmungaip worked out what caused it, I'll have to dig through the emails to refresh my memory09:21
patersonciwamatsu: Thank you for reporting the issue.09:21
szlin#endmeeting09:21
brloggerMeeting ended Thu Jul  4 09:21:57 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:21
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2019/07/cip.2019-07-04-09.00.html09:21
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2019/07/cip.2019-07-04-09.00.txt09:21
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2019/07/cip.2019-07-04-09.00.log.html09:21
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:21
szlinthank you all09:22
szlinpave1: thank you for attending during your travel :)09:22
iwamatsupatersonc: I see.  you are welcome.09:22
pave1szlin No problem.09:22
iwamatsuoave1: have a nice trip.09:22
Yamamodothanks09:22
iwamatsus/oave1/pave109:23
iwamatsuthanks, all.09:23
pave1thank you!09:24
*** vidda has quit IRC09:29
*** pave1 has quit IRC09:31
*** tpollard has quit IRC10:07
*** tpollard has joined #cip10:10
*** Yamamodo has quit IRC11:56
*** kazu has quit IRC13:14
*** rajm has quit IRC13:57
*** OutBackDingo has quit IRC14:27
*** OutBackDingo has joined #cip14:27
*** rajm has joined #cip14:33
*** Yamamodo has joined #cip14:43
*** Yamamodo has quit IRC15:08
*** Yamamodo has joined #cip15:10
*** Yamamodo has quit IRC15:33
*** tpollard has quit IRC16:31
*** OutBackDingo has quit IRC16:45
*** OutBackDingo has joined #cip16:52
*** Yamamodo has joined #cip17:16
*** Yamamodo has quit IRC17:23
*** Yamamodo has joined #cip17:29
*** Yamamodo has quit IRC17:53
*** Yamamodo has joined #cip18:08
*** Yamamodo has quit IRC18:30
*** Yamamodo has joined #cip18:35
*** Yamamodo has quit IRC18:57
*** Yamamodo has joined #cip19:00
*** Yamamodo has quit IRC19:22
*** rajm has quit IRC22:20
*** OutBackDingo has quit IRC23:10
*** OutBackDingo has joined #cip23:15

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!