This is the journal followed by CIP devs during 2019

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Updated data in security tracker

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Attended the cip-dev IRC meeting
• Presented scripts to find used sources in the kernel
• Applied fixes to kernel security tracker
• Updated data in kernel security tracker

• Update kernel security tracker

• Updated testing Kernel images on AWS following release of v4.4-cip33 and v4.19-cip3

• Update kernel security tracker

• Review and apply additions to kernel config repository
• Update kernel security tracker

• Completed upgrade of lava.ciplatform.org

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Added support for configurable branches and remotes to the security tracker
• Added the CIP branches to the security tracker

• Ben Hutchings continued to apply security updates, see here and here.

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Reported on MDS mitigations to the cip-dev list

• Backported MDS mitigations and other speculation mitigation updates to 4.4

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.
• Send kernel collaboration discussion email

• Reviewing 4.19.39-rc series, reviewing 4.4.178
• Got access to LAVA, submitted example jobs.

• Ben Hutchings has reviewed the suggested package list for CIP core: no strong opinions on this, Laurence sent a mail to the cip-dev list to communicate this.
• Laurence chased members with a polite reminder (via private email) for the kernel 4.19 config files as per the recent request from Ben Hutchings

• Ben Hutchings reviewed the security tracker and applied some updates.

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Ben H. sent the mail to cip-dev requesting the 4.19 kernel configs to CIP members.

• At today's TSC meeting I introduced Laurence, who will substitute me in CIP. I will still be around a few more days to guarantee a correct hand-over.
  • I announced to Members that Ben H. will request from them 4.19 kernel configs to evaluate them, in the same line that what Ben did for 4.4.
  • The CIP Core Debian source packages list has shared internally at Codethink for revision. I will come back with output if any.

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

Started reviewing 4.4.173.

Set up kernel/push and pull to kernel org. Pushed first patches from mailing list to kernel.org.

• Updated lab-cip-renesas
• Added user for Jan K. to lava.ciplatform.org
• Submitted some DHCP client patches to cip-dev and 4.4 stable
  • Without these patches, DHCP client in v4.4.y may not process DHCP offer correctly, hence automated tests fail

• Discussed patch review mechanism with Pavel and Iwamatsu
• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• During the kernel maintenance team meeting Ben Hutchings communicated his intention to take over the 4.19 kernel config evaluation task.

• TSC meeting

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Updated AWS with v4.4.176-cip31 kernel and ran boot test
  • Healthchecks therefore now use this kernel

• Updated the bootloader on all boards in lab-cip-renesas
  • Each board now retains its own MAC address when the kernel boots up

• Pavel Machek

   Kernel meeting on IRC
   Started reviewing 4.4.176 patches
   

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Attended the security workgroup meeting.
  • Discussed the requirement and provided my opinion.

• Question about the CVE tracker to Ben HUtchings in the cip-dev mailing list.

• Started discussion on cip-dev with regards to arm64 configurations. Proposed that renesas-defconfig is used for RZ/G2 boards.
• Completed first version of CIP Testing Working Group.
• Added CIP Centralised Testing.
• Added Submitting a LAVA test job.

• Created and started to populate CIP Testing WG wiki page.
• Started to move testing related pages into the ciptesting sub directory.

• Attended to the TSC Meeting. Check the minutes

• Attended the TSC meeting.

• Attended the TSC meeting.
  • Asked the comments/ feedback from TSC with the purpose of master branch in CIP kernel

• There is an interesting discussion about how to coordinate and tract the patches being reviewed by the team.
  • The current tracking happens in the LF wiki (static). I suggested in cip-dev to move it to Gitlab wiki so you can modify it dynamically.

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• The linux-cip mirror is still not working
• SZLin reports the mention on the wiki of the branches has been done.

• The linux-cip mirror is not working properly. It seems the issue is on gitlab.
  • Reported in IRC. Others confirm
• Suggested to add to the repo description a mention to cip kernels being branches. It can be also mentioned in the wiki.

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• TSC f2f meeting in Nuremberg.
• Provided report from Ben Hutchings.
• How do we manage the kernel configs? So far we are following a black list approach. We want to follow a white list approach, specially for the new kernel.

• Attened TSC f2f meeting in Nürnberg.
• Discussed the mechanism of kernel configuration.

• Updated the cip-kernel-tests repo with a few initial test-definitions
  • cip-kernel-tests repository

• Attended the cip-dev IRC meeting.
• IRC weekly engineering meeting log
• Actions and links.

• Shared software updates survey
• Asked Daniel about the timetable for creating software updates wiki

• Proposed to present a paper for the OSSJ about the work done within the working groups instead of the general purpose presentation we have done several times already at this event.
  • The speakers would be the WG coordinators.
  • They would include as talking point the next steps of each WG and how to join the discussions.

• IRC weekly engineering meeting log
• Actions and links.

• Attended the cip-dev IRC meeting.

• CIP TSC f2f meeting and dinner locations confirmed (Nuremberg, GE during Embedded World '19)

• Attended the cip-dev IRC meeting.
  • https://irclogs.baserock.org/cip/%23cip.2019-02-07.log.html#t2019-02-07T09:00:23

• Updated linux4.4.y-cip-latest stored on AWS to CIP-30 for LAVA use

• Last week Pedro from Codethink configured the Meet Bot in the #cip IRC channel.
  • I tested it.
• Jan and Daniel need to create repos related with cip-core.
  • Instead of making them owners, due to the current policy that states that only a representative from each company can be owner of the cip group, I created a cip-core subgroup and made them both owners, together with Chris Paterson.
  • Notified them through cip-dev mailing list.

• Attended the cip security workgroup meeting.
  • Shared signing mechanism to members

• Agustin and Jon Ward from Codethink confirmed to assift to the TSC f2f meeting in Nuremberg on the 28th of February, during Embedded World 2019.

• Participated in the kernel dev weekly IRC meeting.
  • Made Chris from Renesas admin of the testing-results mailing list. He is now also moderator.

• Updated cip-lava folder on Amazon S3 bucket to include linux-4.4.y-latest and cip29 kernel builds
• Updated health-checks on distributed LAVA test setup to send emails to the cip-testing mailing list

• Attended the cip-dev IRC meeting.

• Set up email notifications on CIP distributed test setup with Ryan from LF

This is the journal followed by CIP developers to keep track of the work being done on behalf of CIP. It starts in 2018Q2.

• I retire at the end of the day - thanks all for working together on CIP!!
• Opened [https://github.com/kernelci/kernelci-backend/issues/94|#94]] in kernelci-backend to associate with our #203.
• I shall update the wiki with the version of the software in the snapshot release.
• Final 1:1 with toscalix - I will send out an email about the shapshot release to cip-dev. My LF account will need disabling by toscalix.
• Ran an iwg20m health check successfully, email sent to the list. Still power switcher issues.
• Ran a BBB health check successfully, email sent to the list.

• Attended cip-dev IRC meeting.

• There was already a process to proposed a new board. Yoshi reminded us all. I forgot

• Updated the wiki to document the downloadable snapshot box, I'll close #204.
• Ran a BBB health check successfully, email sent to the list.
• Ran an iwg20m health check successfully, email sent to the list.

• Proposed to CIP Members a light process to propose a new board to be supported by CIP.

• Fresh provision performed #149 - week 48 - which worked once the manual modification in #203 had been performed.
• #204 has been added to cover making a post v1.0 box available.
• Email to cip-dev discussing what updates are needed to the wiki now that a later box has been uploaded.
• Ran an iwg20m health check successfully but I had issues with the separate power switcher box dropping off the network causing failures, will review.
• Ran a BBB health check successfully, email sent to the list.

• Test downloaded that box and checked that a BBB health check ran.
• Uploaded a provisioned box (of early October) to latest box with gpg and sha256 files.
• Meeting with Renesas to brief them on B@D status before my retirement.
• Ran a BBB health check successfully, email sent to the list.
• Ran an iwg20m health check successfully, email sent to the list.

• Meeting with Renesas to sync up on B@D before Robert retires
  • We agreed on doing what we can to release the new box.
• I tried again to access the S3 and I could with the default pass word.
  • Gave access to Robert again and created an account for Chris Paterson.
  • Sent the costs for the last year to Yoshi and Jeff.

• Ran another internal codethink 'introduction to LAVA' session.
• Team meeting.
• Examined kernelci code for utils.db.find issues, so far unsuccessfully.
• Participated in the cip-dev IRC meeting.
• Ran a BBB health check successfully, email sent to the list.
• Ran an iwg20m health check successfully, email sent to the list.

• Reverting this kernelci-backend change remove limit when looking for test groups fixes issue #203 - but that change is to do with sending reports by email, so why it affects the web interface is not clear!
• I've opened #203 for the kernelci not showing builds as found last Friday.
• Ran a BBB health check successfully, email sent to the list.
• Ran an iwg20m health check successfully, email sent to the list.

• I wonder if the work SZLin and Daniel S. are currently doing to evaluate patches that do not apply can be automated on Gitlab with the jobs. Seem to me like an obvious case of static output that requires to public a report in a static format, a simple but repetitive process that should be triggered with every input change and an input with a controlled change rate and specific process.
  • Sent a mail to the mailing list about it.

• Ran a fresh provision for week 46 #149, however no builds are visible in kernelci - LAVA manages to extract them but nothing in the web interface!
• Ran a BBB health check successfully, email to the list.
• Ran an iwg20m health check successfully, email to the list.

• Ran internal codethink 'introduction to LAVA' session.
• Attended the cip-dev IRC meeting.
• Ran a BBB health check successfully, email to the list.
• Ran an iwg20m health check successfully, email to the list.

• Attended the cip-dev IRC meeting.

• Ran a BBB health check successfully, email to the list.

• Attended to the TSC meeting
• My CIP public calendar proposal is up and running. Yoshi did it.
• Mentioned that rajm is retiring December 1st.

• Added mention of #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.

• Added known issue to cover extending the timeout date for builds in kernelci and closes #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.

• Attended the cip-dev IRC meeting.

• Removed ToDo label from a lot of closed issues.
• Updated Known Issues to include method for BBB ssh connection from #153 and closed the issue.
• Ran a BBB health check successfully, email to the list.

• 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.

• Also closed #75, 79, #150, #160, #189 and #196.
• Updated known issues and therefore closing #196.
• Closed various issues we are not going to fix - #118, #137, #154 and #161
• Ran a BBB health check successfully, email to the list.
• Ran an iwg20m health check successfully, email to the list.

• Closed #190 submitter no longer has problem and not reproducible.
• Closed #158 - was fixed by 01551476f285f2cb5caa5f0e99bf483f24735123 back in July.
• 1:1 with toscalix.
• Ran a fresh provision for week 44 #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.

• Chris reported that the logs of the #cip IRC channel are not accessible. I confirmed it.
  • Reported it to Baserock project sysadmin

• 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.

• Ran an iwg20m health check successfully, email to the list.
• Ran a BBB health check successfully, email to the list.

• 1-1 with toscalix.
• Ran a BBB health check successfully, email to the list.
• Ran an iwg20m health check successfully, email to the list.

• Looking at mungaip's update of 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.

• Attended the cip-dev IRC meeting.

• Ran a BBB health check successfully, email to the list.
• Ran an iwg20m health check successfully, email to the list.

• 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.

• TSC f2f meeting in Edinburgh, UK, during ELCE 2018
  • Presentation of BuildStream: 10 min.
  • Ben H., Emmet and John joins the TSC meeting.

• Joined TSC f2f meeting via zoom

• Preparation of the TSC meeting
  • Preparation of the BuildStream slide deck.
  • Review of the agenda.

• 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.

• 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 #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.

• 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.

• Ran an iwg20m health check successfully, email to the list.

• 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.

• 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.

• Ran a fresh provision for week 40 (a couple of days late!) #149.
• Ran a BBB health check successfully, email to the list.
• Ran an iwg20m health check successfully, email to the list.

• Organising the trip to ELCE 2018.
  • Asked for confirmation about the TSC f2f meeting starting time and location (room).

• 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 issue 186.
• Added #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.

• Team meeting.
• Following bwh's approval MR 63 is now merged.
• Commented on Nguyen's comment on 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.

• 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.

• Tried running lava-docker away from the Codethink network but that still failed.
• I tried to replicate the wifi issue on the BBB #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.

• Create wiki page for stable kernel review.
• Confirmed that 4.4.y-stable is *NOT* vulnerable with this security bug (Fixed in 86949eb96466e “exec: Limit arg stack to at most 75% of _STK_LIM”)

• 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 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.

• 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 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 #187
• Ran an iwg20m health check successfully, email to the list.
• Ran a BBB health check successfully, email to the list.

• 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. #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.

• Attended the cip-dev IRC meeting.

• 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 #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?

• Sent email listing progress in weeks 30-38 to the cip-dev email list.
• New section on 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.

• Ran a fresh provision for week 38 #149.
• Met in the team meeting.
• Pushed a new version of docker-provision.sh to 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.

• 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.

• 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 #192.
• I've added a docker-provision.sh to 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 kernelci are still failing.
• Ran a (lava-tool) test of BBB using a wifi connect for Vagrant on the host to attempt to replicate #200 but it worked ok.
• Ran a BBB health check successfully with an email to the list.

• Participated at the TSC meeting
  • Provided a status report about kernel maintenance final tasks and handover.

• Attended TSC meeting.
  • Reported status of kernel IRC meeting

• Response to issue 45 from khilman suggesting either a U-Boot upgrade or a lab/networking issue.
• 1:1 with toscalix..
• Ran a BBB health check successfully with an email to the list.

• Demo of the existing state of containerisation with toscalix.
• Added tick box to #192 so that emailed notifications get thought about. IRC notifications don't work now because of the freenode anti-spam +r settings.
• Participated in team meeting.
• Multiple IP address setting documentation is now on the board page - it has been for some time - I just wasn't finding it! (See yesterday's comment for the original mention.)
• Fixed an incorrect internal section number cross reference in “B@D Setup and Configuration (2/5)”
• Raises my lava-docker issue at issue 45 having retried the BBB health check with docker against B@D this morning.
• Realised the default (new) health check for cip28 was missing a notify section, added that and re-ran the check and the email went to the list.
• Attended the cip-dev IRC meeting.
• Built cip28 on B@D and a successful health check - but no email to list.

• 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!
• The section on multiple IP addresses seems to have gone missing from the wiki (or I'm not finding it!) investigating.
• Opened #200 so that the networking issues that have been seen in some situations get addressed.
• Ran a BBB health check successfully with an email to the list - though that's taking a little time to get through. I had issues running B@D using the wifi connection and Ihad to revert to using ethernet to get the healthcheck to run. Email now received ok.

• Added some container todo points to tickboxes in #192.
• 1:1 with toscalix.
• Ran a BBB health check successfully with an email to the list.

• Created the kernelci-docker and lava-docker repos.
• Created the kernelci-docker-mirror and lava-docker-mirror repos in 3rd-party subgroup.

• Added another 2 points from 192 to yesterday's list.
• Added PR 24 for kernelci-docker.
• Attended the cip-dev IRC meeting.
• Ran a BBB health check successfully with an email to the list.

• I think the following need resolving to get the docker implementation of B@D running:
  • Get lava-docker into kernelci swarm.
  • FILE_SERVER_URL = “http://127.0.0.1:8082/” in kernelci flask though maybe this should be in upstream?
  • Create gitlab repos for our mirrors.
  • We need a mechanism for updating health check to use the most recent build of kernel.
  • We should build initramfs on host and then copy to kernelci-docker as part of (initial) provisioning.
  • Add beaglebone to the provision and the health check.
  • Also give the lava docker a history (as kernelci-docker has)?
  • Update kernelci-build automatically on host so that the key matches the currently running kernelci docker.
  • Add installation of expect to lava-docker and our login script for the BBB.
  • Licence headers need adding.

• Confirmed that lava-docker built on my home desktop without the network problems I've been experiencing. So I assume any problems are one of ubuntu (at home) vs debian, my laptop network settings, corporate network settings. May not be relevant as the lava-docker will need merging into the kernelci swarm which doesn't experience this problem.
• Ran a fresh provision for week 36 #149. I had to run QEMU twice to get that to pass and the output showed a slow install of packages (apache) that I don't remember seeing before. I will check against the example output on the wiki. Check made and output is as before, I suspect a slow internet connection made that output scroll slowly and therefore be more apparent.
• Ran a BBB health check successfully with an email to the list.

• Attended TSC meeting.
  • Listed candidates for CIP kernel maintenance.

• Added a cp of a local beaglebone-back.yaml into the lava docker to Dockerfile, however it is not managing to retrieve the build from the kernelci container. In addition consideration needs to be given as to where the initramfs is to be built and stored.
• I don't see the networking failures when starting containers with docker-compose, I think the lava-docker will need setting up with compose anyway so I expect this error will cease to matter. Reading up on 'compose'. No, it already uses compose, it's swarm mode that's different.
• Ran a BBB health check successfully with an email to the list.

• 1:1 with toscalix.
• I've modified my local copy of flask_settings to set FILE_SERVER_URL and am now able to retrieve builds - see #197.
• Initially wasn't seeing builds appear in the kernelci docker - but there were in the image - will keep a watch on this!
• Will look at sangorrin's commits to the kernelci docker wrt being unable to download builds but I think from his comments that it's a general problem.
• Attended the cip-dev IRC meeting.
• Ran a BBB health check successfully with an email to the list.
• Returned from holiday.

• Participated in the cip-de IRC meeting
  • Still pending the request to bwh for advice about the creation of a group account in kernel.org bwh advice is important because we assume that to create it we will need support from him.
  • 4.19 seems to be the next LTS kernel. When is expected to have a decision/announcement from Debian about the next LTS kernel?
  • #192 is the ticket to follow if you are interested in rajm work about containerization of B@D
  • The testing infra is in place: https://kernelci.ciplatform.org/
    • An admin is required. Suggested to discuss it at TSC level since there will be a person assigned. This work cannot be on best effort basis.
• Implemented the Gitlab roles policy at group and subgroup level. It is not for me to decide how to apply it at repo level. That correspond to the maintainers of each repo.
  • Informed about the execution of the policy.
  • Suggested to move cip-core repo to a new subgroup.

• Attended cip-dev IRC meeting.
  • Sent the overlayfs backport patches

• Participated in the weekly cip-dev IRC meeting.
  • I asked where the new kernel repo will be hosted, since the current one, in kernel.org, is under bwh personal account, like the -rt one is under Daniel W.'s.
    • Asked through cip-dev to bwh for advice.
• Working on a proposal for the Linux Foundation about the new role bwh will play as mentor of the kernel maintenance team.

• Attended cip-dev IRC meeting.

• Ran a fresh provision for week 34 #149.
• Reviewing a document prepared by mungaip of the steps he needed to get B@D provisioned behind the Renesas proxy. The intention is to add an item to the Workarounds section.
• Ran a BBB health check successfully with an email to the list.

• TSC meeting
  • The proposal I did to manage the maintainers permissions on Gitlab.com repos was approved. Now we need to implement it.

• Attended cip-dev IRC meeting.

• Responded to mungaip's latest state in #195 - his problems appear to be proxy related, I'll check up on various proxy related issues ticketed previously (that's #99) though his issues are slightly different; #99 suggests there should be an item about proxy problems in Known issues which hasn't happened!
• Ran a BBB health check successfully with an email to the list.

• Various attempts to get the docker images to start without networking failures. Will investigate swarm mode as kernelci in the version I'm using (lucj) doesn't have this problem - and the master version does!
• I have installed vagrant 1.9.1 and virtualbox 5.1.38 (the identical versions to mungaip ) and install_dependencies.sh runs successfully for me.
• Created #195 and #196 to address the issue apparently with Vagrant 1.9.1 and documentation on how to install a version of virtualbox that cooperates with that version.
• Emailed Operations to hand back the Windows 10 machine that we've been using to test B@D in that environment.
• Ran a BBB health check successfully with an email to the list.

• Attended cip-dev IRC meeting.

• Trying to test mungaip's issue with Vagrant 1.9.1 (the default version in Debian stretch) which doesn't work well with the version of VirtualBox also provided by stretch.
• 1:1 with toscalix.
• Discussion with mungaip on IRC about the issues he's having with provisioning a B@D instance.
• Ran a BBB health check successfully with an email to the list.

• Meeting with Ben Hutchings to brainstorm and prepare the hand over to the new maintainer.
• Ben informs me about l1ft. I comment on IRC Ben is on it.

• Created a script for the provisioning of the 2 docker repos and the build script however the network problems within docker are causing the script to exit (not unexpected!)
• Tried again to extract builds from the lucj version of kernelci-docker I can wget from within the container but not externally.
• Added further points for the issues in #192
• Ran a BBB health check successfully with an email to the list.

• Updated #192 to list - in the description - the issues discovered so far which will need incorporating into CIP's version of the docker containers.
• Started the kernelci-docker to check problems were as before - but also verifying that it does run alongside lava-docker.
• Also tried the lava-docker test from the office network - using the B@D builds and still get a failure - having to use the host IP rather than localhost as the port isn't forwarded to the container.
• Ran a BBB health check successfully with an email to the list.

• Chair of the weekly IRC meeting
  • Sent the minutes to cip-dev mailing list.
• Sent a proposal to cip-dev to manage the user roles in gitlab.com

• Intending to try the BBB health check on lava-docker using our B@D builds - but I still see the UBoot timeout.
• I tried provisioning lava-docker without VPN enabled (from outside the company network) and I still had timeout failures.
• A fresh provision for week 32 #149
• Ran a BBB health check successfully with an email to the list.

• Based on the agreement that took place at DedConf 2018, moved the CIP-dev IRC meeting an hour earliues, so people at JST can join.

• I've successfully built with beaglebone enabled - using connection_command. At the moment it is failing in UBoot though to get here I'm having to open a connection to the BBB from the host and leave it logged in (as we did in the early days of the project) will eventually need a login script adding. The IP address of the host is currently hard coded in boards.yaml.
• With a fresh build of the docker image for lava-docker the QEMU health check just works. I wonder whether the network issues I'd been having cause the workers to go irreparably offline? Now looking to build with a beaglebone board configured.
• Ran a BBB health check successfully with an email to the list.

• 1:1 with toscalix
• The DNS failures on needing to restart docker are actually networking failures.
• The health check is not running because the worker is marked as offline. I've tried to put it online without success and created another one which also stays offline.
• Ran a BBB health check successfully with an email to the list.

• The LAVA docker device is marked as having a health check but it hasn't run, investigating why.
• Ran a BBB health check successfully with an email to the list.

• I have successfully built lava-docker from here - I had to move the docker directory from /var/lib to give me more space and to restart docker a number of times on getting DNS failures. Also added some `apt-get update`s to the build-lava script.
• Ran a BBB health check successfully with an email to the list.

• Submitted #12 to kernelci-docker so see if there's a comment, not sure whether it's my settings or how I'm running the interaction.
• Submitted #11 to kernelci-docker otherwise start.sh doesn't keep a clean version.
• Ran a BBB health check successfully with an email to the list.

• Told Fabrizio from Renesas that the patch review will take a few days since Ben H. is at DebConf.
• Ben H. reviewed the CIP Core packages prioritization policy and sent it to cip-dev. I went over it.

• Still getting 500 errors when I start the containers from the original repos and try a build. The build.py file needs modifying on each restart of the containers, this needs scripting? I tried a fresh start of docker (and the laptop) but that still gave the same problem.
• Closed #178 - it should have been done last week when the associated MR was merged.
• Sent a status of CIP testing email to the cip-dev list.
• A fresh provision for week 30 #149 - no longer need to add a local test section with last week's merge.
• Issue #193 has been closed by Zoran, it was a problem with his initialisation script.
• Ran a BBB health check successfully with an email to the list.

• Sent to Jeff the mails related with the suggestion to contact Mitsubishi Heavy Industry as potential candidate to join CIP.
• Catch up with mails from CIP after several week travelling and on vacation.

• Attended to the CIP TSC meeting
  • Reported about bwh and rajm latest work.
  • Several meetings related with kernel maintenance and Debian LTS are expected during DebConf 2018 in which bhw presence would be needed. No schedule yet.
  • A mail was sent by Daniel Sangorrin to cip-dev about the criteria to be used to prioritize the package list to be sent to Freexian / Debian LTS.

• Looking at #192, managed to get start.sh in the original repos to run to completion - I had to `sudo service docker restart` numerous times to get there - but I'm getting a 500 error on running the kernelci-build/build.py script.
• Investigated #190 and updated with a question to the OP.
• Ran a BBB health check successfully with an email to the list.

• I've updated Virtualbox to 5.2.16 - looking at #193 - and after getting the vagrant plugins up to date a pre-existing VM successfully booted and a fresh provision also worked ok.
• Ran a BBB health check successfully with an email to the list.

• Updated Vagrant to 2.1.2 to investigate #193 I don't see the error, will update to Virtual box 5.2.16 and see if that produces the error.
• Merged MR 61 - making the final output of create_test.sh more appropriate to the user's situation and closing #178.
• Merged MR 60 - using a fixed version of LAVA so we can check any new version before incorporating it - and closed the associated issue #185.
• Merged MR 62 - the moving to a local test - and closed the associated issue #191.
• Ran a BBB health check successfully with an email to the list.

• Created MR 62 to use a local test for the BBB health check to make the test more self-sufficient.
• Opened #192 to cover the docker work.
• Ran a BBB health check successfully with an email to the list.

• I'm getting errors when running docker-compose on lava-docker - various packages being unavailable - I guess there's a problem with apt/sources.list at least in the image. I restarted the docker service and that appears to have resolved most of the problems, I guess it didn't like being moved from the home network to the codethink one. Still getting a failure - wget: unable to resolve host address 'images.validation.linaro.org'
• Ran a BBB health check successfully with an email to the list.

• A fresh provision for week 28 #149 with a local test section. Initially had problems with the QEMU test due to / running out of space, I did a make clean in linux-cip to resolve, I'm not sure why this doesn't happen on all clean tests?
• Ran a BBB health check successfully with an email to the list.

• Created kernelci-docker issue #22 to cover the failure to download the kernel.
• Noted kernelci-docker issue #11 I see this issue but we don't have the problem in b@d.
• The build artefacts are uploaded to the kernelci-proxy container, but I think the retrieval is only happening in kernelci-frontend.
• Ran a BBB health check successfully with an email to the list.

• Failing to get the kernelci docker to start with dev-start.sh- getting docker compose version is unsupported - an error which on the face of it is incorrect - as I have the latest version of docker-compose.
• Created version of the frontend with logging enabled in nginx and verified that the failure is happening in that container. I see that the instructions for copying an archive from a kernelci m/c to a container-ised version only copy the logs, does that mean that the main focus is on the logs?
• Ran a BBB health check successfully with an email to the list.

• I'm getting failures of b@d to start up when on wifi and also connected to work VPN I guess this is DHCP issues.
• I am getting 404 errors when attempting to retrieve the build artefacts from the docker image. ISTR getting similar errors in the early stages of B@D development. I will research it. This is the change to server.py in configure_singledev.sh - though even with that change I'm still getting 404's
• Looking at the LAVA docker.

• I've successfully built a BBB image and uploaded it to the docker kernelci.
• Ran a BBB health check successfully with an email to the list.

• Ran the kernelci docker image and am attempting to build with kernelci-build but am currently getting a 413 error (Request entity too large) when the build script attempts to upload the results. Reviewing the B@D settings to see where size limits get set.
• Tweaked my populate script so that it builds linux-cip using the latest tag.
• I see from the fresh provision I did yesterday that backports is now on LAVA 2018.5.post1 which probably makes merging MR60 more important.
• Attended cip-dev IRC meeting.
• Ran a BBB health check successfully with an email to the list.
• Created a branch with a working BBB health check localTest.

• Looking at moving B@D to containers and investigating the kernelci instances.
• A fresh provision for week 26 #149 having missed a week because of holiday. All successfully done (with the local check).
• Built the latest v4.4.138-cip25 kernel for BBB on my VM and ran a local health check on it successfully with an email to the cip-testing-results list.
• The default BBB health check fails “Unable to open test definition 'common/dt-selftests.yaml'” I've opened #191 and assume the linaro repos has changed.
• Returned from holiday.

• Attended TSC meeting.

• I'll be away holidaying for a few days…
• However a test of the iwg20m is not sucessful. #189 opened. The kernel builds ok but I'm currently unable to connect via USB to the board - there's no problems with similar cabling to the BBB.
• Done a fresh provision of B@D on a Windows 10 machine and verified that kernelci and the QEMU & BBB health checks run ok (using initramfs built using populate.sh)
• I've pushed an update to boxPopulate and have verified that it runs ok (on Windows 10)
• Attended cip-dev IRC meeting.
• Ran the BBB health check successfully with the email going to the cip-testing-results list. Worked first time today.

• Created MR61 to handle Issue #178.
• Also ran the iwg20m heath check successfully with an email to the list.
• Ran the BBB health check successfully with the email going to the cip-testing-results list. A couple of failures before the working one 'send-reboot-commands timed out after 119 seconds' and 'matched a bootloader error message'.

• Updated MR60 to use an Debian snapshot for LAVA 2018.4.
• Updated the block diagram on the features page to reflect the versions provided by the git repos and opened #188 to cover consistency issues between the diagram and the rest of the text on that page.
• An iwg20m health check also ran successfully with the email going to the cip-testing-results list.
• Ran the BBB health check successfully with the email going to the cip-testing-results list.

• Attended TSC meeting.

• Work on B@D Friday talk.
• Collaboration with cpaterson wrt the iwg20m problems and installing B@D.
• More updates to the wiki page.
• Ran the BBB health check successfully with the email going to the cip-testing-results list.

• Updates to the wiki features page so that the version of B@D components if run from git are recorded.
• Created MR60 to handle #185 I will take on board bwh's comment and revise it.
• Attended CIP Codethink team meeting
• Tried running the BBB test with a test section identical to the renesas one - gives around 10 seconds shorter run time mainly due to it not downloading a git repos, we might want to replace the BBB test or have this as an alternative - especially if testing without remote access.
• The remote power switcher had problems connecting to the local network which caused a lava-tool job to fail with infrastructure errors. As a consequence LAVA then set the health of the iwg20m to unknown which caused a health check to run - which also failed- because the power switch was off line! Fortunately when it came on line the HC worked and an email went to the list.
• Attended cip-dev IRC meeting.
• Ran the BBB health check successfully with the email going to the cip-testing-results list.

• CIP Codethink team meeting
• Linux Format published an article about CIP. Codethink's name is wrong.
• We have invested a significant amount of effort in making the Renesas board reliable with LAVA and we haven been able to identify the root cause of the issue. We will not dedicate further time at this point. We will wait for Renesas to make an evaluation.
• For OSSJ the plan is:
  • To have a new kernel released.
  • Talk prepared. Daniel Wagner answered the questions Agustin had about the -rt process.
  • Docu and bugs from B@D up to date.
  • Undetermined at this point if the kernel config evaluation of sent by Moxa can be done before the event.
  • Codethink will participate at the CIP with Sudip and Agustin.
• Proposed to SZ Lin a report about the kernel stable patch review experience through cip-dev
• The blog post about Codethink's work will be published next Monday.

• Ran a successful iwg20m HC but previous ones had failed - no apparent software change between the non-working and working tests.
• A fresh provision for week 23 #149 some issues with connectivity (git clone timing out) and lack of disk space causing QEMU to fail but eventually both worked.
• Tried running the iwg20m health check with the Renesas core-image-minimal-iwg20m.cpio.gz but that exhibits the same timeout on starting kernel.
• Ran the BBB health check successfully with the email going to the cip-testing-results list.

• Comparing a test of iwg20m with the same kernel one working one not working shows that the test doesn't get as far as 'Uncompressing Linux' so the test is failing early in initramfs. In that batch of tests 3 worked and one failed.
• It appears that specifying the initramfs fails to work with U-Boot so a u-boot header needs to be added.
• Built iwg20m kernel with EXT4 support and am successfully booting via u-Boot and am trying to provoke it to hang on boot as it does in LAVA. So far in this environment boots are 'just working' - not the desired outcome!
• Ran the BBB health check successfully with the email going to the cip-testing-results list.
• 1:1 with toscalix.

• Had issues with the remote power switch getting a new address more frequently with DHCP.
• Attended team meeting.
• Discussed with bwh my problems with the iwg20m - it needs to be built with EXT4 support or tested using our initramfs.
• Attended cip-dev IRC meeting.
• Ran the BBB health check successfully with the email going to the cip-testing-results list.

• Attended cip-dev IRC meeting.

• Reply from Neil Williams about the QEMU locking up issue. I've replied to it with what information I can provide but as the device has now health checked (and the VM rebooted) it's hard to provide the full information.
• Another failure from the iwg20m - in order to get an attempt working I had to re-power cycle the remote power switcher so that it reset its IP address (addresses having changed in the new office setup).
• Ran the BBB health check successfully with the email going to the cip-testing-results list.
• Successfully setup equipment in new office.

• Sent a couple of interesting links to the cip-testing-results ML for the new stable reviewers.

• Created a report for the CIP TSC meeting. I cannot attend today.
• Worked on issue #187.
• Worked on the OSSJ presentation.

• Attended TSC meeting.

• Packing away equipment for the office move this weekend.
• Tested script to populate a provisioned instance with HCs and build initramfs and kernel (built for BBB) #150.
• Ran the BBB healthcheck successfully with the email going to the cip-testing-results list.

• No response yet from lava-users about the QEMU problem - however the QEMU health check ran ok today, but I'll see if the bug needs reporting once there is feedback.
• Attended cip-dev IRC meeting.
• Anh The reported that the kernelci build script doesn't copy uImage onto the webserver. I checked out build.py and edited patterns in that file which then copied over uImage however the kernelci webserver doesn't report it.
• Ran the BBB healthcheck successfully with the email going to the cip-testing-results list.

• Attended cip-dev IRC meeting.

• Sent email to the lava-users list asking about the 'maybe a bug in LAVA' problem mentioned below.
• Created a skeleton script for the configuration of a new instance once the VM is provisioned.
• 1:1 with toscalix.
• Done a fresh provision for week 21 of #149 all 3 health checks working first time.
• Runs the BBB healthcheck successfully with the email going to the cip-testing-results list.
• Replied to Anh The's support request email.
• Tried U-Boot of the iwg20m using /dev/mmcblk[0-2]p2 as root device. k0 gives a kernel panic the others hang waiting for the root device. Get similar results with the yocto build kernel.
• The QEMU health check is failing to start - or maybe the error at the head of the page “Unable to parse invalid logs: This is maybe a bug in LAVA that should be reported.” is preventing the display of the output? Asked in IRC #linaro-lava channel on Friday but I didn't see any response. Still getting this error after rebooting the VM (and also the host laptop).

• Sent to Mae the content of the post about Codethink activity. I forgot to send it last week.
• I promoted the recently published blog post through twitter and linkedin.

• I also closed #183 as it belonged with #184.
• 1:1 with toscalix.
• BBB health check runs and email sent to list (IWG20M HC fails)
• Updated health check to new kernel for BBB and IWG20M
• Updated VM to v4.4.130-cip23 and successfully built kernel for BBB and IWG20M

• Updated the wiki with fragments of the IWG20M output and added link to full output and have therefore closed #184.
• Ran a successful IWG20M health check after manually poweroff'ing the board and then resetting the remote switch to that state (with an email to the list). I then repeated the success but then got around 50% success/failure ratio on the whole test sequence. Updating #186.
• IWG20M still failing to health check.
• Health check sent to list with BBB from new instance.
• Provisioned fresh VM with latest master (and hence LAVA 2018-4), set up email server and notify for health checks.
• Attended cip-dev meeting.

• Added Daniel S. to the cip-testing-results ML.
• cip-dev meeting. The best one so far.

• Attended cip-dev IRC meeting.

• Mirroring CIP 4.4 -rt kernel into gitlab
  • Repo created.
  • Permissions granted to the right people
  • Gitlab configured.
  • Mirroring triggered. Waiting to be completed. This can take long on gitlab.com
    • Mirroring finished and I communicated to the cip-dev ML.
• Wrote a blog post about Codethink's activity in CIP. It is being reviewed by the CIP team.
  • Sent it to LF for review.

• Updating wiki so that the results match those from the latest version of LAVA - QEMU and BBB done, I just need to persuade a IWG20M HC to complete successfully. Also I've removed mentions of v1.0 from the test cases page.
• Opened #186 tracking reliability of the Renesas board.
• Opened #185 to track work done on keeping a stable version of LAVA in B@D provisioning.
• Ticked 3 items in #184 just need to update the expected output.
• Responded to Renesas question where kernelci / build.py was failing - the .git subdirectory had been removed (deliberately) because disk space was running out.
• Health check sent to list with BBB.

• I won't attend to today's TSC call.
  • Communicated to Members.
• Registered for OSSJ 2018 as speaker.
• Report weeks 18 and 19 sent to cip-dev mailing list.

• Attended TSC meeting.

• bwh approved MR59 and I've merged it.
• Updated reference test case wiki so that it matches the LAVA submit job behaviour.
• Successful HC of iwg20m with email to list though the next test failed.
• Further attempt to test the iwg20m kernel with U-Boot directly - now getting 'Bad Linux ARM zImage magic!'. Further investigation to get parameters passed correctly to kernel.
• Health check sent to list with BBB.

• Discussion with bwh on fixing the LAVA version that we are installing from backports.
• Updated reference test cases wiki page to provide information for when running with LAVA 2018-4 - leaving the old info in place for users with the 2017 version.
• Built LAVA install packages from these instructions but they are for version 2018.4.
• 1:1 with toscalix.
• cip-dev IRC meeting.
• Health check sent to list with BBB.

• cip-dev meeting
• Filled out the info requested to all Members by Jeff related with the OSSJ.
  • Sudip will attend to the event and help at the booth.

• Attended cip-dev IRC meeting.

• I've updated the wiki in line with the Health Check changes mentioned with issue #184.
• Opened MR59 for the provisioning change.
• #184 has been opened to cover necessary repos and wiki updates for B@D use with 2018.4 of LAVA.
• Re-provisioned a fresh instance, script produces an error due to it's assumption that python 2.7 will be installed. I then built BBB and iwg kernels and health checked successfully all but the iwg20m. Some usage changes necessary in health checking.
• Health check sent to list with BBB.
• Attempting to get a modified build with debugging of the iwg20m kernel to U-Boot, getting Error: unrecognized/unsupported machine ID (r1 = 0xc7fadefa).
• Response on lava-users is that the failure in install LAVA is an issue with the Debian backports.

• Provided report about Codethink activities within CIP
• TSC call
  • Mentioned that Codethink requested one ticket for OSSJ. We send an engineer that will help at the booth.

• Attended TSC meeting.

• Health check sent to list with BBB.
• Failure on iwg20m - tried with core-image-minimal-iwg20m.cpio.gz but then amending it to the built in the VM then worked.
• No answer seen on the IRC question from yesterday. Sent email to lava-users, discussion ongoing.

• #183 is due to the 2018 LAVA ending up in stretch-backports, I'm investigating how easy it would be to install LAVA from the Linaro release tagged version. And I've asked a question in #linaro-lava about this.
• 1:1 with toscalix
• Had an error on a fresh provision - verified that the problem happens from master - so created issue #183.
• Health check sent to list with BBB.
• Still failures on the IWG20M board. Had a successful run using the Yocto built .
• Attended cip-dev IRC meeting.

• Attended cip-dev IRC meeting.
• Send out the result of Kernel patch review - 4.4.129 to cip-dev

• Health check sent to list with BBB.
• Having failures (as before) on the IWG20M board. Had a successful run using the Yocto built core-image-minimal-iwg20m.cpio.gz but our initramfs still fails.
• Further discussion on #91 re. QEMU HC errors.

• Updated the minutes for the coming TSC bi-weekly call.
• Attended to the TSC bi-weekly call.

• Attended to the TSC bi-weekly call.
• Called an internal meeting for updating the status of Moxa CIP kernel maintenance team.

• 1:1 with toscalix.
• Health check sent to list with BBB.
• Having failures (as before) on the IWG20M board.
• Added comment to #91 where a user had been having an error.
• Updated wiki to include #181 IWG20M configuration and closed the issue.

• Created and sent the Codethink report weeks 14 - 17
• Meeting with rajm
  • Discussion about documenting the new support of iWave from Renesas on B@D: #181 and #182

• Initial test of the kernelci in docker - some additional reading and investigation is needed.
• Attended cip-dev IRC meeting.
• The BBB and Renesas Health Checks ran with emails sent to the list.
• Corrected typos on features page
• Verified that #154 is still a problem - was wondering if it had gone away.

• Attended cip-dev IRC meeting.
• Start to review stable kernel patch - 4.4.129.

• cip-dev IRC weekly meeting. Minutes.
• Codethink CIP team meeting

• Ran a full provision of a clean VM #149 and ran tests for QEMU/BBB/iwg20m successfully - though each configuration failed initially.
• Closed #167
• Debian had updated Virtual box which meant that Vagrant no longer ran - I updated Vagrant to version to handle this.
• The IPSwitch IP address had changed again so iwg20m01.jinja2 needed manual editing to take account of this.
• The BBB Health Check ran with an email sent to the list.
• The Renesas Health check eventually ran after 4 timeouts at 'starting kernel' - once it ran an email went to the list.

• Paper for OSSJ 2018 approved. I will provide the talk.
  • Notified Daniel W. and bwh
  • LF fixed the info about my profile.
• Provided credentials for bwh to access AWS
• bwh showed me the kernel config from Members stored in repos in gitlab.
• I will be giving an introductory talk about CIP in a local Open Source event in Malaga, Spain called Opensouthcode.

• The merge request was approved by bwh and merged. An email was then sent to Renesas detailing how to set up tests with that board.
• Successful run of 'daily' BBB and Renesas health check - results emailed to list.
• Updated #149 to move the next expected provision along a week.
• I've done a fresh provision of B@D with the Renesas changes and that built kernel health checked first time. I've therefore pushed the changes and created a MR.
• 1:1 with toscalix

• Asnwered a comment on lwn.net
  • Sent the article to cip-dev
• How can we forward the 4.4-stable mails to cip-dev since the linux foundation mail server does not allow to bounce them to another mail account in its own server?
  • Added a new folder to S3 called cip-kernel.
  • Created an account for bwh

• Sent a reminder of the cip-kernel repo move.
• Cannot access mailman. Nofified to Jeff.
• Sent agenda for today's cip-dev IRC meeting
  • Minutes sent to cip-dev
• linux-cip moved inside the cip-kernel subproject.
  • Notified.

• Successful run of 'daily' BBB and Renesas health check - results emailed to list.
• Attended cip-dev IRC meeting.
• Noticed that a local ramdisk (iwg) test got further and then the health checks started failing. Rebooted the VM and the HC worked and (after another VM reboot) again a better - but not quite successful test with local ramdisk. Output is here.
• On adjusting the expected prompt in the health check the renesas board works with our initramfs. However the test working or not appears fragile - a (expected) non-working test can cause subsequent good tests to also fail. Discussion ongoing with patersonc on this.
• Team meeting.

• Successful run of 'daily' BBB and Renesas health check - results emailed to list.
• I had to reconfigure the device settings as the remote power switcher's IP address had changed.
• Discussion with bwh about the failures with our ramdisk, I edited the device dictionary to incorporate more of the U-Boot settings but without success.

• Conversation with bwh
  • ARM64 and LTS. ASked him a few questions about the process to add a new architecture.
  • Kernel LTS patch review process. Discussion about how to onboard Moxa developers.

• Added report about Codethink's activity in the TSC meeting minutes document.
• Attended to the TSC bi-wwekly call
  • Asked through cip-dev to bwh when if there is any forecast or discussion about when Debian intends to support ARM64 in LTS.

• Edited wiki page of cyber security for EDSA part
• Sent email which is related to kernel maintenance to dev-cip ​
• Attended to the TSC bi-weekly call

• Created and edited wiki page of cyber security Cyber security wiki

• Edited #167 with a description of the Renesas issues below and a link to the output of running the test with the VM built initramfs used for the BBB.
• Successful run of 'daily' BBB and Renesas health check - results emailed to list.
• The Renesas health check with the kernelci artifacts was timing out. I reverted to using the yocto ones which worked correctly. I tried using lava-tool with a notify section (I'd been using lava-tool in yesterday's successful tests) and that worked! I put the HC back to use the kernelci kernel and removed the notify section that also worked. I have now edited the HC to use a pared down notify and that still works.

• Conversation on IRC with Cris Paterson and Ben H. about Debian LTS process.

• Team meeting
• I have a kernelci built kernel and dtb file working with the Renesas board. Still need to remove dependency upon the yocto core-image-minimal-iwg20m.
• Successful run of 'daily' BBB and Renesas health check - results emailed to list.
• Built BBB v4.4.126-cip22 kernel and set the health check to use this version. Successful further test of this.
• Attended CIP-dev IRC meeting.

• Sent downtime announcment for the cip-kernel repo move.
• Codethink cip Team meeting.
• IRC cip-dev meeting: minutes
• Created a new subgroup in Gitlab: cip-kernel.
  • Added a new repo cip-kernel-config
  • Provided permission as owner to bwh.
  • cip-kernel tests moved.

• Send meeting agenda and status of team member to cip-dev

• Successful run of 'daily' Renesas iw20gm health check - results emailed to list.
• Successful run of 'daily' BBB health check - results emailed to list.
• Fresh re-provision of VM and successful BBB test, ticking week 14 of #149 (a few days late!)
• Pushed a branch for the latest Renesas changes renesasWorking.
• Created new VM from renesasWorking and successfully ran a Renesas health check on it.
• Cleaned up some of the old branches from my forked repos.

• Successful run of 'daily' BBB health check - results emailed to list.
• Discussion with tpollard over getting Renesas and B@D working. (see journal from Oct 30th 2017)
• We removed the networking related lines from iwg20m01.jinja2 - the uboot_ipaddr_cmd and the base_ip_args lines - increased a few timeout values and the Renesas health check passes - when using the yocto built kernel.

• Successful run of 'daily' BBB health check - results emailed to list.
• Closed #177.

• Successful run of 'daily' BBB health check - results emailed to list.
• Updated wiki in accordance with #177, I've also added some text to cover the case where the user needs to modify the Vagrantfile. The provisioned box case needs some thought - though there isn't one with this configuration yet!
• Wiki updated to add link to older version of the document if user is using the provisioned box (or v 1.0 release from git).

• Based on the request from Moxa (SZLin), I move this diary from the CIP Testing to a general page so they also can use it for their work, as Codethink does, beyond testing tasks.
  • Added a message on the previous journal (testing) warning people from writing there messages.
  • Copied the content here.
  • The complete task is described in #179
• Sent schedule proposal to Moxa for our IRC weekly meeting
  • Meeting set.
• Sent weeks 11 to 13 report to cip-dev
• Promoted the Spotlight article in cip-dev which I believed nobody has before.
• Some members has already shared internally some packages they are interested on including in CIP Core.
  • Shared them with Ben Hutchings. I checked them out. A sheet should be created to manage them better.
• Prepared and attended to the TSC bi-weekly call.

• Successful run of 'daily' BBB health check - results emailed to list.
• Created MR57 to deal with issue #133 - the LAVA source link. Some discussion with bwh as to whether this is the correct approach and what the link needs to be - see the issue
• Fixed errors in the wiki.
• MR55 has been merged so #159 has been closed.
• Team meeting.
• Another test of Renesas board getting the eth speed change now on the host and still see the uboot timeout.
• Changed status of #177 to Doing as it's dependent task #159 has been closed.

• Successful run of 'daily' BBB health check - results emailed to list.
• Edited the wiki page to mention description setting for email and tied that into use of create_test.sh.

• Successful run of 'daily' BBB health check - results emailed to list - now including kernel version as standard.
• Updated test cases page to update prerequisites.
• Closed #166 the remote PDU is controlled successfully from the health check.
• Updated #167 to include latest run log.

• Successful run of 'daily' BBB health check - results emailed to list.
• Edited the BBB health check description to embed the kernel version and reran the HC and the email now contains useful data. #118 has been edited to log this.
• Meeting with moxa.
• Added MR56 to automate the test description modification - which has now been merged.

• Meeting with Moxa
  • Advised Moxa to send their kernel configs to the cip-dev mailing list, like the rest of Members did, to evaluate their needs.
  • Talked about having one Moxa kernel dev, at least, joining the LTS process, mentored by Ben H.
  • Advised MOxa to take the lead in the CIP Core related areas that are strategic for them.
• Promoted the CIP Spotlight article.

• Successful run of 'daily' BBB health check - results emailed to list.
• Opened #177 to be addressed once #159 is closed.
• Ran a fresh provision and health check to fulfil week 12 of #149 and added a couple more weeks to the future provisioning.
• Team meeting.

• updated minutes for the TSC bi-weekly call
• TSC bi-weekly call
  • A meeting with Moxa devs is needed
• Presented a paper for a talk about the CIP kernel to OSSJ
  • Pinged both kernel maintainers to let them know about this talk and request help from them for the content. They agreed to help me.

• Successful run of 'daily' BBB health check - results emailed to list. Again an alternate location of home office.

• Back in the office and ran 'daily' BBB health check - results emailed to list. No manual intervention required again to fix host IP.
• Closed #139 now that MR 55 is complete.
• Updated the VM iw20gm build to 4.4.120.
• Successfully connected via ssh to the BBB and updated #157 with my (at the moment) manual method.

• Team meeting and 1:1
• Merged in MR 53 after bwh's approval and updated wiki and the example log of a first VM boot.
• Responded to bwh's comments on MR55
• Ran 'daily' BBB health check from my home network - results emailed to list. IP address of laptop was different to last health check and the VM settings for connecting to the Beaglebone required no manual intervention - so testing MR55.

• Got confirmation from Yoshi he will include the bullet points I sent in the CIP talk at ELC.
• Team meeting.

• Sent to Yoshi from Toshiba some bullet points to add to the slides of tomorrow's CIP talk at ELC.

• Reviewed the TSC minutes.
• Created and sent to CIP-dev the latest report
• CIP spotlight sent to LF marketing.
• CIP will sponsor Ben H. to attend to DebConf.

• Ran 'daily' BBB health check - results emailed to list.
• Updated build to use v4.4.120-cip20 and re-ran health check - results again to list.
• Created MR55 to handle #159.
• Updated MR 53 responding to bwh's comments.

• Codethink spotlight reviewed.

• Ran 'daily' BBB health check - results emailed to list.
• Tested clean VM against QEMU and BBB successfully, updated #149 week 10.
• Realised that the daily health check was not using the latest CIP tag updated script and re-ran successfully.
• Verified that the IP 9258 ipEdit.exe for locating the network switch's IP address runs successfully under wine[32].
• Testing fix for #159.

• Ran 'daily' BBB health check - results emailed to list.
• Set up testing system in Codethink office environment.
• Still getting timeouts in u-boot-interrupt.
• Provisioned a clean VM instance for testing #149

• Call with Jan and Yoshi to talk about the future of the CIP kernel maintenance.

• Ran 'daily' BBB health check - results emailed to list.
• Further advice to user setting up LAVA and kernelci.

• Ran 'daily' BBB health check - results emailed to list.
• Further testing of Renesas health check.
• Updated #166 with log of error in u-boot-interrupt timeout.

• Ran 'daily' BBB health check - results emailed to list.
• Gave advice to user having issues with ser2net.
• Setup jinja file for Renesas board so that the network switch powers the board on/off correctly. But still having health check failures. Updated #166 to give the correct reset command.

• Ran 'daily' BBB health check - results emailed to list.
• Added Tom's version of B@D with some Renesas changes to my pre-existing VM and did an initial check that it was talking to the Renesas board.
• Provisioned new VM from Tom's repos.
• Obtained network power switch and ethernet switch for testing.

• Approved 2 additions to the testing ML.
• Ran 'daily' BBB health check - results emailed to list. Some issues with timeouts before run was successful.
• Provisioned week 8 and edited #149 to include extra weeks.
• Looking at Renesas build and #167.
• Team Meeting.

• Codethink CIP team meeting: looking at what can it be done before ELC. Robert will focus on supporting Renesas board in B@D, as expected.

• Sent to the LF/CIP Board the budget request for Ben H. to attend to DebConf 2018 on behalf of CIP.

• Reminder about the testing ML sent to cip-dev
• Activated mail notifications from gitlab to cip-dev
  • Notified cip-dev mailing list admins.

• Finished report and sent it.
• Working on the budget proposal for debconf 2018
  • Notifications from gitlab will be sent to CIP-dev mailing list.
• Attended to the TSC bo-weekly call
  • Got approval to activate mail notifications from Gitlab.
  • Notified plans to make B@D work with the Renesas board, hopefully on time for ELC

• Reviewed bwh's comments on MR54 and MR53
• Ran successful health check with email to the list.
• Considering adding content - to at least give the kernel version to the emails.
• #165 /etc/linaro permissions has been fixed upstream so this has been closed.
• Edited the wiki to suggest the use of busybox-1.28.0 (rather than 1.26.2)

• Working on the budget request for Ben H. to attend to debconf 2018
• Draft of the report to be sent on Monday to cip-dev.

• Team meeting
• Discussion with bwh about what to do of interest for CIP at DebConf 2018.

• Discovered that connecting to LAVA on the newly created VM was giving an 'Internal server error' after trying various options - rebooting both the VM and the host (I was working from home via VPN so wanted to rule that out), I found in in /var/log/lava-server/django.log a python stack dump ending with DoesNotExist: Site matching query does not exist and realised that the change I made to the site name in preparation for the emails must have broken LAVA. The LAVA installation doesn't easily uninstall/re-install - too much extra config so I started another VM from scratch. I will review the wiki instructions on hostname carefully.
• Saw Zoran's comments on 99 - problems when behind a proxy - and have reopened that issue.
• I used busybox 1.28.0 rather than the 1.26.2 mentioned on the wiki to build initramfs and the eventual health check ran first time - I propose to update the wiki to reference that version.
• Installed mail server on VM and successfully sent health check success email with the latest kernel built using the latest kernelci.

• Created MR54 to address issue #165.
• Other responses to #173 to address ser2net issues.
• Looked at the AGL LAVA output.
• Started to create a VM to be used to send out health check emails to the list.

• Revised the MR (53) in line (I hope) with bwh's comments.
• Checked that issue #157 is still a problem.
• Tried to replicate #170 and has, so far, failed.
• Responded to #173 re. ser2net.
• Replied to cip-dev emails.

• Team meeting.
• Created MR 53 to address issues with the up to date kernelci.

• Conversation through cip-dev with bwh about his plans for Debconf.
• Issue list review in preparation for the CIP team meeting at Codehtink
• Sent a mail to open a discussion about the future plans on the kernel within CIP Membership, since I will not attend to ELC
• CIP Codethink Team meeting
• Played with IRC and mail notification on gitlab.
  • MAde a proposal to cip-dev to send notifications by mail in order to increase visibility of the work being done in this tool.

• Initial review of issues in preparation for team meeting.
• Updates Vagrantfile comment and closes #171

• Changed deadlines for milestones.
• Made some comments about current tickets to get some updates from rajm
• Updated the bi-weekly call report about CIP kernel and B@D
• Although we have a slot, Agustín cannot attend to Openexpo to introduce CIP. Asking Members about sending somebody local (Madrid, ES).
• TSC call
  • Renesas plans to send further patches to the CIP kernel before ELC. The idea for Codethink is to release a new kernel before ELC.
  • CIP would like to see LTS, Debian and CIP kernel based on the same kernel version.

• Discussion of directions for our CIP work.
• Opens internal discussion of #139 as to whether my branch is the correct approach.

• f2f meeting to discuss the remaining tasks as well as what to do next. The following two tasks seem obvious:
  • Clean up the current tasks, now that B@D is in maintenance mode.
  • Bring some automation to B@D provisioning to reduce the effort required to maintain it.

• bwh releases the new cip kernel 4.4.112-cip18

• Runs a successful provision and health check on the BBB for week 4 and updates #149

• Opened #171 to cover a typo (or was never changed when we moved from port 80 to 8080?) in a comment in the Vagrantfile.

• Participated at the TSC bi-weekly call.

• Addes some updates to the CIP TSC call minutes
• Participated at the TSC bi-weekly call.
  • Used zoom instead of gotomeeting.

• More discussion with Zoran Stojsavljevic re. his suggested changes.
• Runs a successful (first post my laptop Debian upgrade) health check on the BBB and updates #149

• Reviewed Zoran Stojsavljevic's suggested changes to importbox.sh.

• A new-kernelci branch has been pushed at least as a basis for fixing #139.

• I have a fix for #139. I can now provision with the latest kernelci. Hopefully I'll push it to a branch tomorrow.
• Replied to a B@D query on the lava-users email list.

• Trying various options for getting ser2net to work - the local connect is working.

• Updated minutes from TSC bi-weekly call.
• TSC Bi-weekly meeting

• Attempted build of a freshly provisioned B@D - am having issues with the ser2net connection (my laptop has been upgraded to Debian stretch since the last provision)

• Provided the link to CIP kernel policies in a mail to CIP answering a question. This page requires more promo.
• CIP TSC bi-weekly call moved to tomorrow due to bank holiday in Japan.

• Tested a fresh provision of B@D - which worked - and I updated the week 50 checkbox on #149

• Report weeks 48 to 50 done and sent to cip-dev mailing list.
• I willbe on vacation the coming two weeks, until 2018

• New CIP kernel version released by bwh
• Kernel maintenance wiki page content reviewed and improved by bwh

• Included the latest news about Codethink work in the TSC bi-weekly call minutes.
• Daniel seems to not receive the mails from AWS with credentials. I created a manual password and sent it to him. I did not followed up this correctly.
• For a reason I do not understand I could not connect to the meeting. I will reinstall the plugin

• Improved the current content in the Kernel maintenance wiki page
  • Included also the text written by bwh: Kernel patch review howto

• planning with bwh the CIP/Debian related events we will attend to:
  • ELC, OSSJ and/or DebConf are candidates.

• With input from bwh, I wrote the report from the last three weeks and sent it to cip-dev.

• Answered a couple of mails from Tiujen.

• Replied to Albert Aribaud's email about problems with provisioning an B@D instance from Vagrant with suggestions and a request for more information.

• Tiejun Chen wrote back. CC the list.
  • Link to Tiejun presentation at RT Summit.
• Interesting conversation in #kernelci about testing 3.2 Not sure if relevant for our case but the fact that there are conversations about testing older kernels is good in itself. Sent it to bwh
• Link to read that might be interesting for CIP inmutable infrastructure
• Got asked about Thursdays developers meeting.
  • They are not taking place any more.
• Went through the Kernel maintenance wiki page. We can improve it. Annie has been updating it. I would like to work on it a little this week.

• Further response to the Trung Huynh's email thread - would be helpful to see the actual yaml file that he's currently using.

• Tiejun Chen offered help. I wrote him back with some links and ideas.

• Built and briefly tested a new CIP kernel version on the Beaglebone and iWave boards, and in an x86 VM
• Tagged and released this as version 4.4.98-cip13

• Replied to Trung Huynh's email about the problems he is having getting a health check to run on the Renesas iwg20m.

• Finished reviewing the patches pending for 4.4.98, and pointed out a number of inappropriate or incomplete fixes
• Updated the kernel security tracker and identified fixes that should be backported to stable branches
• Sent necessary fixes and commit references to Greg Kroah-Hartman for 4.4 (and later branches)

• As recap, I sent a mail to the cip-dev mailing list explaining the history of the CIP Testing project.
• I sent a second e-mail summarising my view on what to do next in the Testing project.

• Had my weekly one-to-one meeting with Agustin, discussing various outstanding tasks and issues.
• Started reviewing the changes pending for 4.4.98.

• Opened ticket #170 to log kernelci network fragility encountered on Friday's talk

• Created a report for the TSC meeting minutes since the bi-weekly call will be later today.
• Removed due dates from several tickets
• Participated in the TSC call.
  • Agreed on sending a mail explaining my view on testing the CIP kernel in kernelci.org
• Added the talk Ben H. and I did at ELCE to the events wiki page in this wiki.
  • Notified to the mailing list.

I subscribed to the libc-alpha and y2038 mailing lists last week in order to keep track of and participate in the work on Y2038 safety. I have reviewed a few patches on the kernel side, and sent comments on the latest draft specification for glibc, but haven't seen any other activity on the glibc side.

I'm catching up on reviewing 4.4 stable changes for CIP, and covered 4.4.96 and 4.4.97 today.

• Preparation for and delivery of internal talk to Codethink on b@d.

• rajm will work maintaining the tool
• Went over the current pending tasks. Need to work further over the release tasks in order to close it.

• Tidied tickets to put project into maintenance mode. Added a little more info on the transition to gitlab #148
• Team meeting.
• Opened #169 to track Daniel's networking issue.
• Doing full test (more than just provision) of MR51 which looked good so I have closed the associated issue #168
• Ran health check successfully on BBB (cip11).

• Team meeting. Went over the Doing tasks and decide what to do with them.

• I've merged MR50 to clean up the device dictionary file, we may want PDU commands but they can be added later - and with the correct syntax!
• Adding python-selinux fixes the provisioning failure so I have created MR51.
• Ran health check successfully on BBB (cip11).
• Seeing libselinux-python support errors on a fresh provision, thought last week this was due to an attempt to migrate only to gitlab git repositories but it appears not! Investigating and #168 opened.

• Checked the latest messages on the lava-users mailing list. The same applies to other Open Source testing projects.
• Giving some thoughts about how to share tests and reports with upstream projects, specially kernelci.org. Wrote to Nori about it.

• Resized b@d stock vmdk to allow for more kernel sources
• Built cip4 kernel from renesas upstream with kernelci (taking config from cip-core yaml)

• Replied to Thanh's email to cip-dev - his test has the deploy section commented out.
• Created branch fix-linaro-permissions in git@gitlab.com:rajm/board-at-desk-single-dev.git to test #165
• Questioning why setting DATE_RANGE in /etc/linaro/kernelci-frontend.cfg doesn't take effect. Looks like permissions on /etc/linaro are too restrictive opened #165 to investigate this.
• Sent report on ELCE to codethink.
• Ran health check successfully on BBB (cip11).

• CIP Testing plan creation up to ELC 2017
• Report creation
  • Report sent after reviewed by the team
  • Included the new tickets created by tpollard #166 and #167

• Team meeting
• Hooked up BBB to remote PDU
• Tested current healthcheck with http curl requests for power commands (as with iw20gm)
• Started to look at provisioning the iw20gm kernel outside of kas/bitbake
• Building kernel with kernel ci, taking config from recipe/yaml, having to expand vmdk

• Has noticed that my kernelci builds are marked as 'building' in spite of the build having completed.
• Added documentation on the testing as to how to test an externally built kernel in B@D.
• Investigation of #164, it's the frontend file that requires amendment, in addition the number of displayed builds may require user configuration.
• Team meeting
• Updated the tickets mentioned in yesterday's entries.
• Closed #120 - which commented on the referencing of v0.9 tag on the wiki which is a no longer working version. The wiki was altered for the release to mention the v1.0 tag.
• Ran health check successfully on BBB (cip11).

• Evaluating the open tasks.
  • Added metadata and evaluate priority with rajm
• Based on the input from ELCE, working on the plan for the coming months.
• Team meeting
  • For the training session, in order to support Renesas board, we used CIP Core. Now we will go back to the original plan which is to build the kernel supporting Renesas board on ots own, in the same way we do with BBB, in order to test it, avoiding further dependencies.
  • Disussed issue #164. Added a comment with my idea about it.

• Attempted to build just using gitlab repos, the internal links for the ansible provisioning in kernelci-backend-config/ kernelci-frontend-config will also need changing. The provisioning fails with a “This module requires libselinux-python support” error.
• Tried altering the timeout for display of builds manually in kernelci-backend query.py that changes it but there seems to be some caching somewhere as another manual change doesn't take effect?
• Replied to Takuo Koguchi's email about problems with his version of the Beaglebone black.
• Closed #53 - the U-Boot prompt configuration.
• 1:1 with toscalix
• Consideration of future issues and their priorities.
• Ran health check successfully on BBB (cip11).

• Ill

• continue to interact with b@d & iw20gm with remote pdu
• b@D completes sample test from Daniel for iw20gm, removed/tweaked jinja config for specific scenario

• Issues #163 and #164 created relating to builds no longer appearing in kernelci if they are more than 5 days old - needs to be user configurable!
• cip11 health check runs correctly.
• Built cip11 in kernelci preparatory to using it for the BBB.
• Ran health check successfully on BBB (cip8).

• Thanked Arnd, Mark and Albert for their time at ELCE to talk about Y2038
• Requested to publish the pending CIP TSC meeting minutes on the wiki.
• Promoted the previous days Ben H. and mself talk about kernel maintenance. Positive feedback.
• Prepared some points of the CIP TSC agenda for today's call.
  • Feedback from ELCE.

• The previous days rajm and toscalix has been at ELCE 2017

• Received IP Power 9258 Remote PDU
• Connected to internal network, can power cycle 4 sockets via http requests/telnet
• Added http commands to template provided by Daniel for iw20gm test case

• Initial investigation of checking the host IP against that in the device dictionary.
• Ran successful health check on BBB.
• Removed various of the VMs from my laptop, that were provisioned during testing, to free up disk space.
• I've also added #161 to review the pause after ramdisk drops to shell.
• Added #160 - to start the kernelci webserver on booting the VM. This may also solve the issue we had with the builds not appearing and mean that we don't need our own version of build.py.
• Added #159
• Reviewed expenses for the ELCE trip

• Uploaded the slides from the elce talk with bwh to the LF tool and promoted the slides.

• Installed 16.04 Ubuntu on borrowed laptop and the shared ethernet connection worked immediately
• Due to delays getting shared connection to work the training session was cancelled - just as well in view of the hotel network blocking dhcp settings, we'd have had to instruct attendees to use their wifi hotspots.
• We had settings from nowster for setting up a shared connection on Debian but there were issues further down the line and the settings were overwritten when we did a fresh install.
• Team meeting at 16:30 to discuss training session situation.
• Work done on the abortive training session script.
• Still issues with a shared connection, have borrowed a laptop from ops for this to take with me. Currently provisioning a fresh install at the end of which I'll be able to test!

• Worked on the slides for the training session
  • Finished
• Sent additional information to Arnd about the Y2038 meeting.
  • Told Nori we have 4-5 free seats at the meeting. People from other LF groups can join.
• Worked on the CIP - AGL meeting organisation.
• Cancelled the training session.
  • Communicated to the CIP members and LF.

• Meeting to discuss blockers & actions to take asap
• Managed to config both windows & linux (ubuntu 16.04) to provision wifi over ethernet to BBB
• Documented the screen shots in draft slides, tested b@D worked correctly in this config
• Worked to get around uboot versioning problems, fix found by rajm

• Meeting with toscalix discussion the various blockers to the training session - ssh, u-boot on some boards and renesas issues.
• Ran daily health check on BBB successfully - was keen to do so after it being used elsewhere and for flashing an sd card.
• Created draft script for training session

• Battled with getting BBB & iw20gm working with windows provisioned box
• Used project-x in Jessie VM to produce uimage,uboot & ramdisk for iw20gm
• Acquired iw20gm board
• Flashed revC BBB from debian8 to 7, healthcheck now matches rajm's board
• Got b@d talking to iw20gm, missing remote power for lava to operate correctly

• Worked on getting a direct ssh connection via 192.168.7.2 to the BBB but it doesn't appear to work. Took the board home and checked that the issue is also a problem there - to rule out a company network cause.
• Created an sd card containing an image of my B@D working Beaglebone Black.
• Checked out tpollard's Renesas health check - Daniel's email confirms that not having a remote power switch is a blocker.
• There's a concern that different firmware versions on the BBB may result in the health check not working.
• Reviewed release announcement.
• Verified that my BBB works with tpollard's setup.
• Checked out acceptance criteria of #144
• Added links to the downloads to the download page, updated the link to the public GPG key.
• Reviewed and made modifications to the FAQ page.
• Further work on the feature page - add initial section, link to merge requests, mention codethink. Described block diagram. Added bug fixes section but many of the ones we fixed were reactive to our changes - for example because of the LAVA update.

• Reviewed the article that will be published by LF marketing
• Published and promoted the RT-4 linkedin messages.
• Added the kernel release announcement to the mail version of the B@D announcement
• Check the tasks.
• Reviewed the feature page. Added some bits.
• Release announcement reviewed and published.
  • Mail version reviewed and published. We are out!
• Attended to the lab in a box talk from Baylibre at AGL AMM.
  • There will be documentation about it next month.

• Assisted tpollard with setting up B@D.
• Revised the test cases wiki page so that it reflects the order that tests should now be done and hilights the changes necessary to perform tests on the locally built kernel (always now!)
• Further work on feature page.
• Work on #144

• Reviewed the feature page. More content needed.
• Got the link to the release announcement so finished the twitter social media messages and added the link in several other places.
• Created the Linkedin messages
  • Published the linkedin messages in the marketing page
  • Notified marketing LF

• Received mail about adding iwg20m to b@d
• Applied provided patches to b@d, including lava & vagrant changes to support it
• Current 'project-x' deby system is created with bitbake, using the meta-debian poky reference system
• Problematic as based on old version of yocto (2.0 ~2015), does not 'support' debian9/ubuntu16.04 has host system (already encountered ncurses problem, fixed upstream but not backported to recipe)
• Building require cip kernel & core-minimal system inside 14.04vm, will then provision into b@d box for testing
• Received BBB order along with other items to be provisioned & tested for the hands-on-session

• More work on feature page.
• Spotted duplication in paragraphs 3 & 4 of the test cases page.
• Attended CIP sync meeting.
• I've changed the configuration page to use /vagrant/tests/bbb_debian_local.yaml rather than bbb_debian_ramdisk_test.yaml as that should be the basis of the eventual working health check, rather than trying to find a linaro kernel which isn't there. A non working config to use a locally built kernel is good.
• Reviewed feature page.
• Posted logs of provisioning and health checks (QEMU and BBB) and linked to them in technical documentation.
• In the future I'd like to remove some of the many numbered references to the B@D version scattered though the technical documentation!
• Reviewed and edited technical documentation.
• Worked with toscalix on revision of block diagram.
• Ticked acceptance criteria in #143
• Ran successful BBB health check and mentioned on public IRC channel - I'll get back to the emailed version soon!

• Published the new features and download pages. Still both of them need work.
• Went through the block diagram with rajm
  • Updated and uploaded in the feature page
• Closed the deployment ticket
• Improved the feature page
• Sent a reminder to Annie to add tpollard as editor in the public wiki
• Created a task for the future to refurnish the landing page.
• TSC bi-weekly call
• Sync up meeting wit the Codethink team
• Mail version of the release announcement (draft) created.

• Updated known issues removing issues which save been solved in the coming release.
• Updated #143 with links to the downloads.
• Downloaded the v1.0 files and checked sha256 and gpg signing.
• Tested the box after downloading it from S3
• Started #143 Uploaded the box and and artifacts to S3.
• Added a list of files to be uploaded to #142
• Created sha256 hashes and gpg signatures for the box and the sources
• Created the metadata -tar.gz files containing the sources
• Tested exported box under Linux and Windows10
• Exported the box
• The Windows hosted install BBB health check now passes.

• rajm declared Gold Master. I communicated it: #142
• Worked on the slides for the talk with bwh
• Created and sent to cip-dev mailing list the bi-weekly report. On monday I will update the TSC

• The Windows install is provisioned and currently building the CIP kernel.
• The Debian hosted install is now provisioned and tested.
• Commenced provisioning and testing of VMs under Debian and Windows 10
• Tagged the repositories #142
• Added licence information to the wiki for contributors
• Closed #140 licenses
• Team meeting discussing Gold Master
• Synced the repositories
• Added LICENSE.spdx to the B@D repos

• Team meeting to talk about the Gold Master declaration
  • We went over the tasks involved in this phase of the release process.
  • Fixed some links of the GM declaration task
• Management page done. MArketing page also done according to #144
• Purchase order for the material required for the B@D 101 training session sent.
• Filled the info about the demo that will be used by the Linux Foundation to promote the CIP demos.

• I am now doing a fresh provision from new master, hopefully this will form the basis of gold master.
• Both these merge requests have now been approved and merged (after a few changes).
• Created 48 for the update to debian stretch.
• Created merge request 49 for the licensing update.
• Created #152 for the stretch update.
• I've created a branch for the stretch update. That provisions ok for me under linux and health checks on QEMU and BBB run. Now checking with Windows 10.

• CTtpollard on boarding process. Welcome Tom.
  • Tom has now access to gitlab
  • Requested for him edit rights on the CIP public wiki.
• Sync up meeting with robert
• Tasks update
• tpollard added as approver in master repo
• CIP Developers Meeting at ELCE announced.
• Sync up meeting with Ben H (bwh) about the common talk we will do at ELCE.

• After consulting with colleagues we're using jessie-backports and jessie-backports-sloppy as well as stretch for the cross compilers and have removed testing. Currently trying a fresh provision if that works will then embark on extra testing!
• Attempted an install from snapshot.debian.org but is, so far, unable to get apt-get to see the correct version of LAVA
• Created a branch update-licences for the licence updates.

• Worked on the marketing content page
• Communication with LF marketing about the release process.

• Worked with Agustin - and a meeting - to determine the 3 issues which will need to be addressed after the release - see toscalix's comments below.
• Installed 2017-10 on Linux and that shows the same issue as the Windows 10 install - making it more likely that there won't be another issue to solve once we get 2017-7 installed on Windows 10.
• The Windows 10 install revealed that the lava version installed by default in B@D is the latest which is now 2017-10 which is not the one we tested against (which was 2017-7). On further investigation that version is now unavailable in the testing/backports repository and work is being carried out to determine how to install 2017-7.
• Updated version on the new block diagram.
• Updated the draft release announcement.
• Testing the current git master on Windows 10, provisions ok and the initramfs kernel build and kernelci i/f works, currently issues with USB and ser2net.
• Successful run of BBB health check with result going to email list.

• Started to work on the release announcement #146
  • Finished and reviewed by rajm. Sent it to cip-members for feedback.
• Meeting with Robert to evaluatre the current state of technical issues.
  • I created three tickets of tasks that will not be performed in this release cycle but the next one.
  • There are two technical issues to solve: point to the right LAVA version on Debian, since it has been updated and add the license header to every file developed/modified by Codethink when missing and the spdx file..
• Created the block diagram draft. Robert updated the versions. #144
• Created a ticket to track the actions related with the developers meeting at ELCE #151
• Worked on the new CIP Testing release page.
• Moved the content of the feature page and the download page from the previous release to be able to modify them for the new coming release

• Investigated improving the licence state of the forthcoming v1.0 release.
• MR 47 was approved and merged (by Lachlan), I've now done a fresh provision, configure, compile and BBB health check successfully.
• Successful run of BBB health check with result going to email list.

• Finished the release plan
  • #141 Release B@D v1.0. This is the task that track the whole process
  • #142 B@D v1.0 release: Gold Master declaration.
  • #143 B@D v1.0 release: deployment.
  • #144 B@D v1.0 release: documentation
  • #146 B@D v1.0 release: marketing material preparation
  • #147 B@D v1.0 release: publishing
• Meetig with Robert to analyse the improvements to be made on this release on the license compliance front.

• Amended wiki to cover the changes for LAVA 2017-7 and the necessary reboot of the VM, added point on this to known issues.
• Opened #145 to document efforts to drop back to a more stable version of kernelci for the release and the ELC-E training session. Provisioning with a checkout of older versions is working well and a MR has been created.
• Weekly meeting
• The provision of kernelci works ok by adding the install of nginx explicitly to the provisioning script. A manual reboot of the VM is still required part way through the provisioning, so we need to either work our way around this or run the provisioning in two phases.
• Emails sent to cip-dev to keep the kernel-ci provisioning issue #139 still in focus.
• Successful run of BBB health check with result going to email list.
• Returned from vacation!

• Analysis of the release schedule.
• Tech weekly meeting
  • Sync up with Daniel S.
  • Renesas Board with LAVA will require a relay.
  • General agreement on the release schedule.
• Created the main task to track the release schedule.
  • Working on creating all the tasks to track the complete release process.
• Requested Ben H. to prioritise the cip kernel release including the Renesas board support so Daniel S. and the CIP testing project arrive on time to ELCE to use the board.
• Suggested Daniel W. to use gitlab or what Ben H. is doing.
• Finished documentation task from the release process.

• On vacation

• Preparation of the ELCE activities
  • Added CIP devs meting content in the ELCE activities wiki page.
  • Several short actions
• Analysis of the release schedule.

• On vacation

• Pinged Members so they join the CIP activities at ELCE.
• Added the first three confirmed people to the B@D 101 training session.

• On vacation

• Added content to the TSC bi-weekly call agenda
• Working on the mail report weeks 38 and 39
  • Report sent to ip-dev mailing list.
• Added Daniel S. to the list of CIP S3 admins.
• Attended to the TSC bi-weekly meeting.
• Proposed an action plan for the CIP developers meeting to Members.
• Daniel needs to know when will he have available LAVA 2017.07 so he integrates it in Project-X

• On vacation

• Room for the CIP workshop confirmed: Athens. Communicated through the cip-dev ML
• Created a task to review the licenses, based on the guide done by the Commons Conservacy and now donated to the OpenChain project.

• On vacation

• Completed the information about the B@D 101 training session on the CIP workshop wiki page.
  • Sent the call for registration to the cip-dev and cip-members mailing list
  • Asked Annie about the room name where the workshop will take place.
• Pending a meeting to clarify the workshop set up to the Linux Foundation so the room is prepared as well as the material.
• Requested to CIP Members potential topics for the CIP Kernel Maintenance Q&A Session through a mail to the cip-dev mailing list. I will also ask in the open mailing list in a couple of days.
• Managing the Y2038 meeting at ELCE
• Managing the CIP developers meeting and CIP kernel maintenance meeting. Sent info to Daniel Wagner from Siemens so he attends.

• On vacation

• Provided some support through mailing lists.

• On vacation

• On vacation

• Merged the initramfs branch and closed #56, #111 and #136.
• Pushed fix-new-kernelci as an approach to solving the kernelci issue, still hangs at the listening on port 8888 in install_backend.sh and needs a manual vm restart. But once that's done the rest of the kernelci provisioning works.
• I will be on holiday from this weekend for just over a week.
• Reviewed MR for initramfs and cleaned up a comment in the local test script.
• Pushed new initramfs changes to my add-initramfs branch.
• Ran 2 successful BBB health checks one with the linaro initramfs one with the one built locally yesterday. The local one runs around 35 seconds faster.

• Altered PS1 within the initramfs as dropping to shell and that initramfs allows the test to run.
• Pushed updates to the initramfs script as suggested by Ben, also hard coding the ALERT message in my add-initramfs branch.
• Successful run of BBB health check with result going to email list.
• ALERT message inserted, it is recognised by LAVA but I then get another timeout. Checking what the init in the linaro version does as it doesn't produce an ALERT but Ben's issue #56 is probably pertinent.

• Discussion with Ben on initramfs, will make sure that out version prints out the ALERT message that LAVA is looking for.
• Merge request !44 approved and merged, the corresponding issue #99 has also been closed.
• Still having problems with a fresh provision, nothing listening on port 8888 until I reboot the VM and issues with the nginx install completion.
• Successful run of BBB health check with result going to email list.
• Though the backend provision hangs when the script tries to check for a listener on port 8888 - it isn't there.
• Reopened #99 as MR!44 is associated with it. Lachlan approved the MR and I have merged and closed the issue.
• Looks as if a fix to the kernelci backend population problems is another case, like in the front end, of the first ansible run failing and a repeat run works.

• Lachlan has approved MR 43 so I've merged it and closed #84 and #115 - this is the LAVA2017-7 update.
• I tried creating a new instance and am having problems do to a recent change and the introduction of storage_certname which then requires other consequential changes.
• 1-1 with Agustin.
• Successful run of BBB health check with result going to email list.

• Created fix-lava-source with a view to a MR for #133
• I've closed #129 the user needs to set up a local build.
• Tried a wifi, with BBB connected directly to laptop - still failures, DHCP issue needs resolution. The solution is not IMHO to run a DHCP server on the laptop as that would involve - at ELC-E - all the participants needing that setting up.
• Successful run of BBB health check with result going to email list.

• Confirmed schedule for ELCE:
  • Kernel maintenance meeting
  • y2038 meeting. arnd confirmed his presence.
  • B@D 101 training session
  • Kernel maintenance Q&A
• Report weeks 36 and 37 done and sent to cip-dev mailing list.
  • @rajm, does the project journal work for this particular usage?
• TSC bi-weekly call.
  • I have a couple of extra tasks on my plate now.
  • Approval for the expenses for the training session.
  • Green light to advertise the workshop activities. Call for participation.

• Updated #120 - as it will be fixed by the new release.
• Still no success with a local initramfs - we need assistance here if this is going to proceed.
• Successful run of BBB health check with result going to email list.

• Removed requirement for a new wiki page for report format from #114 - at this point the report is going to be simple. Also revisited the release procedure issue #75
• Tried more options to avoid errors in the init in initramfs but this is unlikely to be the core issue #136.
• #help discussion has made the issue clearer but not given a resolution.
• Successful run of BBB health check with result going to email list.
• Question placed in codethink's #help re initramfs issue.

• Successful run of BBB health check with result going to email list
• Asked in #linaro-lava for any additional insight on the notifications without any comeback.
• Tried various options mainly in respect of init for the initramfs issue without getting any to work, tried using the init from the linaro one but that seems tied to the file system in that initramfs.cpio.gz. I'll ask in codethink's #help tomorrow.

• Tried notification callbacks with POST on a lava-tool test see notifications for documentation. Not sure that it gives the information promised - log files? - but will investigate further.
• Ran lava-tool test on BBB successfully (host on the home wifi) - not sure why it failed on 4th Sept! But this appears to have resolved.
• Gave more suggestions to Daniel on lava-users list.

• Team meeting (face to face)
• I've closed #127 the 'failure to provision due to an error in kernelci-backend' as a fresh install works here.
• Now running tests on laptop connected only via wifi successfully - in contradiction to tests on 2017/09/06 I don't think anything has changed?
• Created MR 45 for issue #138.
• Emailed lava-users as a result of seeing Daniel Sangorrin's wish to move to LAVA 2017-7.

• I've removed everything but the connect_command and extends from the device dictionary and the check still runs, so I've added an issue #138
• Runs successful healthcheck which goes to list after 3 failures
• I've also noted that the device dictionary only needs the extends and the connection_command - the other commands were invalid and therefore weren't used!

• On holiday!

• Tried various suggestions on the BBB test from Neil Williams but am still not getting a successful test.
• 1-1 meeting.
• Discussion with Jan-Simon about notifications and updated issues with the new #137
• Sent description of initramfs issue #136 to lava-users and response from Neil Williams.
• Attempted a health check across wifi - added wifi bbb device with data dictionary specifying the correct ip address - this works if bridging to eth0 but not to wifi?
• Added point to #114 so that the wiki gets an update once the 2017 upgrade is complete describing the report format.

• Team meeting
• Ran successful BBB health check (LAVA 2017).
• Updated #136 with comparison of working/non working initramfs output.
• Still looking at initramfs

• Codethink CIP team meeting to sync up
  • Updated the team about the TSC bi-weekly call.

• Ran BBB health check from home with laptop on wifi - it failed I need to diagnose this.
• Ran successful BBB health check once in Codethink offices
• Replied to Daniel Sangorrin'e email about ser2net.
• Will update various merge requests and get them moving!
• Checked out the week 34/35 report.
• Confirmed that a health check also fails at Codethink when the laptop is on wifi.
• Replaced MR 34 with MR 44

• TSC bi-weely call
  • Updated the minutes
  • Provided reports about CIP testing.
  • Progress in the meetings organizations at ELCE.
• Created and sent the week 34 and 35 report

• Runs BBB health check with 2017-7 - succeeds - on second attempt and is emailed to list.
• Created #136 to cover the initramfs issue, locally built ones that worked with 2016-12 fail with 2017-7.
• Updated #115 and #84 to 'Doing' as they're part of #114.

• ELCE prepaprations. Y2038 and maintainers meeting

• Tech weekly meeting - discussed the changes made to get the BBB health check to work with LAVA 2017
• Updated VM (with 2017) so that emails can be sent to the list - amended the health check so that this happens.
• Looking at the current requirement within the health check for ethernet connectivity - if this were not necessary then the ELC-E workshop setup would be easier.
• Added Merge request 43 for the update to 2017
• Tried various options for getting a locally built initramfs to HC correctly without success (tried 1.27.2 rather than 1.26.2 and sleeping in init to slow it down).
• The LAVA Help suggests that DHCP is necessary which is at least an initial problem to getting a BBB without ethernet to HC.

• Who is available on Monday Oct 23rd for the Y2038 meeting?
• Tech weekly meeting
  • Provided an overview of the situation now that AGL is investing in a lab in a box concept.
  • I will attend to AGL AMM so I will talk there with the developers to understand what they are doing and how we can collaborate.
  • I need to define the coming release schedule.
  • Considerations about the technical set up for the B@D 101 training session
  • Content for the kernel maintenance activity?

• Ran daily health check on BBB and email sent to testing list.
• Tried 2017 with the health check off the Linaro site also failed but slightly differently.
• Adjusted the health check slightly and have it completing ok under 2017, checked in the check and pushed to the development branch. Updated #114 and will look to setting up email tomorrow so they get reported to the list.
• I'm still having problems with a locally built initramfs with 2017 and for the moment am using the one off the linaro website (but put on the local webserver just for comparison).

• Trying to organise several CIP meetings at ELCE: kernel maintenance and Y2038

• Worked with Agustin on the AGL CIAT slides and meeting (see below).
• Submitted query about a broken link in LAVA web page and was pointed to a configuration - opened #133
• Closed #99 and #128 having merged MR !42
• Still exploring the problems with the LAVA 2017-7 upgrade

• Working on the slides for the AGL CIAT meeting
  • Slides added to the CIP and AGL wikies.
• Meeting took place. Robert and I introduced B@D. Bad sound quality most of the meeting.
  • Reported about it to cip-dev mailing list
  • Sent a mail to Kevin Hilman to meet him at AGL AMM.
• team meeting: sync up with rajm.
• Following AGL CIAT tickets related with “lab in a box”.

• UK public holiday

• Organising a meeting with Arnd Bergmann to talk about Y2038 at ELCE. We have a room for the meeting.

• Preparing project summary for next week's call.
• More investigation of LAVA 2017-7 upgrade problems.

• Solved the escalations for the journal. Added them to the ground rules.
• Organising the B@D training session. Network cables question.

• Moved management wiki page.
• Created journal ground rules.
• Moved journal wiki page.
• Created journal wiki page

Project journal ground rules:

• In this case the entries will be structured first by month, then by date and finally by contributor.
• You decide what kind of information you should publish.
• Assuming that it is public, add what you think is :
  • Relevant to you.
  • Relevant to your peers.
  • Relevant to those you interact with like, managers, other teams, Members, etc.
• The latest entries should be on top (ascending order).
• Be concise.
• Use links to tasks, commits, web pages, etc. as much as you can. This is not about duplicating the information but about providing context.
• Read the journal every day (ideally). Does it reflect the most relevant work you have done today?
• As guidance, include an entry every couple of hours of work and every time you accomplished something or a relevant event has taking place.
• Assume that your colleagues read the journal regularly. Add information of potential interest for them but remember that the main focus of the journal is the answer to the question: what am I doing? Write for yourself first.
• Agree with your colleagues on the tags to be used to provide further context to entries. Examples:
  • Escalations:

    • Blue to solved or stalled issues

    • Amber for topics that require attention

    • Red for critical issues

  • User ID to call the attention of a colleague.
  • #milestone to structure the information based on delivery timeline.
• Activity reports should be extracted from the journal so, ideally, no need to ping colleagues to create a report should be required. This is a sign of the correct usage of the journal.
• Standup meetings should not be any more about what I did (reporting) but about discussions. The time that a distributed team gets together is precious, do not waste it talking about something you can read ahead of the meeting.
• Do not add anything that you would not like others to know. Use common sense.
  • The journal is not designed to substitute 1:1's, private reporting nor conversations.

— Agustin Benito Bethencourt 2017/08/24