User Tools

Site Tools


civilinfrastructureplatform:journal

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
civilinfrastructureplatform:journal [2018/09/14 09:56]
rajmarshall
civilinfrastructureplatform:journal [2018/11/14 14:01]
rajmarshall
Line 2: Line 2:
  
 This is the journal followed by CIP developers to keep track of the work being done on behalf of CIP. It starts in 2018Q2. This is the journal followed by CIP developers to keep track of the work being done on behalf of CIP. It starts in 2018Q2.
 +
 +
 +===== November =====
 +
 +==== Wednesday 2018/11/14 ====
 +
 +=== rajm ===
 +
 +   * Ran a BBB health check successfully,​ email to the list.
 +
 +==== Friday 2018/11/08 ====
 +
 +=== rajm ===
 +
 +   * Added mention of [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​195|#​195]] web proxies to Known Issues and closed the issue.
 +   * 1:1 with toscalix
 +   * Ran iwg20m and BBB health checks successfully,​ email to the list.
 + 
 +
 +==== Thursday 2018/11/08 ====
 +
 +=== rajm ===
 +
 +   * Added known issue to cover extending the timeout date for builds in kernelci and closes [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​164|#​164]].
 +   * Amended the lavacli documentation so that the adding of the auth token appears and pastes correctly.
 +   * Ran a BBB health check successfully,​ email to the list.
 +   * Attended the cip-dev IRC meeting.
 +   * Ran an iwg20m health check successfully,​ email to the list.
 +
 +
 +=== SZ Lin (林上智) ===
 +  * Attended the cip-dev IRC meeting.
 +
 +==== Wednesday 2018/11/07 ====
 +
 +=== rajm ===
 +
 +   * Removed ToDo label from a lot of closed issues.
 +   * Updated Known Issues to include method for BBB ssh connection from [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​153|#​153]] and closed the issue.
 +   * Ran a BBB health check successfully,​ email to the list.
 +
 +==== Monday 2018/11/05 ====
 +
 +=== toscalix ===
 +
 +   * SZLin asked me to resend the Weekly IRC event invitation since there has been time changes in several timezones lately.
 +      * I sent a mail to guests warning them about this circumstance.
 +         * SZLin has not received such note.
 +      * I proposed on cip-dev creating a public Google calendar for CIP so more Members can publish and manage the calendar events and everybody can see it.
 +   * IRC logger is up and running now. Baserock sysadmins fixed the isse.
 +      * The #automotive logger was also down. Walt Miner reported it at the cip-dev channel.
 +
 +==== Friday 2018/11/02 ====
 +
 +=== rajm ===
 +
 +
 +   * Also closed #75, 79, #150, #160, #189 and #196.
 +   * Updated known issues and therefore closing [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​196|#​196]].
 +   * Closed various issues we are not going to fix - [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​118|#​118]],​ [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​137|#​137]],​ [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​154|#​154]] and [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​|#​161]]
 +   * Ran a BBB health check successfully,​ email to the list.
 +   * Ran an iwg20m health check successfully,​ email to the list.
 +
 +==== Thursday 2018/11/01 ====
 +
 +=== rajm ===
 +
 +   * Closed [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​190|#​190]] submitter no longer has problem and not reproducible.
 +   * Closed [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​158|#​158]] - was fixed by 01551476f285f2cb5caa5f0e99bf483f24735123 back in July.
 +   * 1:1 with toscalix.
 +   * Ran a fresh provision for week 44 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]].
 +   * Participated in cip-dev IRC meeting.
 +   * Ran an iwg20m health check successfully,​ email to the list.
 +   * Ran a BBB  health check successfully,​ email to the list.
 +
 +
 +=== toscalix ===
 +
 +   * Chris reported that the [[https://​irclogs.baserock.org/​cip/​|logs of the #cip IRC channel]] are not accessible. I confirmed it.
 +      * Reported it to Baserock project sysadmin
 +
 +===== October =====
 +
 +==== Monday 2018/10/29 ====
 +
 +=== toscalix ===
 +
 +   * Attended to TSC meeting
 +      * Provided feedback about the event.
 +      * Sent a few days back the slides provided to me by kernelci.org promoters to evaluate CIP participation to CIP Members.
 +   * Provided feedback to Yoshi about the slides used for the CIP talk at ELCE 2018 thorugh cip-dev mailing list. 
 +
 +=== rajm ===
 +
 +   * Ran an iwg20m health check successfully,​ email to the list.
 +   * Ran a BBB  health check successfully,​ email to the list.
 +
 +==== Friday 2018/10/26 ====
 +
 +=== rajm ===
 +
 +   * 1-1 with toscalix.
 +   * Ran a BBB  health check successfully,​ email to the list.
 +   * Ran an iwg20m health check successfully,​ email to the list.
 +
 +
 +==== Thursday 2018/10/25 ====
 +
 +=== rajm ===
 +
 +   * Looking at mungaip'​s update of [[https://​github.com/​kernelci/​lava-docker/​issues/​45|issue 45]].
 +   * Attended cip-dev IRC meeting.
 +   * Ran a BBB  health check successfully,​ email to the list.
 +   * Ran an iwg20m health check successfully,​ email to the list.
 +
 +=== SZ Lin (林上智) ===
 +  * Attended the cip-dev IRC meeting.
 +
 +==== Wednesday 2018/10/24 ====
 +
 +=== rajm ===
 +
 +   * Ran a BBB  health check successfully,​ email to the list.
 +   * Ran an iwg20m health check successfully,​ email to the list.
 +
 +
 +==== Monday 2018/10/22 ====
 +
 +=== toscalix ===
 +
 +   * Kernel maintenance devs breakfast.
 +   * Kernel maintenance team meeting: Ben Hutchings participated,​ not me.
 +   * Meeting CIP with kernelci.org Linux Foundation Initiative promoters at ELCE 2018.
 +   * Interesting conversation with J. Colbert after his reference to CIP at  his ELCE 2018 keynote.
 +
 +==== Sunday 2018/10/21 ====
 +
 +=== toscalix ===
 +
 +   * TSC f2f meeting in Edinburgh, UK, during ELCE 2018
 +      * Presentation of BuildStream:​ 10 min.
 +      * Ben H., Emmet and John joins the TSC meeting.
 +
 +=== SZ Lin (林上智) ===
 +   * Joined TSC f2f meeting via zoom
 +
 +==== Friday 2018/10/19 ====
 +
 +=== toscalix ===
 +
 +   * Preparation of the TSC meeting
 +      * Preparation of the BuildStream slide deck.
 +      * Review of the agenda.
 +
 +=== rajm ===
 +
 +   * Reviewed the wiki and made minor changes.
 +   * Sent an email with a report on progress since June so it can be reported on at ELC-E.
 +   * Ran a BBB  health check successfully,​ email to the list.
 +   * Ran an iwg20m health check successfully,​ email to the list.
 +
 +==== Thursday 2018/10/18 ====
 +
 +=== rajm ===
 +
 +   * Tested lava-docker on our guest network - which gives ip addresses 172.16* matching the addresses docker uses but I'm still getting failures in U-Boot.
 +   * 1:1 with toscalix.
 +   * Ran a fresh provision for week 42 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]].
 +   * Participated in cip-dev IRC meeting.
 +   * Ran a BBB  health check successfully,​ email to the list.
 +   * Ran an iwg20m health check successfully,​ email to the list.
 +
 +==== Wednesday 2018/10/17 ====
 +
 +=== rajm ===
 +
 +   * Discussion with mungaip on getting artifacts from host with LAVA running in docker.
 +   * Still issues running from home with lava-docker - I'll check with the CT guest network tomorrow.
 +   * Ran an BBB health check successfully,​ email to the list.
 +
 +==== Tuesday 2018/10/16 ====
 +
 +=== rajm ===
 +
 +   * Ran an iwg20m health check successfully,​ email to the list.
 + 
 +
 +==== Friday 2018/10/12 ====
 +
 +=== rajm ===
 +
 +   * A provisioned box is now ready to be uploaded but having issues connecting to AWS.
 +   * Ran an iwg20m health check successfully,​ email to the list.
 +   * Ran a BBB health check successfully,​ email to the list.
 +
 +==== Thursday 2018/10/11 ====
 +
 +=== rajm ===
 +
 +  * Participated in cip-dev IRC meeting.
 +  * Ran a BBB health check successfully,​ email to the list.
 +  * Ran an iwg20m health check successfully,​ email to the list.
 +
 +
 +
 +==== Tuesday 2018/10/09 ====
 +
 +=== rajm ===
 +
 +  * Ran a fresh provision for week 40 (a couple of days late!) [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]].
 +  * Ran a BBB health check successfully,​ email to the list.
 +  * Ran an iwg20m health check successfully,​ email to the list.
 +
 +=== toscalix ===
 +
 +   * Organising the trip to ELCE 2018. 
 +      * Asked for confirmation about the TSC f2f meeting starting time and location (room).
 +
 +
 +==== Friday 2018/10/05 ====
 +
 +=== rajm ===
 +
 +  * Sent fortnightly progress report to cip-dev
 +  * Creating a provisioned box (of latest master) for upload to the website.
 +  * Now that the iwg20m MR is merged I've closed the associated [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​186| issue 186]].
 +  * Added [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​202|#​202]] so that file headers get checked and any necessary licence information added.
 +  * Ran a BBB health check successfully,​ email to the list.
 +  * Ran an iwg20m health check successfully,​ email to the list.
 +
 +
 +
 +==== Thursday 2018/10/04 ====
 +
 +=== rajm ===
 +
 +  * Team meeting.
 +  * Following bwh's approval [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​63|MR 63]] is now merged.
 +  * Commented on Nguyen'​s comment on [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​63|MR 63]]
 +  * Participated in cip-dev IRC meeting.
 +  * Ran an iwg20m health check successfully,​ email to the list.
 +  * Ran a BBB health check successfully,​ email to the list.
 +
 +
 +==== Tuesday 2018/10/02 ====
 +
 +=== rajm ===
 +
 +  * Tried running lava-docker on my (home) ubuntu which gave more issues.
 +  * Clarification of when iwg20m health checks will be run to cpaterson.
 +  * Ran a BBB health check successfully,​ email to the list.
 +
 +
 +==== Monday 2018/10/01 ====
 +
 +=== rajm ===
 +
 +  * Tried running lava-docker away from the Codethink network but that still failed. ​
 +  * I tried to replicate the wifi issue on the BBB [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​200|#​200]] but failed to do so - the test worked.
 +  * Unable to run an iwg20m health check this morning as I'm working from home - I'll run this again on Thursday.
 +  * Ran a BBB health check successfully,​ email to the list.
 +
 +=== SZ Lin (林上智) ===
 +  * Create [[civilinfrastructureplatform:​linux-4.4.y|wiki page]] for stable kernel review.
 +  * Confirmed that 4.4.y-stable is *NOT* vulnerable with [[https://​thehackernews.com/​2018/​09/​linux-kernel-vulnerability.html|this security bug]] (Fixed in 86949eb96466e "exec: Limit arg stack to at most 75% of _STK_LIM"​)
 +
 +=== toscalix ===
 +
 +   * Attended to the TSC meeting
 +      * I have no objections of using patchwork at CIP.
 +         * Does Ben H. has any objections?
 +      * Raised a question about the TSC meeting schedule. It is not confirmed yet.
 +      * A meeting of the Debian Kernel team will take place [[https://​www.mail-archive.com/​debian-kernel@lists.debian.org/​msg112588.html|tomorrow]]. It is interesting for CIP if the discussion about the next kernel is part of the agenda. ​
 +      * During ELCE it would be ideal to know the ddates for the f2f TSC meeting around Embedded World 2018.
  
 ===== September ===== ===== September =====
 +
 +==== Friday 2018/09/28 ====
 +
 +=== rajm ===
 +
 +  * Some discussion with bwh as to whether a move to use the zImage is appropriate. ​
 +  * A fresh provision of the B@D has been done and the iwg20m build and health check worked.
 +  * An email has been sent to cip-dev thanking Nguyen and as a notification of the iwg20m advance.
 +  * A [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​63|MR]] has been created for the iwg changes.
 +  * I see that if the host is suspended, on reawakening the clock is correct - this is with Vagrant 2.1.2 so I've closed [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​187|#​187]]
 +  * Ran an iwg20m health check successfully,​ email to the list.
 +  * Ran a BBB health check successfully,​ email to the list.
 +
 +
 +==== Thursday 2018/09/27 ====
 +
 +=== rajm ===
 +
 +
 +  * 1:1 with toscalix.
 +  * The iwg20m appears to work consistently if the device-type is changed so that LAVA doesn'​t attempt to convert to a uImage and uses bootz. [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​186|#​186]] has been updated.
 +  * Attended the cip-dev IRC meeting.
 +  * Ran an IWG20M health check successfully,​email to the list.
 +  * Ran a BBB health check successfully,​email to the list.
 +
 +=== SZ Lin (林上智) ===
 +  * Attended the cip-dev IRC meeting.
 +
 +==== Wednesday 2018/09/26 ====
 +
 +=== rajm ===
 +
 +   * I tried amending renesas-iwg20m.jinja2 in B@D and using the zImage kernel but unsucessfully.
 +   * There are differences between beaglebone-black.jinja2 in B@D and the lava-docker version, I attempted to make the lava-docker version like our version but so far it still fails to health check. The tftp serverip is rather different in lava-docker and wonder if our network settings are causing the issue.
 +   * Updated iwg20m to use a uImage as per Nguyen'​s instructions on [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​186|#​186]] ran 5 tests (one health check the others using lavacli) and all worked. Added a notify section and re-ran the health check which also worked, if the daily health check also runs ok tomorrow, I'll close the issue and update the wiki with instructions.
 +   * Ran a BBB health check successfully,​email to the list. The email from last Friday never appeared, I don't know why - it left the VM but didn't reach the list server, maybe there was a connection with the office power cut we had that morning?
 +
 +==== Friday 2018/09/21 ====
 +
 +=== rajm ===
 +
 +   * Sent email listing progress in weeks 30-38 to the cip-dev email list.
 +   * New section on [[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​ciptestingreferencetestcases#​test-7use-lavacli-utility|lavacli]] added to wiki.
 +   * lava-tool is deprecated, so I've manually installed lavacli and run a test successfully.
 +   * I've added a note to the LAVA notification section on the wiki that IRC pings on Freenode are not working at the moment due to their SPAM avoidance methods.
 +   * Ran a BBB health check successfully,​ still waiting for the email to appear on the list.
 +
 +
 +==== Thursday 2018/09/20 ====
 +
 +=== rajm ===
 +
 +   * Ran a fresh provision for week 38 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]].
 +   * Met in the team meeting.
 +   * Pushed a new version of docker-provision.sh to [[https://​gitlab.com/​cip-project/​cip-testing/​kernelci-docker|the CIP kernelci-docker]] where the initramfs build works - it uses init-example from b@d.
 +   * Attended the cip-dev IRC meeting.
 +   * Ran a BBB health check successfully with an email to the list.
 +
 +
 +=== toscalix ===
 +
 +   * During the IRC cip-dev meeting I checked the state of the TSC minutes being published since there were a couple of actions points to escalate topics there. Instead of any of us providing outcome of the TSC discussions,​ we should just simply refer to the minutes.
 +     * There are no minutes published sinec January 2018
 +     * I sent a mail to cip-dev to have them published. ​
 +
 +==== Wednesday 2018/09/19 ====
 +
 +=== rajm ===
 +
 +   * docker-provision.sh builds initramfs and copies it to the kernelci docker in the correct location (or at least a http accessible location) so I've ticked the relevant box on [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​192]].
 +   * I've added a docker-provision.sh to [[https://​gitlab.com/​cip-project/​cip-testing/​kernelci-docker|the CIP kernelci-docker]] and will add init-example shortly (or maybe it should take that from B@D?).
 +   * The 3rd party docker repos mirrorings e.g [[https://​gitlab.com/​cip-project/​3rd-party/​kernelci-docker-mirror|kernelci]] are still failing.
 +   * Ran a (lava-tool) test of BBB using a wifi connect for Vagrant on the host  to attempt to replicate [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​200|#​200]] but it worked ok.
 +   * Ran a BBB health check successfully with an email to the list.
 +
 +==== Monday 2018/09/17 ====
 +
 +=== toscalix ===
 +
 +   * Participated at the TSC meeting
 +      * Provided a status report about kernel maintenance final tasks and handover.
 +
 +=== SZ Lin (林上智) ===
 +  * Attended TSC meeting.
 +      * Reported status of kernel IRC meeting
  
 ==== Friday 2018/09/14 ==== ==== Friday 2018/09/14 ====
Line 10: Line 369:
  
   * Response to [[https://​github.com/​kernelci/​lava-docker/​issues/​45|issue 45]] from khilman suggesting either a U-Boot upgrade or a lab/​networking issue. ​   * Response to [[https://​github.com/​kernelci/​lava-docker/​issues/​45|issue 45]] from khilman suggesting either a U-Boot upgrade or a lab/​networking issue. ​
-  * 1:1 with toscalix. +  * 1:1 with toscalix.
-  * Ran a BBB health check successfully with an email to the list+  * Ran a BBB health check successfully with an email to the list.
  
 ==== Thursday 2018/09/13 ==== ==== Thursday 2018/09/13 ====
Line 31: Line 390:
 === rajm === === rajm ===
  
-  * I need to ensure that the correct ​scripts are passed to the correct container in lava-docker. connectBBB.sh needs to be copied to lab-slave-0. Trying lava-docker with b@d as a provider of builds still times out when trying to talk to the tftp server.+  * I need to ensure that the connect ​scripts are passed to the correct container in lava-docker. connectBBB.sh needs to be copied to lab-slave-0. Trying lava-docker with b@d as a provider of builds still times out when trying to talk to the tftp server.
   * Note that editing the health check on the host with emacs if it produces a backup file (ending in '​~'​) makes the built docker unusable!   * Note that editing the health check on the host with emacs if it produces a backup file (ending in '​~'​) makes the built docker unusable!
   * The section on multiple IP addresses seems to have gone missing from the wiki (or I'm not finding it!) investigating.   * The section on multiple IP addresses seems to have gone missing from the wiki (or I'm not finding it!) investigating.
civilinfrastructureplatform/journal.txt · Last modified: 2019/07/12 06:40 by SZLin