gt; > any way it wants, note that options above don't require much
> > "configuration", for example --type= just maps to top-level download
> > dir.
Just wondering how much overlap there could be between publishing for
CI and publishing IP addresses between clie
On 3 June 2013 19:18, Paul Sokolovsky wrote:
> On Mon, 3 Jun 2013 12:57:43 +0100
> James Tunnicliffe wrote:
>
>>
>> I know some of our ARM slaves are a bit CPU light, but they also tend
>> to have slow network connections. I am sure a bit of experimentation
>> will tell us if we we should always
the changes I have
considered are quite intrusive for this part of the code.
We could document these as "overrides" using a comment but that won't
change how PyCharm shows the file, yet this "error" has nothing to do
with PEP8 AFAICT.
How intrusive do we want to go for PE
lava-dispatcher to a point where there are no problems
reported by pep8 or flake8 (modulo the line length) *and* PyCharm is
also happy to show all the files as without warnings.
I'll push the changes selectively, there is a proposed merge for files
which only need whitespa
e return code of
> the previous command in the prompt before, but don't know if I need to
> get images set up to do that or if I can script setting that up as
> part of a test or boot process.
lava_test_shell will provide that scripting. (MultiNode extends that
support to add
ith no other changes. Configuration changes need to
happen in etc/ (and the db).
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists
tall, compile & run results.
> > bootchart is just a use-case. it needs to set up the OS, reboot to
> > collect data, finally test results are available.
That is just what LAVA does with two lava_test_shell blocks.
> Maybe my solution with two test definitions is the right
On Tue, 27 Aug 2013 14:34:09 +0300
Fathi Boudra wrote:
> On 27 August 2013 14:17, Neil Williams wrote:
> > It is up to the test writer to put the reboots in the right places.
> > What we do need to do is document that this is done by having more
> > than one lava_test_she
value per testdef? In the
> last example can 'installer.yaml' have a timeout of 60 and
> 'parser.yaml' a timeout of 900?
No. Only lava_test_shell parameters support the timeout, not the
testdef_repos or testdef_url. To change the timeout, you need to have
multiple command
can see has worked in other tests or use one of the KVM types to test
your own installation.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation
worker, or is there an easy way to test
> > the connection between the two?
As long as the scheduler daemon is running on the worker, the scheduler
log on the worker should give some indication of whether it can connect.
The log also shows how many configured devices the scheduler thinks it
has.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation
ll always
be content in the scheduler log if the scheduler is running.
If it's not running, try executing the command directly as root - at
least that way you'll see any errors.
The command on the worker will be similar to what clearly *is* running
on the master, with the loglevel cha
l use of setup instead of setupworker could have messed up
the database configuration on the worker. It just looks like the worker
cannot find the database.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
__
this, so this has been deployed from scratch using the updated
> commands you gave me.
>
> Possibly the issue is with the configuration of the master. There
> has already been one issue with the postgresql setup, so possibly
> there are more. I will look into it.
It may well be wi
pgrades and add
any comments you have regarding why your master postgresql configuration
still wasn't right.
It needs to be possible to take a "stand-alone" master with it's own
devices and add a remote worker using lava-deployment-tool
upgrade just using the tool and without
be in this column and I will add the data
> manually to try and resolve the problem.
The queries being sent need to handle the new field, it's not missing
data because the field is typically empty.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
on which
gives you a starting point for a job of your own.
panda03 has been fairly quiet recently, so a lot of the recent jobs are
health checks - those cannot be directly submitted by users.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.a
involve interim kernel builds - it is all too easy
to make a commit which gets turned into a LAVA job which leads to a
kernel panic in the test. If that was the main kernel for the device,
*someone* (i.e. the LAVA lab admins) would have to fix it. Restricting
tests to submitted jobs is that fix
nces//etc/lava-dispatcher/device-types
> on our control server, would all of the remote workers pull these
> settings in?
No. What LAVA is currently doing is using salt to push the file from
"control" to each remote worker.
--
Neil Williams
=
l-d-t should not be
doing.
I've just upgraded playground using current l-d-t without errors. We've
also seen no problems with staging or with local upgrades. (The
documentation step is run on both upgrades and installs in the same
manner.)
The manpage change went in on the 8th.
-
e. In
> particular, steps 2. and 3. seem like something it would be reasonable
> for LAVA to provide helpers to do.
The LAVA support for this would be to use filters and Image Reports on
the server, not during the test when repeating the analysis means
repeating the entire te
require particular services to be installed and running on all
nodes which lava-network does not enforce.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
On Wed, 27 Nov 2013 13:29:16 -0300
Antonio Terceiro wrote:
> On Wed, Nov 27, 2013 at 04:13:14PM +0000, Neil Williams wrote:
> > Data cannot go over the existing API connection, it has to be
> > configured separately over something like TCP/IP and root on node01
> > does
On Thu, 28 Nov 2013 14:35:21 +1300
Michael Hudson-Doyle wrote:
> Neil Williams writes:
> > MultiNode result bundle aggregation combines completed results
> > after all test cases have run (specifically, during the
> > submit_results action), at which point no fu
;ll see if I can reproduce in a
quantal VM. In the meantime, try switching to Precise.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@
oordinator installed correctly.
The only thing I had to do was install software-properties-common to
bring in the add-apt-repository support.
I can only assume it is some problem on your own system?
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
y provides credentials for the initial submission, the
rest is done by tokens within LAVA.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-valida
/srv/lava/instances//etc/lava-dispatcher/devices/kvm01.conf
You may need to create the devices/ directory.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing l
t;device" relates to the kvm01.conf device configuration
file:
> Exception: no config files named u'devices/kvm01.conf' found
>
> Path "device" must be a relative path, so you need to find out where
> exactly it is.
/srv/lava/instances//etc/lava-dispatc
pported tags when the TestJob does not require the services
provided by devices with those tags will simply delay the running of
that TestJob by limiting the number of devices suitable for the job.
Please start changing any CI jobs *now* to prevent interruptions to
submissions. Removing tags wi
bmission will fail.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation
shed from other key=value pairs
from other job definitions, e.g. when used as part of lava-network. The
messageid is used to do this.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
li
A-849 - Support running virtual machines on devices under test -
supporting Antonio & Senthil where requested.
--
Neil Williams
=
neil.willi...@linaro.org
http://www.linux.codehelp.co.uk/
___
linaro-validation mailing list
linaro-v
- table position fix
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro
om/a/linaro.org/document/d/1fYn6dj44_3jnQs7wfSkp2vxbWXKNdzaoezQA28Tbte4/edit#heading=h.u0tv2mccywk2
# Issues #
* No longer re-basing lava-server packaging branch, too many conflicts
for a public branch. Gerrit merges into lava-server tip are being
cherry-picked into the packaging branch.
--
Neil Will
pe entries in your JSON - make sure these exact types
exist on the server to which you are submitting the job.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing
=h.u0tv2mccywk2
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation
t tools are included to rebuild the packages from
the packaging branch.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.
# Progress #
* LAVA-333
* cherry picking updates for packaging branch
* packaging updates for dependencies
* LAVA-856
* testing vm-groups on arndale & playground.
* Time
* packaging : 20%
* vm-groups: 80%
# Plan #
* vm-groups testing
--
Neil Williams
=
# Progress #
* LAVA-333
* cherry picking updates for packaging branch
* packaging updates for dependencies
* LAVA-856
* testing vm-groups on arndale using staging & playground.
* Time
* packaging : 20%
* vm-groups: 80%
# Plan #
* vm-groups testing & packaging testing
--
be available in
the same way.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo
one remaining dependency which is due to be merged into
lava-server - linaro-django-xmlrpc. Other changes in the packaging
branch are mainly cherry-picked updates from master for lava-server and
lava-dispatcher.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Descrip
umenting for packaging branch
* migration planning for merging packaging branch
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.li
relevant packages
are purged. (Standard apt/dpkg behaviour: apt-get remove will leave the
configuration files in place, apt-get --purge remove will remove those
as well.)
The update also includes a fix for lava-dispatcher LAVA_NETWORK_IFACE
setup and the latest update of lava-tool.
--
Neil
-modules.conf
file.
lava-server: the sshfs mountpoint only has sub-directories created on
the master and does not try to change permissions on files across the
sshfs from the worker side.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
: 30%
* migration: 70$
# Plan #
* complete migration of playground & run test jobs
* migrate staging and run the functional tests
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-va
Migration support for moving off lava-deployment-tool/Precise is
currently under test and the documentation is being improved.
http://localhost/static/docs/migration.html
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
The Job Submission Wizard is now included and the tables have had
numerous improvements. More documentation updates.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation
will be respected by future lava-server upgrades, so the
choice of OpenID service is open to the local admin.
(If there are other OpenID servers people want to use, this support
should work but note that OAuth2 is the preferred option, so it may
only be a temporary step.)
--
Neil William
groups.
* Time
* packaging : 30%
* migration: 70$
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org
onf
for d-i and for other package installs, using parameters where
required. It would be a different kind of deployment with custom
deployment data based on the underlying OS.
A separate action would be the best way to implement that.
--
Neil Williams
=
h
sults (currently
> have 75 pm-qa test runs for beaglebone-black), or am I
> misunderstanding the purpose of count?
This might be a limitation in the linaro-django-xmlrpc support
integrated into lava-server. The xmlrpclib docs do appear to hint that
the usual python default argument syntax shou
On Thu, 29 May 2014 14:30:26 +0100
Neil Williams wrote:
> On Tue, 27 May 2014 15:44:10 -0700
> > get_filter_results(filter_name, count=10, offset=0)
>
> I get working results with:
>
> print "filter results: %s\n" %
> server.dashboard.get_filter_results(filt
includes all changes for the LAVA 2014.05 release.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org
http://playground.validation.linaro.org/static/docs/dummy-deploy.html#configuration-dummy-ssh
A Fedora image running on a dedicated (Ubuntu/Debian) machine as a kvm
device type would be the best option, if you can find / create a
Fedora KVM image which works with qemu.
--
Neil Wi
how to migrate are available in
the migration documentation on staging.
https://staging.validation.linaro.org/static/docs/migration.html
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
%
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation
b - you lose the ability to re-test and
you lose all the context of the results.
There are times when developers will pull sets of bundles from a server
or manipulate bundles directly but this is for testing. It makes no
sense for a CI loop to have results without context.
--
Neil Williams
===
s externally can be executed
within LAVA - all it needs is a connection to that box. If you don't
want a cleanly booted image, then use a connection to a dirty
environment which is already running but a clean environment is
preferable.
LAVA can support multiple nodes per test job, so you could do all th
ckages on the ssh
host or if you're using Android. You should be able to use a "ubuntu"
target_type even when connecting to Fedora if all the packages you need
are already installed. We don't have Fedora users in the team, so
various bits of Fedora deployment are untested and poss
community support
* Time
* cards: 20%
* bugs: 30%
* code reviews: 20%
* bbb: 30%
# Plan
* LAVA sprint & dispatcher refactoring.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
___
li
://validation.linaro.org/dashboard/streams/anonymous/botao-sun/bundles/78eda41094d97f424fe281d2c55436e4a896aeb3/
>
> Similar jobs are:
>
> https://validation.linaro.org/scheduler/job/138636
>
> https://validation.linaro.org/scheduler/job/138560
>
> https://validation.linaro.org/scheduler/
jobs with the build 718: 139428 which was Complete
and 139427 which was Incomplete: ErrorMessage: The test case(methanol)
on device(10.254.30.148:) timed out.
https://validation.linaro.org/scheduler/job/139427
Better identification of such failures is part of the dispatcher
refactoring.
--
E-mail: huangwen...@hisilicon.com
>
> Best Regards.
>
> Huangwenhui
>
--
Neil Williams
=
neil.willi...@linaro.org
http://www.linux.codehelp.co.uk/
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
e pokes the relevant parts of /sys/.
> P.S. I know the Arndale boards haven't been happy with pm-qa for a
> while.
I think this is the wrong mailing list for problems related to bugs in
the kernel or the test suite.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
field of storage and computing.
>
> Follow-up to do a lot of functional tests on LAVA testing platform for
> computing and storage. So we want to know whether LAVA considered adding
> related-testcase.
>
>
>
>
>
> 发件人: Neil Williams [mailto:neil.willi...@linaro.org]
&g
need to be designed and tested by
whoever wants the test results. Everything else that may become
necessary is down to what tests need to run on the board.
--
Neil Williams
=
neil.willi...@linaro.org
http://www.linux.codehelp.co.uk/
___
l
Correct, you do not automatically have permissions to view all reports.
Which parts of dashboard are you trying to view? A list is much more useful
than a picture. Please ask your team lead about which reports you should be
able to access for team requirements.
On 4 Aug 2014 07:03, "Chase Qi" wro
now]
>linaro-android-member-ti_panda-linaro
>
>
> Thanks,
> Chase
>
>
>
> On 4 August 2014 16:16, Neil Williams wrote:
>>
>> Correct, you do not automatically have permissions to view all reports.
>> Which parts of dashboard are you trying to view?
; contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
> ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ,
> Registered in England & Wales, Company No: 2557590
> ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ,
> Registered in England & Wales, Company No: 2548782
>
--
Neil Williams
=
neil.willi...@linaro.org
http://www.linux.codehelp.co.uk/
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation
ta.py#L70
Sample LAVA test job:
https://staging.validation.linaro.org/scheduler/job/50882.1
There could be changes needed in the test image as this was changing
during the finalising of the change in LAVA.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
signature.asc
Descrip
earlier in the function:
# Set the default boot commands
if default is None:
boot_cmds = self.deployment_data['boot_cmds']
else:
boot_cmds = default
Please see the documentation on ways to contribute patches for LAVA:
https
rom the hacking session:
https://staging.validation.linaro.org/dashboard/streams/anonymous/codehelp/bundles/3e2a9c96c9704821cd93cd70f079568335f34cca/7acb16f6-dd47-4741-877e-a5d16bc2fdd4/
Thanks to Milosz for implementing the changes from the session.
--
Neil Williams
=
neil.willi...@
quot;oldstable" into 2017.
--
Neil Williams
=
neil.willi...@linaro.org
http://www.linux.codehelp.co.uk/
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-validation
ou
would have been offered the related documentation.
The guide is here:
https://validation.linaro.org/static/docs/migration.html
This is the recommended path:
https://validation.linaro.org/static/docs/migration.html#debian-jessie
--
Neil Williams
=
http://www.linux.codehe
admin or whatever you call the user submitting these
Jenkins jobs).
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
pgpMuiWCTuw4Z.pgp
Description: OpenPGP digital signature
___
linaro-validation mailing list
linaro-validation@lists.
tyle formatting) in
> the device file would be useful:
>
> boot_cmds_ramdisk =
> setenv usbethaddr ,
>%(boot_cmds_ramdisk)s
>
> Is there a good way of doing that?
>
> Kevin
>
--
Neil Williams
=
neil.willi...@linaro.org
http://www.linux.cod
in due course. The
slides are already available.
[0] https://sfo15.pathable.com/meetings/302656
[1] https://sfo15.pathable.com/meetings/303074
--
Neil Williams
=
Tech Lead LAVA Software
http://www.linux.codehelp.co.uk/
pgpDTUjW7MTbE.pgp
Description: OpenPGP digital signature
On Mon, 28 Sep 2015 10:25:51 +0100
Neil Williams wrote:
> https://lists.linaro.org/pipermail/lava-announce/2015-September/00.html
>
> This list is to be renamed to lava-devel for discussions directly
> relating to the refactoring, new support, use cases and discussions
> a
s (use the version in
Jessie as outlined in the bug report above).
When this bug report is closed, the package can be upgraded again.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
pgp53_rT78UB4.pgp
Description: OpenPGP digital
is a better
option, so make a backup and ensure that the backup works.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
pgp7Gjav6v1wv.pgp
Description: OpenPGP digital signature
___
linaro-validation mailing list
linaro-validation
e original.
Please talk to us and test out what you are going to do.
https://validation.linaro.org/static/docs/support.html
--
Neil Williams
=
neil.willi...@linaro.org
http://www.linux.codehelp.co.uk/
___
linaro-validation mailing l
interested in or using LAVA is encouraged to subscribe to the
lava-announce mailing list which is low volume and only used for
substantial changes like this.
https://lists.linaro.org/mailman/listinfo/lava-announce
See also https://validation.linaro.org/static/docs/support.html
--
Neil Williams
n the trusty-repo on
images.validation.linaro.org and that will be the last change.
At this stage, there is *no* supportable way to incorporate any
releases after 2015.9.post1 on Trusty, that is why we are freezing
trusty support.
--
Neil Williams
=
neil.willi...@lin
jango authentication modules, also
let us know.
--
Neil Williams
=
neil.willi...@linaro.org
http://www.linux.codehelp.co.uk/
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-validation
, this means that refactoring will have an impact here
- once the code support for Bundle et al is removed, there will be
database migrations to drop those tables. Just dealing with those
migrations is going to be an issue for large instances.
--
Neil Wi
On Mon, 4 Jan 2016 20:17:55 +
Neil Williams wrote:
> On Mon, 04 Jan 2016 15:37:38 +0100
> Sjoerd Simons wrote:
>
> > Hey all,
> >
> > Our lava instance is currently well over 120.000 jobs ran, which is
> > great.
> >
> > Unfortunately this m
on with scheduling priorities of it's own like lavapdu.
vland is not merged into master yet, the pipeline protocol code is here:
https://review.linaro.org/#/c/7719/
The actual vland daemon code is here:
http://git.linaro.org/lava/vland.git
Hope this helps.
--
Neil Williams
=
ht
7; traffic between the two hosts.
> Should I see the slave somewhere in django application?
> On the Admin/worker view I only see the master.
>
> master: lava-server 2015.12-3~bpo8+1
> slave: lava-dispatcher@c391b53231fba978532327d2bdff5173fcb55db4
Check the /var/log/lava-scheduler/lava-ma
On Mon, 18 Jan 2016 23:57:09 +0100
Alexander Couzens wrote:
> On Mon, 18 Jan 2016 18:38:29 +
> Neil Williams wrote:
>
> > You're a bit ahead of the docs at this point.
> > ;-)
> ;)
>
> > Pipeline-only workers would need to be added on the command li
t: ssh" expects a fully booted device.
Yes - you'd need something like the secondary media support or a second
deploy to actually get a rootfs into which can be installed
openssh-server (and doing the installation will require the 'os' field).
You may simply need t
- lava-announce is a read-only list. Posts to this list
are only made by the LAVA software team. Replies need to be directed
to
linaro-validation@lists.linaro.org - your email client should do this
for you, using the Reply-To header added by mailman.
--
Neil Williams
=
neil.willi
://yaml-online-parser.appspot.com/?yaml=&type=json and make sure
it parses as valid YAML.
> b. how our test-job YAML (a simple pass/fail test, just to demonstrate
> it runs in the log files) should look like?
A working ssh-host job file for beaglebone-black is attached.
>
&g
s not
need to be configured - the tftpd-hpa package is installed by
lava-dispatcher dependencies and can be used as-installed.
> 3. How the LAVA dispatcher use the connection commands
The command is executed as-is when the connection needs to be made.
--
Neil Williams
AD:/staging.validation.linaro.org/lava/device-types/beaglebone-black.conf
The device configuration for a device like this is:
https://git.linaro.org/lava/lava-lab.git/blob/HEAD:/staging.validation.linaro.org/lava/devices/staging01.lavalab/staging-black01.conf
--
Neil Williams
=
http://www.l
packet
sniffing, https is what you want.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
pgpItp0zNm_gD.pgp
Description: OpenPGP digital signature
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-validation
ll lava
> to use the other network interfaces?
Use a second slave, instead of doing firewall / routing tasks on the
slave.
The only configuration that the pipeline V2 dispatcher will use is the
configuration sent from the server and it seems unlikely that
.
https://www.djangoproject.com/download/
lava-dispatcher is unaffected.
--
Neil Williams
=
neil.willi...@linaro.org
http://www.linux.codehelp.co.uk/
___
linaro-validation mailing list
linaro-validation@lists.linaro.org
https
ld also show up on the list of pipeline devices:
e.g. https://staging.validation.linaro.org/scheduler/alldevices/pipeline
We're expanding the documentation in this area. You may find this proposed page
useful:
https://git.linaro.org/lava/lava-server.git/commitdiff/12f0b078186b319db9df841088b02b8666dae3b3
nks,
>
> Josue Albarran
>
> -Original Message-
> From: linaro-validation
> [mailto:linaro-validation-boun...@lists.linaro.org] On Behalf Of Neil
> Williams Sent: Friday, July 01, 2016 3:56 AM To:
> linaro-validation@lists.linaro.org Subject: Re: [Linaro-validation]
>
1 - 100 of 148 matches
Mail list logo
