From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] B@D on Windows 10
Date: Tue, 4 Jul 2017 11:48:34 +0200 [thread overview]
Message-ID: <595B6472.3040006@codethink.co.uk> (raw)
In-Reply-To: <87lgo45yz2.fsf@ctlt579.codethink.co.uk>
Hi,
On 04/07/17 11:32, Robert Marshall wrote:
> Robert Marshall <robert.marshall@codethink.co.uk> writes:
>
>> The B at D development team has been investigating if there are any issues
>> with the use of the B at D VM on Windows. The ticket
>> https://gitlab.com/cip-project/cip-testing/testing/issues/106
>> is being used to collect information and workarounds.
>>
>> Briefly the current issues/state is as follows:
>>
>> - We are using virtualbox rather than rsync for config.vm.synced_folder
>> - core.autocrlf=input is needed in the git settings for the scripts to
>> run under Debian (and an ssh client either via git or another route)
>> - We need to look at a substitute for ser2net running on the host in
>> order to open a connection from the VM to the BBB
>> - The VM installs and both the KernelCI webserver and Lava2 run
>> - Having built a kernel the build does not appear in the KernelCI web
>> interface, there's a long delay before it times out
>> - Health checks can be created but they don't appear to run, the admin
>> interface knows about the devices but they don't appear in
>> Scheduler->All Devices
>>
>> This testing has been carried out directly from the pure Vagrant install
>> - once this is running the pre-loaded Vagrant box will also be tested.
>>
>> Further work is continuing to get B at D fully operational on a Windows 10 host.
>>
>
> To report on the progress since Friday:
>
> - KernelCI does not work with Microsoft Edge or Internet Explorer - we
> recommend the use of firefox to display kernel build results - where
> the KernelCI web interface does work.
> - The hostname in the VM is different when run from windows a MR
> has been created to deal with both versions of this
> - The QEMU health check now runs on the W10 virtual machine
> - The BBB health check will run when connecting to a BBB attached to a
> debian machine from the Windows VM both with the linaro kernel and a
> locally built one
Can someone confirm the above results, please? Now that Robert is the
only person working on the testing front, double checking his results by
other companies/contributors becomes almost imperative.
Thank you Robert, good progress this week.
As usual, you can also meet us at #cip in freenode.
> - We are still in progress of creating and testing a local initiramfs
> and configuring the FTDI connection correctly
>
>
> Robert
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next prev parent reply other threads:[~2017-07-04 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 8:13 [cip-dev] B@D on Windows 10 Robert Marshall
2017-07-04 9:32 ` Robert Marshall
2017-07-04 9:48 ` Agustin Benito Bethencourt [this message]
2017-07-05 0:44 ` Daniel Sangorrin
2017-07-05 9:47 ` Agustin Benito Bethencourt
2017-07-07 10:47 ` Robert Marshall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=595B6472.3040006@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox