Re: autobuild system of linaro
Hi Paul, For daily build packages, you can download from http://snapshots.linaro.org/11.05-daily/, there is an introduction on https://wiki.linaro.org/Releases/DailyBuilds For image creator tool, you can get the latest code by $ bzr branch lp:linaro-image-tools, or get a release from https://launchpad.net/ubuntu/natty/+source/linaro-image-tools. On Wed, 2010-12-15 at 09:48 +0100, Alexander Sack wrote: > On Wed, Dec 15, 2010 at 9:39 AM, Alexander Sack wrote: > > Hi Paul, > > > > On Wed, Dec 15, 2010 at 9:28 AM, Paul Li wrote: > >> Hi, > >> > >> > >> > >> If I want to build the system from scratch, what should I do? I > >> mean, where to get the deb binary packages of Linaro? Where to get the > >> image > >> creator tool? etc. thank you. > > > > most of the content for that should be linked from > > https://wiki.linaro.org/Source ... let us know if there is anything > > missing to get a start. > > One thing we seem to be missing there is a comprehensive > "Source/BuildingHwpacks" wiki page. The details for that are available > in the spec: > https://wiki.linaro.org/Platform/UserPlatforms/Specs/10.11/HardwarePacks > > Basically what you need is a hwpack config like one from here: > https://code.launchpad.net/linaro-images > > ... and then use hwpack-create from lp:linaro-image-tools > > Would be great if you could take a few minutes afterwards to write up > a short Source/BuildingHwpacks intro for us. Thanks and let us know! > -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Call for testing: linaro-media-create
Hi, Guilherme, I checkout revision 196, and use 1204 daily build to verify, the SD card is burned successfully, but there is an error return from media_create.remove_binary_dir. + '[' -d /home/spring/linaro/linaro-image-tools/root-disc ']' + cleanup_tempfiles + rm -r /tmp/tmp.STMDNpUpGK + cleanup_loopbacks + local d + '[' -n '' ']' + python -m media_create.remove_binary_dir + '[' 100 '!=' 0 ']' + remove_image_file + '[' -f '' ']' spr...@ic:~/linaro/linaro-image-tools$ echo $? 100 And there is an long waiting time after the following line, could we add some process information during it? Unpacking hardware pack ...Done Reading package lists... Done On Fri, 2010-12-10 at 12:11 -0200, Guilherme Salgado wrote: > Forgot to mention that there's one new dependency which you may need to > install in case you don't have it yet: python-parted -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Linaro 11.05 Alpha-3 Candidate testing
On Wed, 2011-03-02 at 19:18 +, Jamie Bennett wrote: > Hi, > > The Linaro 11.05 Alpha-3 image [1] is set to be released on Thursday 3rd > March (tomorrow [2]) and we need your help. In addition to our > in-house validation testing we ask anyone with supported hardware, as > found on: > > http://releases.linaro.org/platform/linaro-n/hwpacks/alpha-3-rc/ > > to test the Alpha-3 release candidates at: > > Linaro Ubuntu Desktop LEB (Linaro Evaluation Build): > http://releases.linaro.org/platform/linaro-n/nano/alpha-3-rc/ Should be http://releases.linaro.org/platform/linaro-n/ubuntu-desktop/alpha-3-rc/ > > Nano: > http://releases.linaro.org/platform/linaro-n/nano/alpha-3-rc/ > > ALIP: > http://releases.linaro.org/platform/linaro-n/alip/alpha-3-rc/ > > Developer Tools: > http://releases.linaro.org/platform/linaro-n/developer/alpha-3-rc/ > > The Nano and Ubuntu Desktop LEB are both new for this milestone so extra > testing would be appreciated. Also note that the headless image has been > replace by the Nano (for small installations) and Developer (for a > headless + developer tools solution). Netbook has similarly been replaced > by the Linaro Ubuntu Desktop image. > > Please make your way to: > > http://wiki.linaro.org/Releases/DailyBuilds > > for an explanation on how to test and submit your results to the QA > tracker at: > >http://qatracker.linaro.org > > For an explanation of how to use the qatracker please see: > >https://wiki.linaro.org/QA/QATracker > > Happy Testing ! > > Regards, > Jamie. > -- > Linaro Release Manager | Platform Project Manager > > [1] https://wiki.linaro.org/Releases/1105/Alpha3 > [2] https://wiki.linaro.org/Releases/1105/Schedule > > _______ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: About how to integrate android test into LAVA
s_host_post=RUN_STEPS_HOST_POST)
>> >
>> > parser = lava_android_test.testdef.AndroidTestParser(PATTERN)
>> > testobj = lava_android_test.testdef.AndroidTest(testname=test_name,
>> > installer=inst,
>> > runner=run,
>> > parser=parser)
>> >
>> >
>> >
>> ###
>> >
>> > And in the command part, you can use
>> >
>> > "$(SERIAL)" to represent the device serial number, like:
>> > RUN_STEPS_HOST_POST = [ 'python
>> > %s/android-0xbenchmark/android_0xbenchmark_wait.py $(SERIAL)' % curdir]
>> >
>> > and
>> >
>> > "$(OPTIONS)" to represent the option string passed from command line.
>> Like
>> > INSTALL_STEPS_HOST_PRE = [ 'echo $(OPTION)'],
>> > RUN_STEPS_HOST_PRE = [ 'echo $(OPTION)'],
>> >
>> > then you can run lava-android-test install -o "install options string"
>> > or lava-android-test run -O "run options string"
>> >
>> >
>> > Note:
>> > Because lava-android-test will be run on lava-lab, and there
>> will
>> > be multiple devices connected simultaneously,
>> > So we should consider to pass the device serial number for
>> each
>> > test tools.
>> > If the test tools is defined
>> > for steps_adb_pre/adbshell_steps/steps_adb_post,
>> > then there is no need to pass the device serial
>> > number, lava-android-test will do this for you.
>> >
>> > 5. you can
>> > use "lava-android-test list-tests" to check if the test wrapper
>> created
>> > can be recognized,
>> > use "lava-android-test install ${test_name}" to install the test,
>> > use "lava-android-test run ${test_name}" to execute the test,
>> > use "lava-android-test show ${result_id}" to show the output
>> > the test executed,
>> > use "lava-android-test parse ${result_id}" to to generate the result
>> > bundle for the test executed.
>> >
>> > And here is a blog about install/test lava-android-test that you can
>> > reference:
>> >
>> >
>> http://www.linaro.org/linaro-blog/2011/12/01/local-lava-testing-of-android-ics/
>> >
>> > 6. When you have done the above steps and verified your test that works
>> > well, then you can integrate it in LAVA with the android-build.
>> > Here is a description about that.
>> >
>> https://wiki.linaro.org/Platform/Android/AndroidBuild-LavaIntegration
>> >
>> >
>> > If you have any questions, please contact me.
>> > Also I have copied it to google docs,
>> >
>> https://docs.google.com/a/linaro.org/document/d/1kVyuFZtnMsganZaszQZhgX3QPOF5KXhKvefCUq4Xh3A/edit
>> > you can comment directly there.
>> >
>> >
>> > Thanks,
>> > Yongqin Liu
>> > -
>> > Mail: yongqin@linaro.org.
>> > IRC Nickname: liuyq
>> >
>> > ___
>> > linaro-dev mailing list
>> > linaro-dev@lists.linaro.org
>> > http://lists.linaro.org/mailman/listinfo/linaro-dev
>> >
>>
>>
>>
>> --
>> Zach Pfeffer
>> Android Platform Team Lead, Linaro Platform Teams
>> Linaro.org | Open source software for ARM SoCs
>> Follow Linaro: http://www.facebook.com/pages/Linaro
>> http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
>>
>> ___
>> linaro-dev mailing list
>> linaro-dev@lists.linaro.org
>> http://lists.linaro.org/mailman/listinfo/linaro-dev
>>
>
>
> ___
> linaro-dev mailing list
> linaro-dev@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-dev
>
>
--
Best wishes,
Spring Zhang
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: LAVA Dashboard user forum
On 16 June 2011 08:59, Michael Hudson-Doyle wrote: > On Thu, 16 Jun 2011 02:12:19 +0200, Zygmunt Krynicki < > zygmunt.kryni...@linaro.org> wrote: > > W dniu 16.06.2011 00:19, Michael Hudson-Doyle pisze: > > >> I created user forum for the dashboard at: > > >> > > >> http://fracture.suxx.pl/projects/lava-dashboard/boards > > > > > Is there a way I can subscribe via email? > > > > There's a watch icon in each thread/forum. AFAIK you will be notified of > > changes in the objects you subscribed to. > > I can see it in the thread page, but not the forum page :/ > If you use RSS, there's a Atom link in the right-bottom of the forum page. And for watching forum, there are 3 sub-forums watch at the right-upper of sub-forum page, you can watch all of them. Like: http://fracture.suxx.pl/projects/lava-dashboard/boards/5 > Cheers, > mwh > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev > -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: continuous integration for the lava software packages
Does the job always uninstall the previous installed packages? On 22 July 2011 12:24, Michael Hudson-Doyle wrote: > Given the focus of my team's efforts, it's perhaps a bit silly that we > haven't been running our own tests regularly. In any case, I've just > set up a quick n' dirty jenkins job that sets up lava-dev-tool, runs > lava-dev-tool sequence and puts the results here: > > > http://validation.linaro.org/jenkins/job/lava-selftest/lastSuccessfulBuild/artifact/ldt/status.txt > > which perhaps isn't an ideal summary, but it's a start. More > information on the errors will be buried in the logs somewhere :) > > Cheers, > mwh > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev > -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: LAVA master images.
On 22 November 2011 00:10, Zygmunt Krynicki wrote: > Hi Dave. > > I need reference master images for our boards. Do we have an archive > anywhere. I'm interested in Panda, iMX53 loco and snowball if you have > them. One (panda) will do but I can use more once I can get them across the > wire. > What kind of image you like? I have MX53 one but it's a whole TF card image zipped to a .gz, about 1.2GB. I don't know where to place such large file. For master image generation, the general instructions also list on: http://lava-dispatcher.readthedocs.org/en/latest/installation.html#creating-a-sd-mmc-card-with-master-image, maybe not up to date. > Thanks > ZK > > __**_ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/**mailman/listinfo/linaro-dev<http://lists.linaro.org/mailman/listinfo/linaro-dev> > -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Master images are a mess
Generally, there are two ways to drive the boards: by serial line or network(NFS maybe plus NBD). If all switching to NFS, I'm sure there will be other problems in daily using. For the MAC address issue, it will occur both on current master/tester image layout and NFS deployment if uboot can't get board fused MAC address and pass it to kernel. For the master image generation, I think the best way is to make LMC be able to create a custom master SD card layout, now it only needs to extend to shrink boot and rootfs partition, and make two or more blank partitions(testboot and testrootfs) with label in one command. -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Please review blueprint linaro-n-validation-job-dispatcher
On 28 January 2011 08:12, Paul Larson wrote: > Other questions... > > > What does it do after running the test? How, and where does it leave the > results? What get's added to the results (e.g. serial log) and how does > that happen? What is the mechanism for then taking that bundle and pushing > to the server? What happens if there were no results from the client, what > do we capture in that case? > About the test result, I draft a test result bundle template, for a job test result bundle, it is stored in a text file. Dispatcher server part will get the return value of the test case and the serial port log, then create test result together with some info from job message, client dispatcher test logs. I think server dispatcher can fetch the client test logs initiatively after client dispatcher ends. If there is no result from the client, after timeout, 1. server dispatcher send some "Ctrl+C" to client dispatcher to end it. 2. then restart the client dispatcher. 3. try to get the client dispatcher remained test logs. 4. mark the test case to TIMEOUT and create the test result. PS. If step 1 can not end the client dispatcher, it may need a reboot for server dispatcher have lost the control of serial line. Test result bundle composed of every test case result, for each test case result, it includes: - LOG casename:Test case name testsuite:Test suite name testcmd:Test case Command timeout:Timeout retvalue:Return value version:kernel version(by "cat /proc/version") seriallog: serial port log ENDLOG e.g. - LOG casename:PERF001 testsuite:abrek testcmd:x11perf timeout:6 retvalue:0 version:2.6.35- seriallog: xxx xxx xxx ENDLOG And a test result bundle: LOG casename:PERF001 testsuite:abrek testcmd:x11perf timeout:6 retvalue:0 version:2.6.35- seriallog: xxx xxx xxx ENDLOG LOG casename:USB002 testsuite:abrek testcmd:usb_app timeout:6 retvalue:0 version:2.6.35- seriallog: yyy yyy yyy ENDLOG What do you think? The flow to get test result: 1. Server dispatcher sends commands to client dispatcher via serial line to invoke client dispatcher, capture all the serial log and wait for the client dispatcher ends. 2. Client dispatcher executes the command, save logs to some place on the board. 3. If client dispatcher ends normally(return to the "root@testimage:~$" string), server dispatcher uses "echo $?" to get the return value. Or terminate the client dispatcher after timeout. 4. Server dispatcher gets client dispatcher test logs. 5. Server dispatcher uses the collected information to create test result. -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Please review blueprint linaro-n-validation-job-dispatcher
Hi, Paul, For the python environment in the deployed test image, how much support will it provide? Can we deploy additional python libs to the test image if required? Dispatcher client part may need some. -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: problem with linaro-media-create
On 9 February 2011 04:16, Steve Langasek wrote: > Hi Aneesh, > > On Tue, Feb 08, 2011 at 05:43:39PM +0530, Aneesh V wrote: > > > On Monday 07 February 2011 11:07 PM, Steve Langasek wrote: > > >On Mon, Feb 07, 2011 at 03:59:06PM +0100, Alexander Sack wrote: > > >>Since we only really support developer platform hosts with the tools > > >>ppa enabled, could we improve l-m-c to print a warning if that ppa > > >>isn't enabled? > > > >>The other idea I had was to include the working qemu-arm-static in > > >>the tarball releases ... in that way things might even work on > > >>non-ubuntu platform. > > > >Well, given that Aneesh's original message mentioned he was downloading > > >l-i-t directly from launchpad, my first thought was that he indeed > wasn't > > >running Ubuntu on the desktop. Aneesh, was this the case? What are you > > >running on your desktop (distro, version)? > > > I am running Ubuntu Maverick on my desktop. However apt-get didn't work > > for linaro-image-tools. I got this message: > > > E: Couldn't find package linaro-image-tools > > > So, I downloaded it from launchpad as mentioned in the wiki. > > Ok. Which wiki page did you look at? We should be directing maverick > users > to enable the linaro-maintainers/tools ppa, which includes both the > linaro-image-tools and qemu-linaro packages. > I can find linaro-image-tools, but no qemu-linaro on maverick, and I added PPA. > > https://wiki.linaro.org/Releases/DailyBuilds#On%20Ubuntu%2010.10 > > Is there another wiki page with conflicting instructions that we need to > clean up? Or did you read this and go for the download instead of the ppa > (in which case we should clarify the text to direct people to the ppa more > strongly)? > > Thanks, > -- > Steve Langasek Give me a lever long enough and a Free OS > Debian Developer to set it on, and I can move the world. > Ubuntu Developerhttp://www.debian.org/ > slanga...@ubuntu.com vor...@debian.org > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQIVAwUBTVGkqlaNMPMhshM9AQgvkRAArRamc/hlkcFzghRMQvELQAwSC4/SdtVx > umM3CfYPwzw3iQdx20ay2ogRzrRttjac22wvEFCO+a3Jqvv/57tTYge9z27Fqrk2 > +oyK7/2tXKcPd0P5u3CMxkSSXSMdgB2C3sShrl/Bwlfy+PGF2G09+nier3C3cVm7 > g0+nTbQpeKRveqYRr89oJtIYtscmdb/GZDMg9uGWeCHX9N37ZJBL+/mXi9OmAGkx > YXIq/1o6fpEWNjZ5a+ulgnyOfFk99kyfjMrBgEpgBb4oompzghMXHmaII9Gd2Tgd > WCV7Go8z/gzagn/voHiOFlabyRr+ea0VAKRDkBKMx8Kb5H4mBJSiruw7VdRv0JWA > 6nKao+IZcbIa2KI9j9zratygy4PaeHUKwKkUDyRyHbB6F1orNjRNScNZQOy53wg+ > i9CUI0m5z5ctc664VKU/xRS82mPBA5BP/ZFx2MS4K1ossopBH4EZ/Z9gR/kbyeea > YY2Ut37+5XW8e7oK89COvfYgDBSTjwF88mzCSkl99UhGSNk7sN57dAp5xUBD3u6D > e8LgH9KvUW7SY9TX80iy/RKwEIN83ng+8qBuXMJXw6HHdSBjReWMGq4zUwNr7L6g > 1bjwL1YDmfxV3P5QSDKch0ITRMpHs77vbwsCSoEUP3SkJHlqypkeURcyaHTEDGTZ > ZIT3wkXavTU= > =167/ > -END PGP SIGNATURE- > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev > > -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Running linaro-media-create on machine behind firewall
On 8 March 2011 17:19, Shawn Guo wrote: > I'm recently trying to install alpha-3 image using l-m-c on an AMD64 > machine which is behind the company firewall. Though I have apt proxy > set on host machine, l-m-c installing system (chroot env?) does not > know it. Can we improve the l-m-c a little bit to copy apt proxy > setting if any on host machine into installing system? So that the > machine behind proxy can survive with l-m-c too. > > PS. > Actually, I have my machine home which can directly access natty > repository, but it's very slow (see below), probably because there > is no natty mirror in China yet. > Did you try to switch apt source to China in the updater-manager? Can this work: http://ubuntu.cn99.com/ubuntu/dists/ > Fetched 15.0 MB in 10min 22s (24.1 kB/s) > > When I use vpn to connect company network, speed of accessing ubuntu > repository can reach ~200 kB/s. Considering that I'm testing l-m-c > back and forth, I really need a faster apt speed within l-m-c. > > -- > Regards, > Shawn > > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev > -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Do we have a memory footprint evaluation of ubuntu-desktop?
On 18 April 2011 16:03, Dave Martin wrote: > On Mon, Apr 18, 2011 at 03:34:21PM +0800, Eric Miao wrote: > > All, > > > > It was found that the ubuntu-desktop is a bit memory hungry on this > i.MX53 > > QuickStart board. There is a large chunk of memory being reserved for the > > graphics/video drivers, and the memory size reserved has to consider the > > worst case. And we have to live with this before the unified memory > allocator > > is available. > > > > I don't yet have a /proc/meminfo after system is right up, I'll get some > > statistics a bit later. However, I do want to know if we have some memory > I have a try. MX53 loco meminfo on: 20110414 Ubuntu desktop release root@linaro:~# cat /proc/meminfo MemTotal: 868092 kB MemFree: 705228 kB Buffers:5288 kB Cached:74580 kB SwapCached:0 kB Active:75488 kB Inactive: 62940 kB Active(anon): 61168 kB Inactive(anon): 1028 kB Active(file): 14320 kB Inactive(file):61912 kB Unevictable: 0 kB Mlocked: 0 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 868092 kB LowFree: 705228 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty:16 kB Writeback:24 kB AnonPages: 58576 kB Mapped:29208 kB Shmem: 3636 kB Slab: 11080 kB SReclaimable: 5028 kB SUnreclaim: 6052 kB KernelStack:1912 kB PageTables: 2128 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit: 434044 kB Committed_AS: 482812 kB VmallocTotal: 319488 kB VmallocUsed: 165468 kB VmallocChunk: 131068 kB root@linaro:~# smem info after installed smem: http://pastebin.ubuntu.com/595429/ > > footprint evaluation of the existing ubuntu-desktop (we are using > unity-2d)? > > And what can we do to improve on that? > > There's some old data I recorded on netbook-efl which is probably > the closest data I know about: > > > https://wiki.linaro.org/Platform/DevPlatform/MemoryFootprintSampleData#netbook-efl > > I've been focusing on kernel work this cycle, so I don't know if > the memory footprint work has been moving forward. > > Steve may know who's involved now. > > Cheers > ---Dave > > _______ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev > -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: reorganzing the lava projects on launchpad
Seems lava-dispatcher online now, some blueprints change from lava to lava-dispatcher, https://blueprints.launchpad.net/lava-dispatcher/+spec/linaro-platforms-o-lava-dispatcher-improvements, also lava-server and lava-scheduler. On 24 May 2011 12:02, Michael Hudson-Doyle wrote: > On Thu, 19 May 2011 17:05:09 +1200, Michael Hudson-Doyle < > michael.hud...@linaro.org> wrote: > > Hi there, > > > > Some of you know about this already as it was discussed a bit at LDS, > > but probably not very inclusively. > > > > We have a slightly strange arrangement of projects on Launchpad, with > > the main ones being "launch-control" and "lava". AIUI, Zygmunt really > > wanted to call "launch-control" "dashboard" from day 1, but that was > > clearly an overly generic name. Since then, we've come up with the > > "lava" name to cover our automated validation efforts, but currently the > > "lava" project just contains code to do with the validation farm in > > Cambridge, which is only part of the story. > > > > So. We have a plan to reorganize the projects like so (also documented > on > > > https://blueprints.launchpad.net/linaro-validation-misc/+spec/linaro-platforms-o-reorganize-lava-projects > ): > > I've started to do this now, and have mostly split launch-control into > lava-server and lava-dashboard. It's been a bit complicated, to be > honest, but I think it sort of works now. If you create a virtualenv, > get both lp:lava-server and lp:lava-dashboard and run > "$VIRTUALENV/bin/python setup.py develop" in both, then > "$VIRTUALENV/bin/python lava_server/manage.py runserver" in the > lp:lava-server checkout, you should be able to browse around to some > extent. Some things that are clearly lacking: the dashboard has no > front page now, and we need to work on the bread crumbs a bit, but I > think it basically works. > > I'll try to catch Zygmunt tonight and see what needs to be done to > finish the launch-control split, and work on splitting up what's in > lp:lava tomorrow. > > Cheers, > mwh > -- Best wishes, Spring Zhang ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
