Linux Foundation Wiki

project collaboration site

User Tools

Site Tools


civilinfrastructureplatform:journal

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
civilinfrastructureplatform:journal [2018/07/13 08:40]
rajmarshall
civilinfrastructureplatform:journal [2018/09/21 14:33] (current)
rajmarshall
Line 1: Line 1:
 ====== CIP journal 2018 ====== ====== CIP journal 2018 ======
  
-This is the journal followed by CIP developers to keep track of the work being done on behalf of CIP.It starts in 2018Q2.+This is the journal followed by CIP developers to keep track of the work being done on behalf of CIP. It starts in 2018Q2. 
 + 
 +===== September ===== 
 + 
 +==== Friday 2018/09/21 ==== 
 + 
 +=== rajm === 
 + 
 +   * Sent email listing progress in weeks 30-38 to the cip-dev email list. 
 +   * New section on [[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​ciptestingreferencetestcases#​test-7use-lavacli-utility|lavacli]] added to wiki. 
 +   * lava-tool is deprecated, so I've manually installed lavacli and run a test successfully. 
 +   * I've added a note to the LAVA notification section on the wiki that IRC pings on Freenode are not working at the moment due to their SPAM avoidance methods. 
 +   * Ran a BBB health check successfully,​ still waiting for the email to appear on the list. 
 + 
 + 
 +==== Thursday 2018/09/20 ==== 
 + 
 +=== rajm === 
 + 
 +   * Ran a fresh provision for week 38 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]]. 
 +   * Met in the team meeting. 
 +   * Pushed a new version of docker-provision.sh to [[https://​gitlab.com/​cip-project/​cip-testing/​kernelci-docker|the CIP kernelci-docker]] where the initramfs build works - it uses init-example from b@d. 
 +   * Attended the cip-dev IRC meeting. 
 +   * Ran a BBB health check successfully with an email to the list. 
 + 
 + 
 +=== toscalix === 
 + 
 +   * During the IRC cip-dev meeting I checked the state of the TSC minutes being published since there were a couple of actions points to escalate topics there. Instead of any of us providing outcome of the TSC discussions,​ we should just simply refer to the minutes. 
 +     * There are no minutes published sinec January 2018 
 +     * I sent a mail to cip-dev to have them published.  
 + 
 +==== Wednesday 2018/09/19 ==== 
 + 
 +=== rajm === 
 + 
 +   * docker-provision.sh builds initramfs and copies it to the kernelci docker in the correct location (or at least a http accessible location) so I've ticked the relevant box on [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​192]]. 
 +   * I've added a docker-provision.sh to [[https://​gitlab.com/​cip-project/​cip-testing/​kernelci-docker|the CIP kernelci-docker]] and will add init-example shortly (or maybe it should take that from B@D?). 
 +   * The 3rd party docker repos mirrorings e.g [[https://​gitlab.com/​cip-project/​3rd-party/​kernelci-docker-mirror|kernelci]] are still failing. 
 +   * Ran a (lava-tool) test of BBB using a wifi connect for Vagrant on the host  to attempt to replicate [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​200|#​200]] but it worked ok. 
 +   * Ran a BBB health check successfully with an email to the list. 
 + 
 +==== Monday 2018/09/17 ==== 
 + 
 +=== toscalix === 
 + 
 +   * Participated at the TSC meeting 
 +      * Provided a status report about kernel maintenance final tasks and handover. 
 + 
 +=== SZ Lin (林上智) === 
 +  * Attended TSC meeting. 
 +      * Reported status of kernel IRC meeting 
 + 
 +==== Friday 2018/09/14 ==== 
 + 
 +=== rajm === 
 + 
 +  * Response to [[https://​github.com/​kernelci/​lava-docker/​issues/​45|issue 45]] from khilman suggesting either a U-Boot upgrade or a lab/​networking issue.  
 +  * 1:1 with toscalix.. 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 +==== Thursday 2018/09/13 ==== 
 + 
 +=== rajm === 
 + 
 +   * Demo of the existing state of containerisation with toscalix. 
 +   * Added tick box to [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​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 [[https://​github.com/​kernelci/​lava-docker/​issues/​45|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. 
 + 
 +==== Wednesday 2018/09/12 ==== 
 + 
 +=== rajm === 
 + 
 +  * I need to ensure that the correct scripts are passed to the correct container in lava-docker. connectBBB.sh needs to be copied to lab-slave-0. Trying lava-docker with b@d as a provider of builds still times out when trying to talk to the tftp server. 
 +  * 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 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​200|#​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. 
 + 
 + 
 +==== Friday 2018/09/07 ==== 
 + 
 +=== rajm === 
 + 
 +  * Added some container todo points to tickboxes in [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​192]]. 
 +  * 1:1 with toscalix. 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 +=== toscalix === 
 + 
 +  * Created the kernelci-docker and lava-docker repos. 
 +  * Created the kernelci-docker-mirror and lava-docker-mirror repos in 3rd-party subgroup. 
 + 
 + 
 +==== Thursday 2018/09/06 ==== 
 + 
 +=== rajm === 
 + 
 +  * Added another 2 points from [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|192]] to yesterday'​s list. 
 +  * Added PR [[https://​github.com/​lucj/​kernelci-docker/​pull/​24|24]] for kernelci-docker. 
 +  * Attended the cip-dev IRC meeting. 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 + 
 +==== Wednesday 2018/09/05 ==== 
 + 
 +=== rajm === 
 + 
 +  * 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 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​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. 
 + 
 +==== Monday 2018/09/03 ==== 
 + 
 +=== SZ Lin (林上智) === 
 +  * Attended TSC meeting. 
 +    * Listed candidates for CIP kernel maintenance. 
 + 
 +===== August ===== 
 + 
 +==== Friday 2018/08/31 ==== 
 + 
 +=== rajm === 
 + 
 +   * 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. 
 + 
 +==== Thursday 2018/08/30 ==== 
 + 
 +=== rajm === 
 + 
 +   * 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 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​197|#​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. 
 + 
 +=== toscalix === 
 + 
 +   * 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? 
 +      * [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​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. 
 + 
 +=== SZ Lin (林上智) === 
 + 
 +  * Attended cip-dev IRC meeting. 
 +      * Sent the overlayfs backport patches 
 + 
 + 
 + 
 +==== Thursday 2018/08/23 ==== 
 + 
 +=== toscalix === 
 + 
 +   * 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.  
 + 
 +=== SZ Lin (林上智) === 
 + 
 +  * Attended cip-dev IRC meeting. 
 + 
 +==== Wednesday 2018/08/22 ==== 
 + 
 +=== rajm === 
 + 
 +   * Ran a fresh provision for week 34 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​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. 
 + 
 +==== Monday 2018/08/20 ==== 
 + 
 +   * TSC meeting 
 +      * The proposal I did to manage the maintainers permissions on Gitlab.com repos was approved. Now we need to implement it. 
 + 
 +=== SZ Lin (林上智) === 
 + 
 +  * Attended cip-dev IRC meeting. 
 + 
 +==== Friday 2018/08/17 ==== 
 + 
 +=== rajm === 
 + 
 +  * Responded to mungaip'​s latest state in [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​195|#​195]] - his problems appear to be proxy related, I'll check up on various proxy related issues ticketed previously (that'​s [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​99|#​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. 
 + 
 +==== Thursday 2018/08/16 ==== 
 + 
 +=== rajm === 
 + 
 +  * 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 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​195|#​195]] and [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​196|#​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. 
 + 
 +=== SZ Lin (林上智) === 
 + 
 +  * Attended cip-dev IRC meeting. 
 + 
 +==== Wednesday 2018/08/15 ==== 
 + 
 +=== rajm === 
 + 
 +  * 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. 
 + 
 +=== toscalix === 
 + 
 +   * 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. 
 + 
 + 
 +==== Friday 2018/08/10 ==== 
 + 
 +=== rajm === 
 + 
 +  * 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 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​192]] 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 + 
 +==== Thursday 2018/08/09 ==== 
 + 
 +=== rajm === 
 + 
 +  * Updated [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​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. 
 + 
 + 
 + 
 +=== toscalix === 
 + 
 +   * Chair of the weekly IRC meeting 
 +      * Sent the [[https://​lists.cip-project.org/​pipermail/​cip-dev/​2018-August/​001470.html|minutes]] to cip-dev mailing list. 
 +   * Sent a proposal to cip-dev to [[https://​lists.cip-project.org/​pipermail/​cip-dev/​2018-August/​001471.html|manage the user roles]] in gitlab.com 
 + 
 + 
 + 
 +==== Wednesday 2018/08/08 ==== 
 + 
 +=== rajm === 
 + 
 +  * 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 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]] 
 +  * Ran a BBB health check successfully with an email to the list. 
 + 
 +=== toscalix === 
 + 
 +   * 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. 
 + 
 + 
 +==== Friday 2018/08/03 ==== 
 + 
 +=== rajm === 
 + 
 +  * 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. 
 + 
 + 
 +==== Thursday 2018/08/02 ==== 
 + 
 +=== rajm === 
 + 
 +  * 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. 
 + 
 + 
 +==== Wednesday 2018/08/01 ==== 
 + 
 +=== rajm === 
 + 
 +  * 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. 
  
 ===== July ===== ===== July =====
 +
 +==== Friday 2018/07/27 ====
 +
 +=== rajm ===
 +
 +  * I have successfully built lava-docker [[http://​github.com/​kernelci/​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.
 +
 +
 +==== Thursday 2018/07/26 ====
 +
 +=== rajm ===
 +
 +  * Submitted [[https://​github.com/​kernelci/​kernelci-docker/​issues/​12|#​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 [[https://​github.com/​kernelci/​kernelci-docker/​issues/​11|#​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.
 +
 +=== toscalix ===
 +
 +   * 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.
 +
 +==== Wednesday 2018/07/25 ====
 +
 +=== rajm ===
 +
 +  * 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 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​178|#​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 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]] - no longer need to add a local test section with last week's merge.
 +  * Issue [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​193|#​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.
 +
 +=== toscalix ===
 +
 +   * 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.
 +
 +
 +==== Monday 2018/07/23 ====
 +
 +=== toscalix ===
 +
 +   * 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.  ​
 +
 +==== Friday 2018/07/20 ====
 +
 +=== rajm ===
 +
 +  * Looking at [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​192|#​192]],​ managed to get start.sh in the original [[ http://​github.com/​kernelci/​kernelci-docker|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 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​190|#​190]] and updated with a question to the OP.
 +  * Ran a BBB health check successfully with an email to the list.
 +
 +
 +==== Thursday 2018/07/19 ====
 +
 +=== rajm ===
 +
 +  * I've updated Virtualbox to 5.2.16 - looking at [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​193|#​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.
 +
 +
 +==== Wednesday 2018/07/18 ====
 +
 +=== rajm ===
 +
 +  * Updated Vagrant to 2.1.2 to investigate [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​193|#​193]] I don't see the error, will update to Virtual box 5.2.16 and see if that produces the error.
 +  * Merged ​ [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​61|MR 61]] - making the final output of create_test.sh more appropriate to the user's situation and closing [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​178|#​178]].
 +  * Merged [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​62|MR 60]] - using a fixed version of LAVA so we can check any new version before incorporating it - and closed the associated issue [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​191|#​185]].
 +  * Merged [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​62|MR 62]] - the moving to a local test - and closed the associated issue [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​191|#​191]].
 +  * Ran a BBB health check successfully with an email to the list.
 +
 +
  
 ==== Friday 2018/07/13 ==== ==== Friday 2018/07/13 ====
 +
 +=== rajm ===
 +
  
    * Created [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​62|MR 62]] to use a local test for the BBB health check to make the test more self-sufficient.    * Created [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​62|MR 62]] to use a local test for the BBB health check to make the test more self-sufficient.
Line 11: Line 401:
    * Ran a BBB health check successfully with an email to the list.    * Ran a BBB health check successfully with an email to the list.
  
-=== rajm === 
  
 ==== Thursday 2018/07/12 ==== ==== Thursday 2018/07/12 ====
Line 26: Line 415:
 === rajm === === rajm ===
  
-   * A fresh provision for week 26 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​149]] with a local test secion. 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? ​+   * A fresh provision for week 28 [[https://​gitlab.com/​cip-project/​cip-testing/​testing/​issues/​149|#​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.    * Ran a BBB health check successfully with an email to the list.
  
civilinfrastructureplatform/journal.1531471243.txt.gz · Last modified: 2018/07/13 08:40 by rajmarshall