Re: [yocto] [Call to Action] Yocto Project Bug Triage
On 5/29/18 8:00 AM, Trevor Woerner wrote: > Is someone working on putting together a (google?) calendar of the > various project (OE Yocto) meetings? Great question. Michael, do we have access to a Yocto Project google account? --S -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Call to Action] Yocto Project Bug Triage
Hi All, Sorry for the cross posting but I want to be sure to hit both the Yocto Project and OpenEmbedded communities with this information. It has been brought to our attention that the weekly bug triage has fallen out of the spotlight and we'd like to get it back into focus. We'd like to encourage anyone who is interested to join us. The invite was sent out to the Yocto Project mailing list: https://lists.yoctoproject.org/pipermail/yocto/2018-May/041308.html We meet once per week to discuss new bugs (bugs with no target milestone) and bugs that might have missed their target milestone. This is a chance for the community to weigh in on features or bugs they care about, as well as to volunteer their time to see that those items are completed on schedule. For those who don't know, we track bugs using bugzilla: https://bugzilla.yoctoproject.org/ To quickly view the bugs that we are triaging during the meeting, you can follow along on the wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage We triage bugs in this order: https://wiki.yoctoproject.org/wiki/Bug_Triage#Bug_Triage_Order Joining this meeting can help keep you up to date with the latest news from the OpenEmbedded and Yocto Project communities. It also helps us better understand and meet the community's needs. Cheers, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project Technical Meeting links
The Yocto Project Technical Meeting is about to start. How To Join: https://www.yoctoproject.org/monthly-technical-call/ Shared Google Doc: https://docs.google.com/document/d/1Lr8KgkmmCZ84RF_ThIwnT3WWxMv_tUsHkpRV5PXTd0s/edit?usp=sharing Cheers, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Setting a custom hostname using git revisions?
On 4/4/18 9:13 AM, Stephano Cetola wrote:
> On 4/4/18 8:48 AM, Giordon Stark wrote:
>> Hi all,
>>
>> I looked at the bitbake manual, but if I have a custom layer that's
>> checked out at a specific revision, how can I access the variable
>> containing the revision to embed it into the hostname variable?
>>
>> I would want to append the hostname variable in:
>> recipes-core/base-files/base-files_%.bbappend which is currently set to
>> "${MACHINE}".
>>
>> Instead, I would like something along the lines of
>> "${MACHINE}-${LAYER_REV}".
>>
>> Thanks,
>>
>> Giordon
>> --
>> Giordon Stark
>>
>>
>
> This is pretty tricky. I'd use a python function inside your recipe.
>
> You can get the layers like this:
>
> layers = (bb.data.getVar("BBLAYERS", d, 1) or "").split()
>
> Then if you have a look at the metadata_scm.bbclass, you can use some of
> the functions in there:
>
> base_get_metadata_git_branch
> base_get_metadata_git_revision
>
> Add some logic and you should be able to pull the revision information
> you care about out of that data.
>
> Cheers,
> Stephano
>
>
A rather elaborate example of how to get the revision number can be seen
here:
https://github.com/openembedded/openembedded-core/blob/master/meta/classes/image-buildinfo.bbclass
--S
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Setting a custom hostname using git revisions?
On 4/4/18 8:48 AM, Giordon Stark wrote:
> Hi all,
>
> I looked at the bitbake manual, but if I have a custom layer that's
> checked out at a specific revision, how can I access the variable
> containing the revision to embed it into the hostname variable?
>
> I would want to append the hostname variable in:
> recipes-core/base-files/base-files_%.bbappend which is currently set to
> "${MACHINE}".
>
> Instead, I would like something along the lines of
> "${MACHINE}-${LAYER_REV}".
>
> Thanks,
>
> Giordon
> --
> Giordon Stark
>
>
This is pretty tricky. I'd use a python function inside your recipe.
You can get the layers like this:
layers = (bb.data.getVar("BBLAYERS", d, 1) or "").split()
Then if you have a look at the metadata_scm.bbclass, you can use some of
the functions in there:
base_get_metadata_git_branch
base_get_metadata_git_revision
Add some logic and you should be able to pull the revision information
you care about out of that data.
Cheers,
Stephano
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel configuration patches not persisting?
On 4/4/18 8:39 AM, Giordon Stark wrote: > Hi Stephano, > > I see. A large part of this confusion probably comes from the fact that > they're both using kconfig indeed. ARCH_ZYNQMP is actually used by the > u-boot-xlnx as well (maybe that makes things even more confusing). > > Do both u-boot and linux-yocto accept kernel fragments? Is a kernel > config fragment detected by bitbake as a file ending in *.cfg and a full > config as a file called "defconfig"? This distinction isn't super clear > in the manual. linux-yocto supports using the .cfg to add configuration fragments for different targets or for multiple configurations on the same target. You can check out meta/classes/kernel-yocto.bbclass to see how this is done. The u-boot recipe is much simpler and any changes to the configuration is probably going to be added in your u-boot tree (configs/[MACHINE]_defconfig). At least that's how I've done it in the past. I know that Freescale uses UBOOT_CONFIG for their boards, but I've never looked into doing this for a custom board. > > In the meantime, I will add a bbappend and a kernel config fragment to > recipes-kernel/linux/ and report back. Sounds good! --S > > G > > On Wed, Apr 4, 2018 at 10:32 AM Stephano Cetola > <mailto:stephano.cet...@linux.intel.com>> wrote: > > On 4/4/18 7:48 AM, Giordon Stark wrote: > > Hi all, > > > > I have a custom board with custom kernel config changes. Because of > > that, I append the u-boot recipe as well: > > > > > > https://github.com/kratsg/meta-l1calo/blob/master/recipes-bsp/u-boot/u-boot-xlnx_%25.bbappend > > > > > with my machine.h and defconfig files > > > here: > https://github.com/kratsg/meta-l1calo/tree/master/recipes-bsp/u-boot/files/gfex-prototype4 > > > > > I find that when I make a change in the defconfig, such as > > "CONFIG_CPU_IDLE=n", bitbake properly recompiles all the necessary > > components... however, when I look at the running kernel > configuration: > > > > root@gfex-prototype4:~# cat /proc/config.gz | gunzip > run.config > > root@gfex-prototype4:~# vi run.config > > root@gfex-prototype4:~# cat run.config | grep CONFIG_CPU_IDLE > > CONFIG_CPU_IDLE=y > > # CONFIG_CPU_IDLE_GOV_LADDER is not set > > CONFIG_CPU_IDLE_GOV_MENU=y > > > > it seems my change still wasn't propagated? I looked at the > instructions > > here > > > > (https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#changing-the-configuration) > > but I'm not sure I want to duplicate my defconfig file into a second > > location to bbappend the linux-yocto. > > > > Have I done something wrong? Am I missing something else? > > > > Giordon > > -- > > Giordon Stark > > Hey Giordon, > > It looks like you're confusing two topics: u-boot and kernel > configuration. > > Both u-boot and the kernel use kconfig. This can confuse folks that are > new to bootloader/kernel work. > > Looking at your layer, you're actually interested in changing the > kernel's configuration rather than u-boot. For example, on the > gfex-prototype4 defconfig, you set ARCH_ZYNQMP, which is a kernel config > for the Xilinx Zynq boards. You probably want to add a bbappend for your > kernel and add the defconfig to that recipe. > > Cheers, > Stephano > > -- > Giordon Stark -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel configuration patches not persisting?
On 4/4/18 7:48 AM, Giordon Stark wrote: > Hi all, > > I have a custom board with custom kernel config changes. Because of > that, I append the u-boot recipe as well: > > https://github.com/kratsg/meta-l1calo/blob/master/recipes-bsp/u-boot/u-boot-xlnx_%25.bbappend > > > with my machine.h and defconfig files > here: > https://github.com/kratsg/meta-l1calo/tree/master/recipes-bsp/u-boot/files/gfex-prototype4 > > > I find that when I make a change in the defconfig, such as > "CONFIG_CPU_IDLE=n", bitbake properly recompiles all the necessary > components... however, when I look at the running kernel configuration: > > root@gfex-prototype4:~# cat /proc/config.gz | gunzip > run.config > root@gfex-prototype4:~# vi run.config > root@gfex-prototype4:~# cat run.config | grep CONFIG_CPU_IDLE > CONFIG_CPU_IDLE=y > # CONFIG_CPU_IDLE_GOV_LADDER is not set > CONFIG_CPU_IDLE_GOV_MENU=y > > it seems my change still wasn't propagated? I looked at the instructions > here > (https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#changing-the-configuration) > but I'm not sure I want to duplicate my defconfig file into a second > location to bbappend the linux-yocto. > > Have I done something wrong? Am I missing something else? > > Giordon > -- > Giordon Stark Hey Giordon, It looks like you're confusing two topics: u-boot and kernel configuration. Both u-boot and the kernel use kconfig. This can confuse folks that are new to bootloader/kernel work. Looking at your layer, you're actually interested in changing the kernel's configuration rather than u-boot. For example, on the gfex-prototype4 defconfig, you set ARCH_ZYNQMP, which is a kernel config for the Xilinx Zynq boards. You probably want to add a bbappend for your kernel and add the defconfig to that recipe. Cheers, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Meeting
Attendees: Armin, Stephano, Robin, Richard, Maxin, Alex K, Sean Gabriel, Martin, Denys, Joshua Watt, Michael Halstead, Pascal Bach, Randy MacLeod, Amanda, Trevor, Tracey If people are aware of items that should be going into 2.5 but are not on the list, please contact Richard. While no high level list exists today we will work on getting that setup. For now, please see the commit logs to determine if a feature you are looking for has been included. The new autobuilder setup will be used for the 2.6 release. Testing on that system can begin soon with the knowledge that some features are not yet implemented. poky-contrib cleanup should be happening regularly and Michael will begin tracking this in bugzilla. AR: Robin - Work to communicate an appropriate high level overview for releases. Be aware Paul usually pulls together the release notes. (the wiki would be higher level) AR: Tracey - Add to the website a page regarding bug triage. AR: Stephano - Add yocto/oe-core/bitbake to bug triage invite. NOTES: "AR" == Action Required "Opens" == Anything you would like to be discussed which is not explicitly on the agenda. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta layers for freescale IMX8 ?
On 3/27/18 6:03 AM, Karim ATIKI wrote: > Hi all, > > We just received some evaluation boards based on Freescale IMX8 Quad. > We'll have to firstly build a custom linux image to test our products. > I'm not experienced with freescales processors. > > Is there some layers managing the recent IMX8 Freescale ? > > Thanks . > > K > You'll want to ask this question on the meta-freescale mailing list: https://lists.yoctoproject.org/listinfo/meta-freescale Also, see the FSL Community BSP: http://freescale.github.io/ --S -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] New Recipes / Recipe Fixes
On 3/27/18 6:28 AM, Eric Schwarz wrote: > Hello, > > is this the right mailing list to post new recipes for libraries to be > included in the openembedded layer and/or recipes patches, respectively? > > Many thanks > Eric Hey Eric, Thank you for looking into contributing to OE & Yocto. Depending on the recipe, you will either submit new recipes / fixes to oe-core or meta-openembedded. oe-core is, as the name implies, reserved for "core functionality". meta-openembedded houses all other peripheral functionality. You can learn more here: https://wiki.yoctoproject.org/wiki/Newcomers Specifically https://wiki.yoctoproject.org/wiki/Newcomers#How_to_Contribute Hope that helps! Cheers, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project Status WW13’18
Current Dev Position: YP 2.5 M3 final close out. Next Deadline: YP 2.5 M4 stabilization is 4/2/18 SWAT lead is currently Ross. SWAT team rotation: Ross -> Juro on March 30, 2018 SWAT team rotation: Juro -> Paul on April 6, 2018 https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: · YP 2.5 M3 rc1 was built and went into QA. This release was built on with the ‘new’ autobuilder codebase. Some issues were found with artefact publication but nothing to block the rc1 as yet. · We are still blocked with morty on the glibc 2.27 and the sdk locale issues · Code has been added to uninative to ensure the glibc corruption that occurred with the newer glibc cannot happen again. · We have found a new issue where fedora 27’s version of coreutils is using syscall() to call a syscall directly and hence corrupting permissions of some files from pseudo’s perspective. We’re currently discussing this with upstream as its looking problematic to fix and we’d much prefer they use the glibc wrappers. · We have a fix for the qemuarm64 hangs during early boot, thanks to everyone who’s helped fix that, its much appreciated and will help our automated tests. · A significant win in opkg compression speed was found (thanks Ross!) Planned upcoming dot releases: YP 2.3.4 (Pyro) will be built after 2.5 M3 YP 2.2.4 (Morty) will be built after 2.5 M3 once the glibc 2.27 issue is fixed YP 2.4.3 (Rocko) is planned for post YP 2.5. Key YP 2.5 Dates are: YP 2.5 M3 is in QA. See status above. YP 2.5 M3 was scheduled for release 3/2/18 YP 2.5 M4 cut off of 4/2/18 YP 2.5 M4 release of 4/27/18 Tracking Metrics: WDD 2673 (last week 2673) (https://wiki.yoctoproject.org/charts/combo.html) Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status [If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to "compute" path to install module file
On 3/22/18 12:31 AM, Vincent Daanen wrote: > Hi, > > I’m porting the makefile to build SocketCan for Ixxat on yocto. At this > time I successfully build the module file. Have you checked out the CANopen drivers? https://github.com/ros-industrial/ros_canopen https://github.com/bmwcarit/meta-ros/tree/master/recipes-ros/ros-canopen There are already recipes for this if it happens to work for your part. Just figured I'd mention it :) For adding the Ixxat driver, this documentation might help: https://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#working-with-out-of-tree-modules > > Build fails with the following error: > > nothing provides kernel-module-ixx-pci-4.12.14-yocto-standard needed by > kernel-module-ixxat-candriver-1.0-r0.qemux86_64 Do you have a recipe that provides ixx-pci? If so it needs to say: PROVIDES = "ixx-pci" https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-PROVIDES Also, you need to be sure that it is being built, so I would add that recipe into some RDEPENDS variable, for example: MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "ixx-pci" (in this case in your machine conf, assuming the package name is "ixx-pci") > > I don’t understand how yocto computes to module filename. It adds the > kernel-version to the default filename… check out the "module_pattern" variables in: meta/classes/kernel-module-split.bbclass I believe this is done during packaging. Cheers, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [RFC] Priority Settings Between Layers
We're updating our manuals and I want to be sure the information we are providing is correct. Here is the section in question: TIP Ordering and BBFILE_PRIORITY for the layers listed in BBLAYERS matter. For example, if multiple layers define a machine configuration, the OpenEmbedded build system uses the last layer searched given similar layer priorities. The build system works from the top-down through the layers listed in BBLAYERS. Is this accurate? I have tested this with a simple machine config example but I want to be sure I am not missing anything. Also, I'm assuming this holds true for all configurations, not just machine. Cheers, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] New Release Number 2.99 in Bugzilla
The Yocto Project team is moving to a new release planning process and I want to provide an overview as there will be some things I need from those of you making changes and adding things to Bugzilla. Overview: We are moving to a “Pull” process for planning rather than a “Push” process. What this means is that we will start with an empty 2.6 release bucket and pull bugs and enhancements in that map to our top priorities rather than push things out of a giant bucket. We are hoping this will help us start 2.6 with a very clear idea as to what we will focus on and be much less overwhelming than pushing a giant snowball through each release. How does this effect you? If you are pushing bugs/enhancements to the next release or adding new bugs/enhancements for the next release you need to be aware of the following: -We have a M+ Future status that holds items that are important and need to be addressed soon. This bucket is pretty big. -We have moved all 2.6 features and bugs to a 2.99 release. This bucket is a temporary hold for the items that didn’t make it into 2.5 and are at the very top of our list for review to pull in. We don’t want them to get lost in the M+ Future bucket. Once 2.6 planning is complete, this 2.99 bucket will be empty and removed. -If you are adding new bugs and enhancements that you believe should be slotted for 2.6, please enter them as 2.99. -If you are pushing anything from 2.5 to 2.6, please enter it as 2.99. Please let me know if you have any questions about this. Thanks, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Meeting
Attendees: Armin, Stephano, Juro, Stephen, Ross, Joshua Watt, Amanda, Tim, David Reyna, Denys, Randy, Michael Halstead, Richard, Alex Kanavin, Bill Mills, Mark Hatle, Tracey Erway Current Status: https://wiki.yoctoproject.org/wiki/Weekly_Status It was mentioned that the 2.6 features should be discussed on the YPTM next month. The hope is that people who have submitted feature requests can give some feedback and possible help by contributing. Any secondary GCC (e.g. 6.4 on Rocko) is hard to test on the autobuilder. We should look into ways to automate this task if possible. Also, Mark brought up that there is a built-in test suite in GCC which YP isn't using. There is a long standing bugzilla entry for that: https://bugzilla.yoctoproject.org/show_bug.cgi?id=4437 Please feel free to comment with suggestions. Cheers, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem in the building phase - Yocto 2.4.1 for Siemens IoT 2040 (Intel Quark)
On 2/22/18 3:59 AM, Pulizzotto Alessio (COMAU) wrote: > Hello, > > I’m writing you because I have some problems with the building of an > 2.4.1 image of the Yocto. > > I am using a Siemens IoT 2040 hardware witch have an intel quark cpu. > > My error is the follow, in the “bitbake name-image”: > > “ExpansionError during parsing > ***/poky/meta-java/recipies-extended/xmlpull/xmlpull_1.1.3.4c.bb” > > And at the end: > > “module bb.data has no attribute ‘getVar’” > I am currently building for a product using Quark + Java running YP 2.4.1. Here are the SHAs that are working for me: meta-yocto-bsp yocto-2.4.1 c2b641c8a0c4fd71fcb477d788a740c2c26cddce meta-intel 8.0-rocko-2.4 d68dda959b5bf6f90aa8e5c2f027be324bb68e14 meta-java master 03e35bf64f97980652ac532cca0ea96e730a551c Cheers, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Meeting
Attendees: Armin, Stephano, Alex, Maxin, Amanda, Stephen, Richard, Pascal, Ross, Denys, Joshua Watt, Tim Orling, Martin/Oliver/Marcus (of Phoenix Contact, Germany), wmills Current Status: https://wiki.yoctoproject.org/wiki/Weekly_Status Spectre / Meltdown Info: http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146441.html Automated Hardware Testing Stay up to date on the Automated-testing list: https://lists.yoctoproject.org/listinfo/automated-testing Also, for an in depth look at automated hardware testing check out Tim Orling's ELC talk coming up in March at ELC: http://sched.co/DXnc -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Reminder: Yocto Project Technical Team Meeting
YPTM will be Feb. 6, 2018 at 8am PST. We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html https://www.yoctoproject.org/tools-resources/community/weekly-technical-call Conference Details: Company: WIND RIVER SYS - dial into: 1-800-262-0778/404-397-1527 - enter the bridge number: 88748961# The international numbers are: United States Toll 404-397-1527 US & Canada Toll Free 800-262-0778 Albania dial 00810+ 8558142509 Angola dial 80811+ 8558142510 Anguilla Toll Free 18003004779 Argentina Toll +541159844583 Argentina Toll Free 08004446354 Australia Toll +610386580431 Australia Toll Free 1800347095 Austria Toll Free 080088668498 Bahamas Toll Free 18003890740 Bahrain Toll Free 80006770 Bangladesh dial 1570011+8558142505 Barbados Toll Free 18002070056 Belarus Toll Free 882000110813 Belgium Toll+3227925498 Belgium Toll Free 080029896 Belize Toll Free18000130907 Bermuda Toll free 18002072792 Botswana Toll Free 002698003004981 Brazil Toll +5501149497489 Brazil Toll Free08008919885 British Virgin Islands Toll Free18002075710 Brunei Toll Free8014373 Bulgaria Toll +359024916371 Bulgaria Toll Free 008001201170 Cambodia Toll Free 1800209578 Cambodia Toll Free 1800209361 Canada Toll +14169810101 Cayman islands Toll Free18444305771 Chile Toll +56442080836 Chile Toll Free 12300206143 China Toll Free 4000342070 China Toll Free 8008709853 China Toll Free 4008877140 China Toll Free 8008768605 Colombia Toll +5714864720 Colombia Toll Free 18000129671 Costa Rica Toll 40017415 Croatia Toll+38517776838 Croatia Toll Free 08009975 Cuba dial 2935+ 8558142540 Cyprus Toll Free80096877 Czech Republic Toll Free0800701476 Denmark Toll+4536927940 Denmark Toll Free 80251209 Dominica Toll Free 18003004904 Dominican Republic Toll Free18887514588 Ecuador Toll Free 180314 Egypt Toll Free 0809493 Estonia Toll+3726867092 Estonia Toll Free 8000100708 Finland Toll+3580923195770 Finland Toll Free 0800774585 France Toll +33272249926 France Toll Free0800947235 French Guiana Toll Free 0800910113 Germany Toll+4930700150733 Germany Toll Free 08007238960 Ghana dial 0242426004+ 8553944954 Greece Toll +302111983414 Greece Toll Free0080016122059757 Grenada Toll Free 18003004905 Guatemala dial 001190+ 8553944634 Honduras Toll Free 80027919493 Hong Kong Toll +85230507540 Hong Kong Toll Free 800961673 Hungary Toll+40017789124 Hungary Toll Free 0680015494 India Toll +914466747384 India Toll Free 18002090252 Indonesia Toll Free 0078030114912 Ireland Toll+35316539376 Ireland Toll Free 1800948436 Israel Toll +97233762260 Israel Toll Free1809458778 Italy Toll +390200617793 Italy Toll Free 0800187234 Jamaica Toll Free 18002196874 Japan Toll +810345786573 Japan Toll Free 0120525303 Jordan Toll Free080022545 Kenya Toll Free 0800723004 Latvia Toll Free8002601 Lebanon dial 01426801+ 8558142511 Lithuania Toll +37052054804 Lithuania Toll Free 880031895 Luxembourg Toll +35228264835 Luxembourg Toll Free80023986 Macedonia Toll Free 080094382 Malaysia Toll +600377248228 Malta Toll +35627781438 Malta Toll Free 80062568 Martinique Toll Free0800910664 Mauritius Toll Free 8020440157 Mexico Toll +52015515001053 Mexico Toll Free018002530547 Moldavia Toll Free 080062305 Monaco Toll Free80094215 Morocco dial 002110011+ 8558142537 Netherlands Toll+310107994621 Netherlands Toll Free 08000200244 New Zealand Toll+64042806288 New Zealand Toll Free 0800441743 Norway Toll +4721034359 Norway Toll Free80058604 Oman Toll Free 80074218 Pakistan Toll +924238108753 Panama Toll +5078323301 Panama Toll Free008002267987 Paraguay Toll Free 009800110233 Peru Toll +51017017728 Peru Toll Free 080078493 Philippines Toll+6322312145 Philippines Toll Free 180011101073 Poland Toll +480223060270 Poland Toll Free800080328 Portugal Toll +351707201563 Portugal Toll Free 800788629 Qatar Toll Free 00800100142 Romania Toll+40215291752 Romania Toll Free 0800400068 Russia Toll +74993504823 Russia Toll Free81080026895011 Saudi Arabia Toll Free 8008442574 Saudi Arabia Toll Free 8008500370 Senegal dial 800103072+ 8558842521 Serbia Toll Free0800190975 Singapore Toll +6563494173 Singapore Toll Free 18005792882 Slovakia Toll +4210268622038 Slovakia Toll Free 0800606692 Slovenia Toll +38618281644 Slovenia Toll Free 080081438 South Africa Toll +
Re: [yocto] Yocto Project Technical Team Meeting
On 2/2/18 11:04 AM, Cetola, Stephano wrote: > Cetola, Stephano has invited you to Yocto Project Technical Team Meeting > > When: > > Occurs the first Tuesday of every month effective 2/6/18 from 8:00 AM to > 8:30 AM. > > Organizer: > > Cetola, Stephano > > Description: > > When: Occurs every month on the first Tuesday of the month from 8:00 AM > to 8:30 AM effective 2/6/2018. (UTC-08:00) Pacific Time (US & Canada) It has been mentioned to me that there is some confusion on when this meeting occurs. I sent this invite using Outlook, which is a necessary evil here. The meeting is from 8:00 - 8:30 (UTC -08:00). I'm happy to send a new invite if enough people need one, but I want to minimize the noise here. Cheers, Stephano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH 4/4] buildset-config.meta-intel: add meta-tlk
Since layer version 5 of meta-intel, meta-tlk is now an external
layer rather than a sub-layer of meta-intel. This requires that we
add meta-tlk as a repo to all buildset-configs, and set the
autoinclude flag to False. Then we must check the layerdirs variable
to see if it contains meta-intel/meta-tlk, and add the appropriate
folder to the bblayers.conf depending on which layer version of
meta-intel we are building.
Also, some cleanup was done on the buildset configs to remove extra
white spaces or cleanup the formatting.
Signed-off-by: Stephano Cetola
---
buildset-config.meta-intel/intel-core2-32-lsb-rt.conf | 5 -
buildset-config.meta-intel/intel-core2-32-lsb.conf| 4
buildset-config.meta-intel/intel-core2-32-rt.conf | 5 -
buildset-config.meta-intel/intel-core2-32.conf| 4
buildset-config.meta-intel/intel-corei7-64-lsb-rt.conf| 4
buildset-config.meta-intel/intel-corei7-64-lsb.conf | 6 +-
buildset-config.meta-intel/intel-corei7-64-rt.conf| 4
buildset-config.meta-intel/intel-corei7-64.conf | 6 +-
buildset-config.meta-intel/intel-quark.conf | 4
buildset-config.meta-intel/nightly-meta-intel-world.conf | 4
buildset-config.meta-intel/nightly-meta-intel.conf| 15 +--
buildset-config.meta-intel/nightly-musl-core2-32.conf | 4
buildset-config.meta-intel/nightly-musl.conf | 4
buildset-config.meta-intel/nightly-x32.conf | 4
buildset-config.meta-intel/yoctoAB.conf | 7 ---
.../autobuilder/buildsteps/CreateBBLayersConf.py | 6 +-
16 files changed, 72 insertions(+), 14 deletions(-)
diff --git a/buildset-config.meta-intel/intel-core2-32-lsb-rt.conf
b/buildset-config.meta-intel/intel-core2-32-lsb-rt.conf
index a31d624ec..cbcb99b4a 100644
--- a/buildset-config.meta-intel/intel-core2-32-lsb-rt.conf
+++ b/buildset-config.meta-intel/intel-core2-32-lsb-rt.conf
@@ -10,6 +10,10 @@ repos: [{'poky':
{'meta-qt4':
{'repourl':'git://git.yoctoproject.org/meta-qt4',
'branch':'master'}},
+{'meta-tlk':
+{'repourl':'git://git.yoctoproject.org/meta-tlk',
+ 'autoinclude': False,
+ 'branch':'master'}},
{'meta-intel':
{'repourl':'git://git.yoctoproject.org/meta-intel',
'layerversion':{'intel':'meta-intel'},
@@ -61,4 +65,3 @@ steps: [{'SetDest':{}},
{'BuildImages': {'images': 'core-image-rt'}},
{'PublishLayerTarballs':{}},
{'PublishArtifacts': {'artifacts': ['conf', 'intel-core2-32']}}]
-
diff --git a/buildset-config.meta-intel/intel-core2-32-lsb.conf
b/buildset-config.meta-intel/intel-core2-32-lsb.conf
index 1aba39718..ccf1e6b8d 100644
--- a/buildset-config.meta-intel/intel-core2-32-lsb.conf
+++ b/buildset-config.meta-intel/intel-core2-32-lsb.conf
@@ -10,6 +10,10 @@ repos: [{'poky':
{'meta-qt4':
{'repourl':'git://git.yoctoproject.org/meta-qt4',
'branch':'master'}},
+{'meta-tlk':
+{'repourl':'git://git.yoctoproject.org/meta-tlk',
+ 'autoinclude': False,
+ 'branch':'master'}},
{'meta-intel':
{'repourl':'git://git.yoctoproject.org/meta-intel',
'layerversion':{'intel':'meta-intel'},
diff --git a/buildset-config.meta-intel/intel-core2-32-rt.conf
b/buildset-config.meta-intel/intel-core2-32-rt.conf
index df04d980d..b591e754f 100644
--- a/buildset-config.meta-intel/intel-core2-32-rt.conf
+++ b/buildset-config.meta-intel/intel-core2-32-rt.conf
@@ -4,6 +4,10 @@ repos: [{'poky':
{'repourl':'git://git.yoctoproject.org/poky',
'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp',
'yocto':'meta-yocto', 'poky':'meta-poky'},
'branch':'master'}},
+{'meta-tlk':
+{'repourl':'git://git.yoctoproject.org/meta-tlk',
+ 'autoinclude': False,
+ 'branch':'master'}},
{'meta-intel':
{'repourl':'git://git.yoctoproject.org/meta-intel',
'layerversion':{'intel':'meta-intel'},
@@ -54,4 +58,3 @@ steps: [{'SetDest':{}},
{'Bu
[yocto] [yocto-autobuilder][PATCH 1/4] buildset-config.meta-intel: add oe-selftest buildsets
These buildset configs add RunOeSelftest steps for x86, x86-64,
corei7 core2-32 and qemux86-64.
Signed-off-by: Stephano Cetola
---
.../nightly-oe-selftest-core2-32.conf | 31 ++
.../nightly-oe-selftest-corei7.conf| 31 ++
.../nightly-oe-selftest-x86-64.conf| 31 ++
.../nightly-oe-selftest-x86.conf | 31 ++
.../nightly-oe-selftest.conf | 30 +
5 files changed, 154 insertions(+)
create mode 100644 buildset-config.meta-intel/nightly-oe-selftest-core2-32.conf
create mode 100644 buildset-config.meta-intel/nightly-oe-selftest-corei7.conf
create mode 100644 buildset-config.meta-intel/nightly-oe-selftest-x86-64.conf
create mode 100644 buildset-config.meta-intel/nightly-oe-selftest-x86.conf
create mode 100644 buildset-config.meta-intel/nightly-oe-selftest.conf
diff --git a/buildset-config.meta-intel/nightly-oe-selftest-core2-32.conf
b/buildset-config.meta-intel/nightly-oe-selftest-core2-32.conf
new file mode 100644
index 0..e174e82e8
--- /dev/null
+++ b/buildset-config.meta-intel/nightly-oe-selftest-core2-32.conf
@@ -0,0 +1,31 @@
+[nightly-oe-selftest-core2-32]
+builders: 'example-worker'
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp',
'yocto':'meta-yocto', 'poky':'meta-poky'},
+ 'branch':'master'}},
+{'meta-tlk':
+{'repourl':'git://git.yoctoproject.org/meta-tlk',
+ 'autoinclude': False,
+ 'branch':'master'}},
+{'meta-intel':
+{'repourl':'git://git.yoctoproject.org/meta-intel',
+ 'layerversion':{'intel':'meta-intel'},
+ 'branch':'master'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'intel-core2-32', 'SDKMACHINE' : 'i686',
+'distro': 'poky', 'nosstate': True,
+'packages': 'rpm', 'buildhistory' : False,
+'prserv': False}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto',
+'bsplayer': True, 'bspprovider': 'intel',
+'packages': 'rpm', 'buildhistory' : False,
+'prserv': False}},
+{'BuildImages': {'images': 'core-image-minimal'}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto', 'layerdirs':
['meta-selftest']}},
+{'RunOeSelftest': {}},
+{'DownloadErrorReports': {}},
+{'SendErrorReport': {}}]
diff --git a/buildset-config.meta-intel/nightly-oe-selftest-corei7.conf
b/buildset-config.meta-intel/nightly-oe-selftest-corei7.conf
new file mode 100644
index 0..e2e71272c
--- /dev/null
+++ b/buildset-config.meta-intel/nightly-oe-selftest-corei7.conf
@@ -0,0 +1,31 @@
+[nightly-oe-selftest-corei7]
+builders: 'example-worker'
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp',
'yocto':'meta-yocto', 'poky':'meta-poky'},
+ 'branch':'master'}},
+{'meta-tlk':
+{'repourl':'git://git.yoctoproject.org/meta-tlk',
+ 'autoinclude': False,
+ 'branch':'master'}},
+{'meta-intel':
+{'repourl':'git://git.yoctoproject.org/meta-intel',
+ 'layerversion':{'intel':'meta-intel'},
+ 'branch':'master'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'intel-corei7-64', 'SDKMACHINE' :
'i686',
+
[yocto] [yocto-autobuilder][PATCH 3/4] buildset-config.meta-intel/nightly-meta-intel.conf: add rocko
Yocto v2.4 is live and the codename is rocko. This adds that name to
the list of possible releases.
Signed-off-by: Stephano Cetola
---
buildset-config.meta-intel/nightly-meta-intel.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/buildset-config.meta-intel/nightly-meta-intel.conf
b/buildset-config.meta-intel/nightly-meta-intel.conf
index ae14c6966..791053fc6 100644
--- a/buildset-config.meta-intel/nightly-meta-intel.conf
+++ b/buildset-config.meta-intel/nightly-meta-intel.conf
@@ -19,7 +19,7 @@ props: [{'release_me':{'prop_type':'ChoiceStringParameter',
'name': 'release_me',
'label':' Generate a release?:'}},
{'poky_name':{'prop_type':'ChoiceStringParameter',
- 'choices': ['', 'pyro', 'morty', 'krogoth', 'jethro',
'fido'],
+ 'choices': ['', 'rocko', 'pyro', 'morty', 'krogoth',
'jethro', 'fido'],
'name': 'poky_name',
'label':' Name of the poky release.For further
info on release names see https://wiki.yoctoproject.org/wiki/Releases";> Releases '}},
{'is_milestone':{'prop_type':'ChoiceStringParameter',
--
2.14.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH 2/4] intel-quark.conf: change the defaults for srcrev_meta and srcrev_machine
The default values for srcrev_machine and srcrev_meta should be set
to blank rather than AUTOREV. AUTOREV will force them to the tip of
the current branch, which is no longer needed.
Signed-off-by: Stephano Cetola
---
buildset-config.meta-intel/intel-quark.conf | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/buildset-config.meta-intel/intel-quark.conf
b/buildset-config.meta-intel/intel-quark.conf
index 931ead0e2..136c2257d 100644
--- a/buildset-config.meta-intel/intel-quark.conf
+++ b/buildset-config.meta-intel/intel-quark.conf
@@ -16,8 +16,8 @@ props: [{'kmeta':{'prop_type':'StringParameter',
{'srcrev_meta':{'prop_type':'StringParameter',
'size': 15,
'name': 'srcrev_meta',
- 'default': '${AUTOREV}',
- 'label':' SRCREV for KMETA_${MACHINE} (default
is ${AUTOREV}):'}},
+ 'default': '',
+ 'label':' SRCREV for KMETA_${MACHINE} (default
is blank):'}},
{'srcuri_meta':{'prop_type':'StringParameter',
'size': 50,
'name': 'srcuri_meta',
@@ -31,8 +31,8 @@ props: [{'kmeta':{'prop_type':'StringParameter',
{'srcrev_machine':{'prop_type':'StringParameter',
'size': 15,
'name': 'srcrev_machine',
- 'default': '${AUTOREV}',
- 'label':' SRCREV for KBRANCH. (default is
${AUTOREV}):'}},
+ 'default': '',
+ 'label':' SRCREV for KBRANCH. (default is
blank):'}},
{'srcuri_machine':{'prop_type':'StringParameter',
'size': 50,
'name': 'srcuri_machine',
--
2.14.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH 0/4] update meta-intel ab
There were a few changes that were not committed on the meta-intel autobuilder, specifically in the buildset configs. These patches get us back up to date with those changes. There is also an update to meta-tlk which should not effect the yocto autobuilder. Since we now have meta-tlk as a separate layer from meta-intel, we need to add that layer's location based on meta-intel's layer version. Stephano Cetola (4): buildset-config.meta-intel: add oe-selftest buildsets intel-quark.conf: change the defaults for srcrev_meta and srcrev_machine buildset-config.meta-intel/nightly-meta-intel.conf: add rocko buildset-config.meta-intel: add meta-tlk .../intel-core2-32-lsb-rt.conf | 5 +++- buildset-config.meta-intel/intel-core2-32-lsb.conf | 4 +++ buildset-config.meta-intel/intel-core2-32-rt.conf | 5 +++- buildset-config.meta-intel/intel-core2-32.conf | 4 +++ .../intel-corei7-64-lsb-rt.conf| 4 +++ .../intel-corei7-64-lsb.conf | 6 - buildset-config.meta-intel/intel-corei7-64-rt.conf | 4 +++ buildset-config.meta-intel/intel-corei7-64.conf| 6 - buildset-config.meta-intel/intel-quark.conf| 12 ++--- .../nightly-meta-intel-world.conf | 4 +++ buildset-config.meta-intel/nightly-meta-intel.conf | 17 +++- .../nightly-musl-core2-32.conf | 4 +++ buildset-config.meta-intel/nightly-musl.conf | 4 +++ .../nightly-oe-selftest-core2-32.conf | 31 ++ .../nightly-oe-selftest-corei7.conf| 31 ++ .../nightly-oe-selftest-x86-64.conf| 31 ++ .../nightly-oe-selftest-x86.conf | 31 ++ .../nightly-oe-selftest.conf | 30 + buildset-config.meta-intel/nightly-x32.conf| 4 +++ buildset-config.meta-intel/yoctoAB.conf| 7 ++--- .../autobuilder/buildsteps/CreateBBLayersConf.py | 6 - 21 files changed, 231 insertions(+), 19 deletions(-) create mode 100644 buildset-config.meta-intel/nightly-oe-selftest-core2-32.conf create mode 100644 buildset-config.meta-intel/nightly-oe-selftest-corei7.conf create mode 100644 buildset-config.meta-intel/nightly-oe-selftest-x86-64.conf create mode 100644 buildset-config.meta-intel/nightly-oe-selftest-x86.conf create mode 100644 buildset-config.meta-intel/nightly-oe-selftest.conf -- 2.14.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH 2/2] meta-intel: nightly-musl: add 32 bit buildset
On the meta-intel autobuilder, we were only building musl for 64bit
architectures. This adds a buildset for core2-32 arch, and adds that
build to the nightly.
Signed-off-by: Stephano Cetola
---
buildset-config.meta-intel/nightly-meta-intel.conf | 3 +-
.../nightly-musl-core2-32.conf | 53 ++
2 files changed, 55 insertions(+), 1 deletion(-)
create mode 100644 buildset-config.meta-intel/nightly-musl-core2-32.conf
diff --git a/buildset-config.meta-intel/nightly-meta-intel.conf
b/buildset-config.meta-intel/nightly-meta-intel.conf
index 012f71f97..ae14c6966 100644
--- a/buildset-config.meta-intel/nightly-meta-intel.conf
+++ b/buildset-config.meta-intel/nightly-meta-intel.conf
@@ -95,7 +95,8 @@ steps: [{'SetDest':{}},
'intel-core2-32-lsb-rt':{},
'intel-core2-32-rt':{},
'intel-corei7-64':{}, 'intel-corei7-64-lsb':{},
'intel-corei7-64-lsb-rt':{},
'intel-corei7-64-rt':{},
- 'intel-quark':{}, 'nightly-musl':{},
'nightly-x32':{},
+ 'intel-quark':{}, 'nightly-musl':{},
+ 'nightly-musl-core2-32':{}, 'nightly-x32':{}},
'schedulerNames_nowait' :
{'nightly-meta-intel-world':{,
{'CreateIntelBSPPackage': {'machine': 'intel-core2-32'}},
{'CreateIntelBSPPackage': {'machine': 'intel-corei7-64'}},
diff --git a/buildset-config.meta-intel/nightly-musl-core2-32.conf
b/buildset-config.meta-intel/nightly-musl-core2-32.conf
new file mode 100644
index 0..0b952a7fe
--- /dev/null
+++ b/buildset-config.meta-intel/nightly-musl-core2-32.conf
@@ -0,0 +1,53 @@
+[nightly-musl-core2-32]
+builders: ['yocto-ab-master.ostc.intel.com', 'yocto-ab01.ostc.intel.com',
'yocto-ab02.ostc.intel.com', 'yocto-ab03.ostc.intel.com',
'yocto-ab04.ostc.intel.com']
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp',
'yocto':'meta-yocto', 'poky':'meta-poky'},
+ 'branch':'master'}},
+{'meta-intel':
+{'repourl':'git://git.yoctoproject.org/meta-intel',
+ 'layerversion':{'intel':'meta-intel'},
+ 'branch':'master'}}]
+props: [{'kmeta':{'prop_type':'StringParameter',
+ 'size': 15,
+ 'name': 'kmeta',
+ 'default': '',
+ 'label':' branch for KMETA_${MACHINE} (default
is blank):'}},
+{'srcrev_meta':{'prop_type':'StringParameter',
+ 'size': 15,
+ 'name': 'srcrev_meta',
+ 'default': '',
+ 'label':' SRCREV for KMETA_${MACHINE} (default
is blank):'}},
+{'srcuri_meta':{'prop_type':'StringParameter',
+ 'size': 50,
+ 'name': 'srcuri_meta',
+ 'default': '',
+ 'label':' SRC_URI_pn-linux-yocto KMETA append.
(default is blank). This should be constructed as *just* the git uri
portion of the string.
(git://git.yoctoproject.org/linux-yocto-3.19.git'}},
+{'kbranch':{'prop_type':'StringParameter',
+ 'size': 15,
+ 'name': 'kbranch',
+ 'default': '',
+ 'label':' branch for KBRANCH_${MACHINE}
(default is blank):'}},
+{'srcrev_machine':{'prop_type':'StringParameter',
+ 'size': 15,
+ 'name': 'srcrev_machine',
+ 'default': '',
+ 'label':' SRCREV for KBRANCH. (default is
blank):'}},
+{'srcuri_machine':{'prop_type':'StringParameter',
+ 'size': 50,
+ 'name': 'srcuri_mac
[yocto] [yocto-autobuilder][PATCH 1/2] nightly-musl-x86-64: add 64bit musl build
We were building with musl on 32 bit platforms but not on 64 bit.
This adds a 64 bit musl buildset that is similar to the 32 bit one
and also adds that buildset to the list of builds for nightly.
Signed-off-by: Stephano Cetola
---
buildset-config.controller/nightly-musl-x86-64.conf | 18 ++
buildset-config.controller/nightly.conf | 1 +
2 files changed, 19 insertions(+)
create mode 100644 buildset-config.controller/nightly-musl-x86-64.conf
diff --git a/buildset-config.controller/nightly-musl-x86-64.conf
b/buildset-config.controller/nightly-musl-x86-64.conf
new file mode 100644
index 0..e9c3f
--- /dev/null
+++ b/buildset-config.controller/nightly-musl-x86-64.conf
@@ -0,0 +1,18 @@
+[nightly-musl-x86-64]
+builders: ['centos7.yocto.io', 'debian8.yocto.io', 'fedora25.yocto.io',
'fedora26.yocto.io', 'tumbleweed.yocto.io', 'opensuse423.yocto.io',
'ubuntu1604.yocto.io', 'ubuntu1704.yocto.io', 'debian9.yocto.io']
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp',
'yocto':'meta-yocto', 'poky':'meta-poky'},
+ 'branch':'master'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'x86_64',
+'buildhistory' : False, 'distro': 'poky',
+'atextappend' : '\nTCLIBC="musl"\n' }},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'BuildImages': {'images': 'core-image-minimal
core-image-full-cmdline core-image-sato-sdk world'}},
+{'RunSanityTests': {'images': 'core-image-minimal
core-image-full-cmdline core-image-sato-sdk'}},
+{'DownloadErrorReports': {}},
+{'SendErrorReport': {}}]
diff --git a/buildset-config.controller/nightly.conf
b/buildset-config.controller/nightly.conf
index dde6c535f..51ddf6e5b 100644
--- a/buildset-config.controller/nightly.conf
+++ b/buildset-config.controller/nightly.conf
@@ -121,6 +121,7 @@ steps: [{'SetDest':{}},
'nightly-world-lsb':{},
'poky-tiny': {}, 'buildtools': {},
'nightly-musl': {}, 'nightly-no-x11': {},
+ 'nightly-musl-x86-64': {},
'nightly-qa-extras': {}, 'nightly-oe-selftest': {},
'nightly-refkit': {,
{'PrepPkgIndex' : {}},
--
2.14.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH 0/2] add musl buildsets
These patches add musl buildsets for 64 bit on the main autobuilders and 32 bit on the meta-intel autobuilder. Stephano Cetola (2): nightly-musl-x86-64: add 64bit musl build meta-intel: nightly-musl: add 32 bit buildset .../nightly-musl-x86-64.conf | 18 buildset-config.controller/nightly.conf| 1 + buildset-config.meta-intel/nightly-meta-intel.conf | 3 +- .../nightly-musl-core2-32.conf | 53 ++ 4 files changed, 74 insertions(+), 1 deletion(-) create mode 100644 buildset-config.controller/nightly-musl-x86-64.conf create mode 100644 buildset-config.meta-intel/nightly-musl-core2-32.conf -- 2.14.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] meta-intel: add CheckYoctoCompat to nightly
Rocko introduces yocto-check-layer-wrapper which creates a separate
build dir to run yocto-check-layer inside.
Signed-off-by: Stephano Cetola
---
buildset-config.meta-intel/nightly-meta-intel.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/buildset-config.meta-intel/nightly-meta-intel.conf
b/buildset-config.meta-intel/nightly-meta-intel.conf
index ae14c6966..dc6548948 100644
--- a/buildset-config.meta-intel/nightly-meta-intel.conf
+++ b/buildset-config.meta-intel/nightly-meta-intel.conf
@@ -89,6 +89,7 @@ props: [{'release_me':{'prop_type':'ChoiceStringParameter',
steps: [{'SetDest':{}},
{'CheckOutLayers': {}},
{'RunPreamble': {}},
+{'CheckYoctoCompat': {'layers': ['meta-intel']}},
{'TriggerBuilds': {'copy_properties': ['custom_deploy_artifacts',
'custom_prefered_kernel', 'custom_kmeta', 'custom_kbranch',
'custom_srcrev_meta', 'custom_srcrev_machine', 'custom_srcuri_meta',
'custom_srcuri_machine'],
'schedulerName': 'main-build', 'waitForFinish':
'True',
'schedulerNames': {'intel-core2-32':{},
'intel-core2-32-lsb':{},
--
2.14.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] CheckYoctoCompat.py: rename yocto-compat-layer to yocto-check-layer
This script name was changed in the following commit:
b46e05677b342df44829ffe8bcfbfc954e906030
This patch updates the script name to match.
[YOCTO #12110]
Signed-off-by: Stephano Cetola
---
lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py
index 134adaa51..62eddae50 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py
@@ -41,11 +41,12 @@ class CheckYoctoCompat(BitbakeShellCommand):
layerversioncore = int(self.getProperty("layerversion_core", "0"))
# yocto-compat-layer-wrapper was introduced in Pyro
+# it was renamed to yocto-check-layer-wrapper Rocko
if layerversioncore >= 10:
command = ". ./oe-init-build-env;"
for layer in self.layers:
layerpath = os.path.join(builddir, layer)
-cmd = "yocto-compat-layer-wrapper {}".format(layerpath)
+cmd = "yocto-check-layer-wrapper {}".format(layerpath)
cmd = cmd + " || export CL_FAIL=1;"
command = command + cmd
command = command + 'if [ "$CL_FAIL" = "1" ]; then exit 1; fi;'
--
2.14.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] buildset-config.controller/nightly-refkit.conf: add poky distro build
In order to test the meta-refkit-core layer we need to remove any
layers not required to build refkit-image-minimal and set the distro
equal to something other than refkit. We also do not want to use the
refkit templateconf. Here, we remove the config files from the
previous build and regenerate them with distro = poky, calling
oe-init inside poky rather than inside refkit. The only layers we
need to add for refkit are "core" and "meta-intel".
Signed-off-by: Stephano Cetola
---
buildset-config.controller/nightly-refkit.conf | 11 +++
1 file changed, 11 insertions(+)
diff --git a/buildset-config.controller/nightly-refkit.conf
b/buildset-config.controller/nightly-refkit.conf
index 5fdfe4fc7..187c1b117 100644
--- a/buildset-config.controller/nightly-refkit.conf
+++ b/buildset-config.controller/nightly-refkit.conf
@@ -29,6 +29,17 @@ steps: [{'SetDest':{}},
{'ScrapeTargets': {'source':
'refkit/meta-refkit/conf/distro/include/refkit-ci.inc',
'targetsvar': 'REFKIT_CI_POSTBUILD_SELFTESTS'}},
{'RunOeSelftest': {'tests': '#SCRAPEDTARGETS'}},
+{'RemoveTmpFiles': {'files': 'build/conf'}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'intel-corei7-64', 'packages': 'ipk',
+'distro': 'poky', 'buildhistory' : False,
+'prserv': False, 'nosstate': True,
+'SDKMACHINE' : 'x86_64'}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto',
+'layerdirs': ['refkit/meta-intel',
+'refkit/meta-refkit-core']}},
+{'BuildImages': {'images': 'refkit-image-minimal'}},
{'DownloadErrorReports': {}},
{'SendErrorReport': {}}
]
--
2.13.3
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] buildset-config.controller/nightly-refkit.conf: add nodistro build
Here we set DISTRO = "" to test building without setting refkit as
the distro. This requires that we set REFKIT_IMAGE_MODE = "" as well,
since refkit-image-minimal does not define any IMAGE_MODES. This is
normally used to enable features like auto-login or setting public /
private keys.
Signed-off-by: Stephano Cetola
---
buildset-config.controller/nightly-refkit.conf | 11 +++
1 file changed, 11 insertions(+)
diff --git a/buildset-config.controller/nightly-refkit.conf
b/buildset-config.controller/nightly-refkit.conf
index 5fdfe4fc7..133eb54fd 100644
--- a/buildset-config.controller/nightly-refkit.conf
+++ b/buildset-config.controller/nightly-refkit.conf
@@ -29,6 +29,17 @@ steps: [{'SetDest':{}},
{'ScrapeTargets': {'source':
'refkit/meta-refkit/conf/distro/include/refkit-ci.inc',
'targetsvar': 'REFKIT_CI_POSTBUILD_SELFTESTS'}},
{'RunOeSelftest': {'tests': '#SCRAPEDTARGETS'}},
+{'CreateAutoConf': {'machine': 'intel-corei7-64', 'packages': 'ipk',
+'distro': '', 'buildhistory' : False,
+'prserv': False, 'nosstate': True,
+'SDKMACHINE' : 'x86_64',
+'atextappend': '\nREFKIT_IMAGE_MODE = ""\nrequire
conf/distro/include/refkit-ci.inc\n'}},
+{'ModBBLayersConf': {'sub': [['openembedded-core/meta', '#YPDIR/meta'],
+['openembedded-core/meta-selftest',
+'#YPDIR/meta-selftest']]}},
+{'BuildImages': {'images': 'refkit-image-minimal',
+ 'oeinit': 'refkit/oe-init-build-env',
+ 'overrideenv': ['BITBAKEDIR=#YPDIR/bitbake',
'OEROOT=#YPDIR/meta']}},
{'DownloadErrorReports': {}},
{'SendErrorReport': {}}
]
--
2.13.3
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH V2] buildset-config/nightly-refkit: add modify bblayers step
Add the new modification step, and remove the second buildimages
test. The second buildimages test aims to change the distro to
"nodistro" and rerun the build. In order to do that we'll need to add
some functionality. For now, we will simply do one buildimage step
until the second step has been flushed out.
Signed-off-by: Stephano Cetola
---
buildset-config.controller/nightly-refkit.conf | 56 ++
1 file changed, 3 insertions(+), 53 deletions(-)
diff --git a/buildset-config.controller/nightly-refkit.conf
b/buildset-config.controller/nightly-refkit.conf
index 1d2487da6..5fdfe4fc7 100644
--- a/buildset-config.controller/nightly-refkit.conf
+++ b/buildset-config.controller/nightly-refkit.conf
@@ -18,29 +18,9 @@ steps: [{'SetDest':{}},
'prserv': False, 'nosstate': True,
'SDKMACHINE' : 'x86_64',
'atextappend': '\nrequire
conf/distro/include/refkit-ci.inc\n'}},
-{'CreateBBLayersConf': {'buildprovider' : 'oe',
-'layerdirs': ['refkit/meta-intel',
- 'refkit/meta-refkit',
- 'meta-selftest',
- 'refkit/meta-refkit-gateway',
-
'refkit/meta-refkit-computervision',
- 'refkit/meta-oic',
- 'refkit/meta-iot-web',
- 'refkit/meta-iotqa',
- 'refkit/meta-security',
- 'refkit/meta-security-isafw',
- 'refkit/meta-intel-realsense',
- 'refkit/meta-clang',
- 'refkit/meta-flatpak',
- 'refkit/meta-refkit-industrial',
- 'refkit/meta-ros',
-
'refkit/meta-openembedded/meta-filesystems',
-
'refkit/meta-openembedded/meta-gnome',
-
'refkit/meta-openembedded/meta-networking',
-
'refkit/meta-openembedded/meta-oe',
-
'refkit/meta-openembedded/meta-perl',
-
'refkit/meta-openembedded/meta-python',
- 'refkit/meta-refkit-core']}},
+{'ModBBLayersConf': {'sub': [['openembedded-core/meta', '#YPDIR/meta'],
+['openembedded-core/meta-selftest',
+'#YPDIR/meta-selftest']]}},
{'ScrapeTargets': {'source':
'refkit/meta-refkit/conf/distro/include/refkit-ci.inc',
'targetsvar': 'REFKIT_CI_BUILD_TARGETS'}},
{'BuildImages': {'images': '#SCRAPEDTARGETS',
@@ -49,36 +29,6 @@ steps: [{'SetDest':{}},
{'ScrapeTargets': {'source':
'refkit/meta-refkit/conf/distro/include/refkit-ci.inc',
'targetsvar': 'REFKIT_CI_POSTBUILD_SELFTESTS'}},
{'RunOeSelftest': {'tests': '#SCRAPEDTARGETS'}},
-{'RemoveTmpFiles': {'files': 'build/conf'}},
-{'RunPreamble': {}},
-{'CreateAutoConf': {'machine': 'qemux86-64', 'packages': 'ipk',
-'distro': 'poky', 'buildhistory' : False,
-'prserv': False, 'nosstate': True,
-'SDKMACHINE' : 'x86_64', 'tmpdir': 'tmp-poky'}},
-{'CreateBBLayersConf': {'buildprovider' : 'yocto',
-'layerdirs': ['refkit/meta-intel',
- 'meta-selftest',
- 'refkit/meta-refkit',
- 'refkit/meta-refkit-gateway',
-
[yocto] [yocto-autobuilder][PATCH V2] buildsteps: add bblayers modification step
Take a list of pairs of layer substitutions: (current, replacement)
and replace each entry's current layer with the replacement layer.
The replacement parameter may include #YPDIR which will be
substituted for the full path of the poky checkout.
[YOCTO #11745 ]
Signed-off-by: Stephano Cetola
---
.../autobuilder/buildsteps/ModBBLayersConf.py | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
lib/python2.7/site-packages/autobuilder/buildsteps/ModBBLayersConf.py
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/ModBBLayersConf.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/ModBBLayersConf.py
new file mode 100644
index 0..5e9a7f22b
--- /dev/null
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ModBBLayersConf.py
@@ -0,0 +1,40 @@
+'''
+Created on July 24, 2017
+
+__author__ = "Stephano Cetola"
+__copyright__ = "Copyright 2017, Intel Corp."
+__credits__ = ["Stephano Cetola"]
+__license__ = "GPL"
+__version__ = "2.0"
+__maintainer__ = "Stephano Cetola"
+__email__ = "stephano.cet...@linux.intel.com"
+'''
+
+from buildbot.steps.shell import ShellCommand
+from twisted.python import log
+import os
+
+class ModBBLayersConf(ShellCommand):
+haltOnFailure = True
+flunkOnFailure = True
+name = "Modify BBLayers Configuration"
+def __init__(self, factory, argdict=None, **kwargs):
+self.factory = factory
+for k, v in argdict.iteritems():
+setattr(self, k, v)
+self.description = "Modify BBLayers Configuration"
+ShellCommand.__init__(self, **kwargs)
+
+def start(self):
+builddir = os.path.join(self.getProperty('builddir'), 'build')
+bblayers = "%s/build/conf/bblayers.conf" % builddir
+cmd = 'echo "Not configured"'
+if self.sub:
+cmd = ""
+for mod in self.sub:
+tgt, rep = mod
+rep = rep.replace("#YPDIR", builddir)
+cmd = cmd + "sed -i 's|.*%s .*|%s |' %s;" % (tgt, rep,
bblayers)
+
+self.command = cmd
+ShellCommand.start(self)
--
2.13.3
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] CreateBBLayersConf: remove meta-qt4 after layer version 10
Qt4 is EOL and is no longer being supported. This patch removes meta-qt4 from the build when the layer version is great than 10. See this commit for removal justifications: oecore c96aa431f2f56d023b84d28e049065eef2a7490f And this for the layer bump: oecore 179b7ae2511974173ae4aa72dfb49384ff69c2e5 Signed-off-by: Stephano Cetola --- .../site-packages/autobuilder/buildsteps/CreateBBLayersConf.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/python2.7/site-packages/autobuilder/buildsteps/CreateBBLayersConf.py b/lib/python2.7/site-packages/autobuilder/buildsteps/CreateBBLayersConf.py index 74871604c..593b9ee37 100644 --- a/lib/python2.7/site-packages/autobuilder/buildsteps/CreateBBLayersConf.py +++ b/lib/python2.7/site-packages/autobuilder/buildsteps/CreateBBLayersConf.py @@ -92,7 +92,7 @@ class CreateBBLayersConf(ShellCommand): if layerversioncore < 9: fout = fout + workdir + '/build/' + layer.iterkeys().next() + ' \ \n' elif layer.iterkeys().next()=="meta-qt4": -if layerversioncore > 6: +if layerversioncore > 6 and layerversioncore < 11: fout = fout + workdir + '/build/' + layer.iterkeys().next() + ' \ \n' elif layer.iterkeys().next()=="meta-gplv2": # We only want meta-gplv2 for pyro or newer -- 2.13.3 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] buildset-config/nightly-refkit: add modify bblayers step
Add the new modification step, and remove the second buildimages
test. The second buildimages test aims to change the distro to
"nodistro" and rerun the build. In order to do that we'll need to add
some functionality. For now, we will simply do one buildimage step
until the second step has been flushed out.
Signed-off-by: Stephano Cetola
---
buildset-config.controller/nightly-refkit.conf | 53 +-
1 file changed, 1 insertion(+), 52 deletions(-)
diff --git a/buildset-config.controller/nightly-refkit.conf
b/buildset-config.controller/nightly-refkit.conf
index 1d2487da6..eb120eded 100644
--- a/buildset-config.controller/nightly-refkit.conf
+++ b/buildset-config.controller/nightly-refkit.conf
@@ -18,29 +18,7 @@ steps: [{'SetDest':{}},
'prserv': False, 'nosstate': True,
'SDKMACHINE' : 'x86_64',
'atextappend': '\nrequire
conf/distro/include/refkit-ci.inc\n'}},
-{'CreateBBLayersConf': {'buildprovider' : 'oe',
-'layerdirs': ['refkit/meta-intel',
- 'refkit/meta-refkit',
- 'meta-selftest',
- 'refkit/meta-refkit-gateway',
-
'refkit/meta-refkit-computervision',
- 'refkit/meta-oic',
- 'refkit/meta-iot-web',
- 'refkit/meta-iotqa',
- 'refkit/meta-security',
- 'refkit/meta-security-isafw',
- 'refkit/meta-intel-realsense',
- 'refkit/meta-clang',
- 'refkit/meta-flatpak',
- 'refkit/meta-refkit-industrial',
- 'refkit/meta-ros',
-
'refkit/meta-openembedded/meta-filesystems',
-
'refkit/meta-openembedded/meta-gnome',
-
'refkit/meta-openembedded/meta-networking',
-
'refkit/meta-openembedded/meta-oe',
-
'refkit/meta-openembedded/meta-perl',
-
'refkit/meta-openembedded/meta-python',
- 'refkit/meta-refkit-core']}},
+{'ModBBLayersConf': {}},
{'ScrapeTargets': {'source':
'refkit/meta-refkit/conf/distro/include/refkit-ci.inc',
'targetsvar': 'REFKIT_CI_BUILD_TARGETS'}},
{'BuildImages': {'images': '#SCRAPEDTARGETS',
@@ -50,35 +28,6 @@ steps: [{'SetDest':{}},
'targetsvar': 'REFKIT_CI_POSTBUILD_SELFTESTS'}},
{'RunOeSelftest': {'tests': '#SCRAPEDTARGETS'}},
{'RemoveTmpFiles': {'files': 'build/conf'}},
-{'RunPreamble': {}},
-{'CreateAutoConf': {'machine': 'qemux86-64', 'packages': 'ipk',
-'distro': 'poky', 'buildhistory' : False,
-'prserv': False, 'nosstate': True,
-'SDKMACHINE' : 'x86_64', 'tmpdir': 'tmp-poky'}},
-{'CreateBBLayersConf': {'buildprovider' : 'yocto',
-'layerdirs': ['refkit/meta-intel',
- 'meta-selftest',
- 'refkit/meta-refkit',
- 'refkit/meta-refkit-gateway',
-
'refkit/meta-refkit-computervision',
- 'refkit/meta-oic',
- 'refkit/meta-iot-web',
- 'refkit/meta-iotqa',
-
[yocto] [yocto-autobuilder][PATCH] buildsteps: add bblayers modification step
This step is currently only applicable to refkit. It allows us to
replace oe-core and oe-selftest layers in their bblayers.conf with
those layers that we are currently testing.
In the future, we may be able to improve this to replace layer "x"
with layer "y" dynamically, however that presents several challenges
outside the scope of this work.
[YOCTO #11745 ]
Signed-off-by: Stephano Cetola
---
.../autobuilder/buildsteps/ModBBLayersConf.py | 35 ++
1 file changed, 35 insertions(+)
create mode 100644
lib/python2.7/site-packages/autobuilder/buildsteps/ModBBLayersConf.py
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/ModBBLayersConf.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/ModBBLayersConf.py
new file mode 100644
index 0..513e8a15a
--- /dev/null
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ModBBLayersConf.py
@@ -0,0 +1,35 @@
+'''
+Created on July 24, 2017
+
+__author__ = "Stephano Cetola"
+__copyright__ = "Copyright 2017, Intel Corp."
+__credits__ = ["Stephano Cetola"]
+__license__ = "GPL"
+__version__ = "2.0"
+__maintainer__ = "Stephano Cetola"
+__email__ = "stephano.cet...@linux.intel.com"
+'''
+
+from buildbot.steps.shell import ShellCommand
+from twisted.python import log
+
+class ModBBLayersConf(ShellCommand):
+haltOnFailure = True
+flunkOnFailure = True
+name = "Modify BBLayers Configuration"
+def __init__(self, factory, argdict=None, **kwargs):
+self.factory = factory
+for k, v in argdict.iteritems():
+setattr(self, k, v)
+self.description = "Modify BBLayers Configuration"
+ShellCommand.__init__(self, **kwargs)
+
+def start(self):
+workdir = self.getProperty("workdir")
+bblayers = "%s/build/build/conf/bblayers.conf" % workdir
+yoctodir = "%s/build/meta " % workdir
+selftestdir = "%s/build/meta-selftest " % workdir
+cmd1 = "sed -i 's|.*openembedded-core/meta .*|%s|' %s" % (yoctodir,
bblayers)
+cmd2 = "sed -i 's|.*openembedded-core/meta-selftest.*|%s|' %s" %
(selftestdir, bblayers)
+self.command = "%s;%s" % (cmd1, cmd2)
+ShellCommand.start(self)
--
2.13.3
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] ScrapeTargets: use translate instead of regex
>From some quick tests the string translate function is comparable in
efficiency and certainly more legible than regex. We should note that
if we ever move this functionality to an environment running python3,
the translate function takes one dictionary argument, but functions
in much the same way.
Signed-off-by: Stephano Cetola
---
.../site-packages/autobuilder/buildsteps/ScrapeTargets.py | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
index ceed0c709..0480f3de3 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
@@ -57,9 +57,10 @@ class ScrapeTargets(ShellCommand):
targets = res.group()
# Try and ensure we scrape the target regardless of which
# assignment operator is used and surrounding whitespace
-targets = re.sub('%s *\??\??:?.?\+?=\+?\.? *\"' % self.targetsvar,
'', targets, 1)
-targets = targets.replace('\\', '')
-targets = targets.replace('\n', '')
+targets = targets.replace(self.targetsvar, '')
+targets = targets.translate(None, ':+?="')
+targets = targets.replace("\\", "")
+targets = targets.replace ("\n", "")
self.setProperty("scraped_targets",
targets,
'Targets "%s" scraped from %s' % (targets,
--
2.13.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] yoctogit: add init to submodule update
We replaced buildbot's standard copy function with our _srccopy function when method=barecopy or movecopy. The srccopy will copy the contents of the "source" directory into the build dir. We cannot assume that submodules have not been added since the buildslave last populated the source dir. Adding --init to the git submodule update resolves this issue. Signed-off-by: Stephano Cetola --- .../buildbot-0.8.8-py2.7.egg/buildbot/steps/source/yoctogit.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/steps/source/yoctogit.py b/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/steps/source/yoctogit.py index 389cf4f8f..ecf4d1a34 100644 --- a/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/steps/source/yoctogit.py +++ b/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/buildbot/steps/source/yoctogit.py @@ -604,7 +604,7 @@ class YoctoGit(Source): def _updateSubmodule(self, _): if self.submodules: -return self._dovccmd(['submodule', 'update', '--recursive']) +return self._dovccmd(['submodule', 'update', '--init', '--recursive']) else: return defer.succeed(0) -- 2.13.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] ScrapeTargets.py: Use python instead of awk
Using awk, sed, or grep to pull a shell variable out of stdio proved
complex. Instead, simply cat the entire "inc" file to stdio and use
python/regex to find the variable.
Signed-off-by: Stephano Cetola
---
.../autobuilder/buildsteps/ScrapeTargets.py | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
index 07e2fdcf4..8844c6366 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
@@ -15,6 +15,7 @@ from buildbot.steps.shell import ShellCommand
from buildbot.status.results import SUCCESS, FAILURE
from autobuilder.config import *
import os
+import re
class ScrapeTargets(ShellCommand):
haltOnFailure = False
@@ -41,9 +42,7 @@ class ScrapeTargets(ShellCommand):
workerdir = os.path.join(os.path.join(YOCTO_ABBASE, "yocto-worker"))
buildername = self.getProperty("buildername")
src = os.path.join(workerdir, buildername, "build", self.source)
-# find targetsvar then return lines up to a quote
-self.command = ["awk",
-'/%s/{flag=1;print;next}/"/{flag=0}flag' % self.targetsvar,
src]
+self.command = ["cat", src]
ShellCommand.start(self)
def commandComplete(self, cmd):
@@ -51,10 +50,14 @@ class ScrapeTargets(ShellCommand):
return
result = cmd.logs['stdio'].getText()
-targets = result.strip()
-targets = targets.replace('%s="' % self.targetsvar, '')
-targets = targets.replace('\\', '')
-targets = targets.replace('\n', '')
+start = result.find(self.targetsvar) + len(self.targetsvar)
+res = re.search('"([^"]*)"', result[start:])
+targets = ""
+if res:
+targets = res.group()
+targets = targets.replace('%s="' % self.targetsvar, '')
+targets = targets.replace('\\', '')
+targets = targets.replace('\n', '')
self.setProperty("scraped_targets",
targets,
'Targets "%s" scraped from %s' % (targets,
--
2.13.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] add force bash option on build and preamble
Certain distros (Ubuntu) use a less desirable shell for /bin/sh
(dash). In some edge cases, if we source oe-init-build-env from
outside the OEROOT folder, the script will fail (as stated in the
oe-init-build-env script). By adding a variable to force bash as the
shell, we can call "bash -c" to ensure that a compatible shell is
used.
Currently, refkit is the only build that suffers from this edge case.
Signed-off-by: Stephano Cetola
---
buildset-config.controller/nightly-refkit.conf| 3 ++-
lib/python2.7/site-packages/autobuilder/buildsteps/BuildImages.py | 3 +++
lib/python2.7/site-packages/autobuilder/buildsteps/RunPreamble.py | 3 +++
3 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/buildset-config.controller/nightly-refkit.conf
b/buildset-config.controller/nightly-refkit.conf
index 1d2487da6..cbc8508d7 100644
--- a/buildset-config.controller/nightly-refkit.conf
+++ b/buildset-config.controller/nightly-refkit.conf
@@ -11,7 +11,7 @@ repos: [{'poky':
'submodules': True}}]
steps: [{'SetDest':{}},
{'CheckOutLayers': {'submodules': True}},
-{'RunPreamble': {'altcmd': 'refkit/oe-init-build-env'}},
+{'RunPreamble': {'forcebash': True, 'altcmd':
'refkit/oe-init-build-env'}},
{'GetDistroVersion' : {'distro': 'refkit'}},
{'CreateAutoConf': {'machine': 'intel-corei7-64', 'packages': 'ipk',
'distro': 'refkit', 'buildhistory' : False,
@@ -44,6 +44,7 @@ steps: [{'SetDest':{}},
{'ScrapeTargets': {'source':
'refkit/meta-refkit/conf/distro/include/refkit-ci.inc',
'targetsvar': 'REFKIT_CI_BUILD_TARGETS'}},
{'BuildImages': {'images': '#SCRAPEDTARGETS',
+ 'forcebash': True,
'oeinit': 'refkit/oe-init-build-env',
'overrideenv': ['BITBAKEDIR=#YPDIR/bitbake',
'OEROOT=#YPDIR/meta']}},
{'ScrapeTargets': {'source':
'refkit/meta-refkit/conf/distro/include/refkit-ci.inc',
diff --git a/lib/python2.7/site-packages/autobuilder/buildsteps/BuildImages.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/BuildImages.py
index 60ce07ff7..0406fd2e9 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/BuildImages.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/BuildImages.py
@@ -23,6 +23,7 @@ class BuildImages(BitbakeShellCommand):
haltOnFailure = False
flunkOnFailure = True
name = "BuildImages"
+forcebash = False
def __init__(self, factory, argdict=None, **kwargs):
self.layerversion_yoctobsp=0
self.machine=""
@@ -163,6 +164,8 @@ class BuildImages(BitbakeShellCommand):
if self.minnowExists is None or self.minnowExists == "True":
self.command = env + ". ./" + self.oeinit + "; bitbake " +
bitbakeflags + self.images
self.description = ["Building " + str(self.images)]
+if self.forcebash:
+self.command = ['bash', '-c', self.command]
ShellCommand.start(self)
def describe(self, done=False):
diff --git a/lib/python2.7/site-packages/autobuilder/buildsteps/RunPreamble.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/RunPreamble.py
index e9de3c76c..23c4ace2b 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/RunPreamble.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/RunPreamble.py
@@ -16,6 +16,7 @@ class RunPreamble(ShellCommand):
haltOnFailure = False
flunkOnFailure = True
name = "RunPreamble"
+forcebash = False
def __init__(self, factory, argdict=None, **kwargs):
self.factory = factory
@@ -27,4 +28,6 @@ class RunPreamble(ShellCommand):
self.command = ". ./oe-init-build-env"
else:
self.command = ". ./" + self.altcmd
+if self.forcebash:
+self.command = ['bash', '-c', self.command]
ShellCommand.__init__(self, **kwargs)
--
2.13.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH V4 1/1] ScrapeTargets.py: improve target search algorithm
On 07/06, Joshua Lock wrote: > This still leaves us a bit brittle. What if someone adds whitespace > around the assignment operator? Could you create a follow-on patch for > that? > > Thanks! Actually, since the awk command just searches for self.targetsvar now instead of ``self.targetsvar="``, it will match even if there are spaces between the equal. I did just realize that if the variable is NOT multi-line, e.g. REFKIT_CI_POSTBUILD_SELFTESTS, this search will fail because of the "next" command. I'll puzzle over this a bit. -S -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH V4 1/1] ScrapeTargets.py: improve target search algorithm
When scraping the build targets from refkit-ci.inc, grep would only
return the first line of the search result. By replacing grep with
awk, we are now searching for multi-line variables, and should now
scrape build targets even if they have line breaks between them.
[YOCTO #11720]
Signed-off-by: Stephano Cetola
---
.../site-packages/autobuilder/buildsteps/ScrapeTargets.py| 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
index 80153fe85..07e2fdcf4 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
@@ -41,7 +41,9 @@ class ScrapeTargets(ShellCommand):
workerdir = os.path.join(os.path.join(YOCTO_ABBASE, "yocto-worker"))
buildername = self.getProperty("buildername")
src = os.path.join(workerdir, buildername, "build", self.source)
-self.command = "cat " + src + " | grep " + self.targetsvar
+# find targetsvar then return lines up to a quote
+self.command = ["awk",
+'/%s/{flag=1;print;next}/"/{flag=0}flag' % self.targetsvar,
src]
ShellCommand.start(self)
def commandComplete(self, cmd):
@@ -49,10 +51,10 @@ class ScrapeTargets(ShellCommand):
return
result = cmd.logs['stdio'].getText()
-targets = result.replace(self.targetsvar, "")
-targets = targets.strip()
-targets = targets.replace('=', '')
-targets = targets.strip('"')
+targets = result.strip()
+targets = targets.replace('%s="' % self.targetsvar, '')
+targets = targets.replace('\\', '')
+targets = targets.replace('\n', '')
self.setProperty("scraped_targets",
targets,
'Targets "%s" scraped from %s' % (targets,
--
2.13.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH V4 0/1] better matching for refkit ci
changed since V3: Remove line breaks as well. Stephano Cetola (1): ScrapeTargets.py: improve target search algorithm .../site-packages/autobuilder/buildsteps/ScrapeTargets.py| 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) -- 2.13.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH V3 1/1] ScrapeTargets.py: improve target search algorithm
When scraping the build targets from refkit-ci.inc, grep would only
return the first line of the search result. By replacing grep with
awk, we are now searching for multi-line variables, and should now
scrape build targets even if they have line breaks between them.
[YOCTO #11720]
Signed-off-by: Stephano Cetola
---
.../site-packages/autobuilder/buildsteps/ScrapeTargets.py | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
index 80153fe85..8d1549636 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
@@ -41,7 +41,9 @@ class ScrapeTargets(ShellCommand):
workerdir = os.path.join(os.path.join(YOCTO_ABBASE, "yocto-worker"))
buildername = self.getProperty("buildername")
src = os.path.join(workerdir, buildername, "build", self.source)
-self.command = "cat " + src + " | grep " + self.targetsvar
+# find targetsvar then return lines up to a quote
+self.command = ["awk",
+'/%s/{flag=1;print;next}/"/{flag=0}flag' % self.targetsvar,
src]
ShellCommand.start(self)
def commandComplete(self, cmd):
@@ -49,10 +51,9 @@ class ScrapeTargets(ShellCommand):
return
result = cmd.logs['stdio'].getText()
-targets = result.replace(self.targetsvar, "")
-targets = targets.strip()
-targets = targets.replace('=', '')
-targets = targets.strip('"')
+targets = result.strip()
+targets = targets.replace('%s="' % self.targetsvar, '')
+targets = targets.replace('\\', '')
self.setProperty("scraped_targets",
targets,
'Targets "%s" scraped from %s' % (targets,
--
2.13.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH V3 0/1] better matching for refkit ci
Updates since V2: match the first line and remove the variable name, rather than skipping the first line. Also, removed some backslashes and submitted the correct patch rather than resubmitting the old patch again. fixes [YOCTO #11720] Stephano Cetola (1): ScrapeTargets.py: improve target search algorithm .../site-packages/autobuilder/buildsteps/ScrapeTargets.py | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) -- 2.13.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH V2 0/1] better matching for refkit ci
Updates since V1: match the first line and remove the variable name, rather than skipping the first line. fixes [YOCTO #11720] Stephano Cetola (1): ScrapeTargets.py: improve target search algorithm .../site-packages/autobuilder/buildsteps/ScrapeTargets.py| 9 - 1 file changed, 4 insertions(+), 5 deletions(-) -- 2.13.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH V2 1/1] ScrapeTargets.py: improve target search algorithm
When scraping the build targets from refkit-ci.inc, grep would only
return the first line of the search result. By replacing grep with
awk, we are now searching for multi-line variables, and should now
scrape build targets even if they have line breaks between them.
[YOCTO #11720]
Signed-off-by: Stephano Cetola
---
.../site-packages/autobuilder/buildsteps/ScrapeTargets.py| 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
index 80153fe85..c5a2f8d6d 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
@@ -41,7 +41,9 @@ class ScrapeTargets(ShellCommand):
workerdir = os.path.join(os.path.join(YOCTO_ABBASE, "yocto-worker"))
buildername = self.getProperty("buildername")
src = os.path.join(workerdir, buildername, "build", self.source)
-self.command = "cat " + src + " | grep " + self.targetsvar
+# find targetsvar=", skip a line, then return lines up to a quote
+self.command = ["awk",
+'/%s="/{flag=1;next}/"/{flag=0}flag' % self.targetsvar, src]
ShellCommand.start(self)
def commandComplete(self, cmd):
@@ -49,10 +51,7 @@ class ScrapeTargets(ShellCommand):
return
result = cmd.logs['stdio'].getText()
-targets = result.replace(self.targetsvar, "")
-targets = targets.strip()
-targets = targets.replace('=', '')
-targets = targets.strip('"')
+targets = result.strip()
self.setProperty("scraped_targets",
targets,
'Targets "%s" scraped from %s' % (targets,
--
2.13.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] buildset-config/nightly-refkit: add layers to bbconf
Since we are parsing and building all the images in refkit-ci.inc,
there are some layers that are now required. This includes flatpak,
industrial, and ROS layers. Since we are building a dynamic set of
images based on this inc file, we should be adding these layers
dynamically as well at some point.
Signed-off-by: Stephano Cetola
---
buildset-config.controller/nightly-refkit.conf | 6 ++
1 file changed, 6 insertions(+)
diff --git a/buildset-config.controller/nightly-refkit.conf
b/buildset-config.controller/nightly-refkit.conf
index ab3ef6fa6..1d2487da6 100644
--- a/buildset-config.controller/nightly-refkit.conf
+++ b/buildset-config.controller/nightly-refkit.conf
@@ -31,6 +31,9 @@ steps: [{'SetDest':{}},
'refkit/meta-security-isafw',
'refkit/meta-intel-realsense',
'refkit/meta-clang',
+ 'refkit/meta-flatpak',
+ 'refkit/meta-refkit-industrial',
+ 'refkit/meta-ros',
'refkit/meta-openembedded/meta-filesystems',
'refkit/meta-openembedded/meta-gnome',
'refkit/meta-openembedded/meta-networking',
@@ -65,6 +68,9 @@ steps: [{'SetDest':{}},
'refkit/meta-security-isafw',
'refkit/meta-intel-realsense',
'refkit/meta-clang',
+ 'refkit/meta-flatpak',
+ 'refkit/meta-refkit-industrial',
+ 'refkit/meta-ros',
'refkit/meta-openembedded/meta-filesystems',
'refkit/meta-openembedded/meta-gnome',
'refkit/meta-openembedded/meta-networking',
--
2.13.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] ScrapeTargets.py: improve target search algorithm
When scraping the build targets from refkit-ci.inc, grep would only
return the first line of the search result. By replacing grep with
awk, we are now searching for multi-line variables, and should now
scrape build targets even if they have line breaks between them.
Signed-off-by: Stephano Cetola
---
.../site-packages/autobuilder/buildsteps/ScrapeTargets.py| 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
index 80153fe85..c5a2f8d6d 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ScrapeTargets.py
@@ -41,7 +41,9 @@ class ScrapeTargets(ShellCommand):
workerdir = os.path.join(os.path.join(YOCTO_ABBASE, "yocto-worker"))
buildername = self.getProperty("buildername")
src = os.path.join(workerdir, buildername, "build", self.source)
-self.command = "cat " + src + " | grep " + self.targetsvar
+# find targetsvar=", skip a line, then return lines up to a quote
+self.command = ["awk",
+'/%s="/{flag=1;next}/"/{flag=0}flag' % self.targetsvar, src]
ShellCommand.start(self)
def commandComplete(self, cmd):
@@ -49,10 +51,7 @@ class ScrapeTargets(ShellCommand):
return
result = cmd.logs['stdio'].getText()
-targets = result.replace(self.targetsvar, "")
-targets = targets.strip()
-targets = targets.replace('=', '')
-targets = targets.strip('"')
+targets = result.strip()
self.setProperty("scraped_targets",
targets,
'Targets "%s" scraped from %s' % (targets,
--
2.13.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] morty populate_sdk_ext fails for recipes inherit bin_package
On 01/05, richard_al...@keysight.com wrote:
> Hi
> 1) I had just successfully built an image with all the recipes ( hals,
> hals-doc) [and yes, there these are non-empty]
> 2) I had then successfully built image with -c populate_sdk
> 3) The bitbake image -c populate_sdk_ext is what is failing
> [ The above works with Krogoth, only on Morty am I getting the errors during
> populate_sdk_ext
>
> May be the recipe is wrong for Morty? ( I have several other recipes, same
> thing, same structure)
Nothing jumps out about that recipe. If you do a `find` in
tmp/deploy/ipk for hals*, does anything show up? That's where opkg
will be looking for the packages, so I assume it is not there.
>
> inherit bin_package
>
> SUMMARY = "HALs "
> DESCRIPTION = "HALs"
>
> LICENSE = "CLOSED"
> LIC_FILES_CHKSUM = ""
>
> # this can be overridden in local.conf
> HALS_TARBALL_URI ?= "file:///opt/packages/${PN}-${PV}-arm.tar.gz"
>
> SRC_URI = "${HALS_TARBALL_URI}"
>
> # the tar has a root directory , which has the files under
> HALS_TAR_ROOT_DIR_NAME ?= "${PN}-${PV}-arm"
>
> #make the source directory start in this directory
> S = "${WORKDIR}/${HALS_TAR_ROOT_DIR_NAME}"
>
> #runtime depends
> RDEPENDS_${PN} = " libgcc \
> libstdc++ \
> dtc \
>"
> DEPENDS_${PN} = " gtest"
>
> #bring in all to build toolchain
> DEPENDS_${PN}-dev += " ${PN}-doc ${PN}-tests ${PN}-samples"
>
> PACKAGES =+ "${PN}-tests ${PN}-samples "
>
> FILES_${PN}-staticdev += " ${libdir}/*/*.a"
> FILES_${PN}-dev += "${includedir} ""
> FILES_${PN}-samples += "${bindir}/*"
> FILES_${PN}-tests += "${bindir}/*[tT]est"
> FILES_${PN}-doc += "${prefix}/src/doc"
>
>
> # this stops an QA issue
>
> INSANE_SKIP_hals += "dev-so"
> BBCLASSEXTEND = "native nativesdk"
>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] morty populate_sdk_ext fails for recipes inherit bin_package
On 01/04, richard_al...@keysight.com wrote: > I am getting errors with morty and -c populate_sdk_ext when I have recipes > which inherit bin_package > These recipes work fine with Krogoth and it's populate_sdk_ext > > Note: package is not empty, Use to install package on running system. > > No idea how to proceed on fixing this (or if this is an morty issue with > populate_sdk_ext > (-c populate_sdk works fine) Are you able to bitbake the image without "-c populate_sdk_ext"? I am currently working on some bin_package related features, and I am able to build my image (with a bin_package recipe) as well as well as populate the eSDK and SDK. > If I use ipk for package managment > > NOTE: Executing RunQueue Tasks > ERROR: uninative-tarball-1.0-r0 do_populate_sdk: Unable to install packages. > Command '/home/rcallen/proto/morty/tmp/sysroots/x86_64-linux/usr/bin/opkg > --volatile-cache -f > /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-linux/uninative-tarball/1.0-r0/opkg.conf > -t > /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-linux/uninative-tarball/1.0-r0/temp/ipktemp/ > -o > /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-linux/uninative-tarball/1.0-r0/sdk/image/opt/tlo/2.2/sysroots/none > --force_postinstall --prefer-arch-to-version install hals hals-doc' > returned 255: Looks like it can't find hals or hals-doc. Are you sure these are built? The error you are seeing (Couldn't find anything to satisfy) is from the above command: opkg [...] install hals hals-doc. The RPM error is the same. It is telling you that the package-feeds don't contain anything called "hals". > Collected errors: > * opkg_prepare_url_for_install: Couldn't find anything to satisfy 'hals'. > * rm_r: Failed to open dir > /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-linux/uninative-tarball/1.0-r0/temp/ipktemp//opkg-BL2Z8g: > No such file or directory. > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH] nightly.conf: add deploy_artifacts to copy_properties
In order for the build slaves to process the "deploy artifacts"
property, it needs to be passed in when the builds are triggered.
This fixes [YOCTO 10229]
Signed-off-by: Stephano Cetola
---
buildset-config.controller/nightly.conf | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/buildset-config.controller/nightly.conf
b/buildset-config.controller/nightly.conf
index b811f68..4ed255d 100644
--- a/buildset-config.controller/nightly.conf
+++ b/buildset-config.controller/nightly.conf
@@ -84,7 +84,8 @@ steps: [{'SetDest':{}},
'atextprepend': 'SOURCE_MIRROR_FETCH = "1"\n'}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
{'BuildImages': {'images': 'universe -c fetch'}},
-{'TriggerBuilds': {'copy_properties': ['custom_create_eventlog',
'custom_yocto_number', 'is_release'],
+{'TriggerBuilds': {'copy_properties': ['custom_create_eventlog',
+ 'custom_yocto_number', 'is_release',
'custom_deploy_artifacts'],
'schedulerName': 'main-build', 'waitForFinish':
'True',
'schedulerNames': {'nightly-arm': {},
'nightly-arm-lsb': {},
'nightly-mips': {}, 'nightly-mips-lsb': {},
--
2.10.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [oe] OE/Yocto developer survey
On 10/26, Cliff Brake wrote: > How long have you been using OE? ~3 years > How do you use OE/Yocto? [ X ] product development [ X ] hobby/research/education/yocto core developer, etc > What distro do you use? [ ] Poky [ ] Angstrom [ X ] nodistro or custom (Based on Poky) > How do you organize multiple git repos? [ ] Git submodules [ X ] Repo [ X ] Other (Customer Python scripts) > What packaging system? [ ] OPKG [ ] RPM [ X ] Other (IPK) > What GUI toolkits? [ X ] Qt [ X ] Gtk [ ] EFL [ X ] HTML5/JS [ ] Other Our clients develop in QML. > What init system? [ ] systemd [ X ] sysvinit [ X ] busybox init [ ] Other > What libc? [ X ] glibc [ ] uclibc [ ] musl [ ] Other > How do you develop custom applications? [ ] application-SDK [ X ] devshell [ X ] develop on PC, test on target [ ] Other > What language do you primarily use for custom applications? [ X ] C [ X ] C++ [ ] Python [ ] Javascript [ ] Lua [ ] Other Qt for C++ > What do you use for Continuous Integration? [ ] Buildbot [ X ] Jenkins [ ] Other Tried buildbot but it required too much customization for our small team. > Do you use any any of the tooling projects > (https://www.yoctoproject.org/tools-resources/projects) such as ADT, > Hob, Toaster, etc? No -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
