Hi, during the past CIP Members meeting call, Monday 23rd January, Members agreed on bringing to the attention of CIP contributors and friends the Y2038 topic. What is Y2038 refers to? "Y2038

Hi Don, Great. I agree. There needs to be some strict rules for applying patches. Okay, understood. What about introducing a default configuration that clones for upstream but it could be

Hi Daniel, I like the change to the patch and I'll incorporate it tonight. We are already mirroring the KernelCI Backend and Frontend and I had almost the exact same thought this weekend that we

Hi Don, Over the weekend I had an idea to improve it even more: GIT_SRC="https://github.com/kernelci/kernelci-backend-config.git" if [ -d /vagrant/kernelci-backend-config ]; then

Hi, this is the report from the activities that Codethink is driving on and or involved. This week is not that we worked more but that we completed more tasks. ++ Meetings * Members meeting on

Good point. I lost myself in the depth of cloudy thoughts.

Am 19/01/2017 um 15:57 schrieb Daniel Wagner: I've had to read the last sentence for a couple of times before I could make sense of it. Perhaps something along the lines of 'The integration scripts

In order to develop or debug the setup we should allow to a developer to use local copy of the sources. This is done by cloning all the remote repos to the project main folder. This folder is shared

Hi Everyone, I'm reporting on 2 issues today: 1. Re: kernelci setup fails 2. Re: Kernel-CI Frontend broken links to build.log et al. ----- #1 I have fixed the issue of the Kernel-CI Virtual Machine

Hi, until then... We have discussed what to do. There are several options: 1 Make Python 3.5.2 work on trusty. 2 Move on to Ubuntu 16.04 3 Move to an in-between version. 4 Try to move it into Debian

I gave it a try, no luck though: ==> default: TASK [install-deps : Install MongoDB] ****************************************** ==> default: failed: [kernel-ci-backend]

Hi Don, I'll create a gitlab account soon, so that I can collaborate via the ticket system. Thanks. Daniel

Hi Daniel, I have the same problem and worked on it yesterday from several angles. My notes are logged in Issue #12 in the GitLab repo. The link

Hi Agustin, Indeed the second bug report in the ticket is the problem I see too. http://packages.ubuntu.com/search?keywords=python3-setproctitle xenial (16.04LTS) (python): A setproctitle

Hi Daniel maybe this helps? https://gitlab.com/cip-project/testing/issues/12 If this is your case, Don is on it. He talked to one of the kernelci developers, Milo Casagrande about it. -- Agustin

Hi, running 'vagrant up' from a clean setup consistently fails with this: ==> default: TASK [setup] ******************************************************************* ==> default: ok:

Hi, since there is no further feedback, I assume you will merge the patches, isn't is? -- Agustin Benito Bethencourt Principal Consultant - FOSS at Codethink agustin.benito@...

Hi, since there is no further feedback, I assume you me merge the patches, isn't is? Hopefully in a couple or three more weeks we can start testing it with kernelci tooling. -- Agustin Benito

[...] Thanks. My backports are identical aside from the placement of some changes in Kconfig files, which shouldn't make a functional difference. Ben. -- Ben Hutchings Software Developer,

Apologies, the following item was missed out of the report: * build artifacts - we're still unable to retrieve these and get 404 errors on selecting the link: