nyuuzyou/wikis huggingface dataset:
Toaster

Category:Toaster
Toaster is a web-based interface to OpenEmbedded and BitBake.
General discussion about Toaster happens on a dedicated mailing list: https://lists.yoctoproject.org/listinfo/toaster
=== Using Toaster ===
Toaster can run in various modes and setups.
* Local mode - in this mode Toaster is setup for use as a local development tool. It can be used to configure builds or just as a receiver for builds done on the command line with bitbake. You can launch it like this:
 $ source oe-init-build-env
 $ source toaster start
You then navigate to the link in your browser (e.g. http://localhost:8000) and configure a project. Or start building in the normal way with bitbake via the command line. Toaster will automatically pick up the builds and you will be able to see them on the build dashboard in your browser.
* Production mode - All the same functionality as the local mode but with the web server setup as a shared service for multiple developers to use, this sets up Toaster as a wsgi application and requires additional configuration.
=== Toaster How-to's ===
Specific pages with Toaster how-tos are available below.
* Contribute to Toaster
* Testing Toaster
* Setting up a local instance of Toaster
* Setting up a production instance of Toaster - documentation for Interactive mode
* How to use the Toaster web interface
* How to delete information from the Toaster database
* How to support permission management in Build Mode for Toaster
* ToasterTable: Toaster's internal API for adding sortable, filterable, paged tables
=== About Toaster ===
* 
* Bug list
* Toaster architecture design
* Toaster and bitbake communications
* Toaster database
* Toaster testing plan
=== In progress documentation ===
We are currently preparing the documentation for the Toaster build functionality. The content here is just a brain dump of what we need to cover (in no particular order). Feel free to add and create content as you see fit:
*Using virtualenv
*Setting up a production instance of Toaster
*manage.py commands - this should include an explanation of lsupdates
*Start Toaster in managed mode
Toaster archive

Category:Toaster
== Design documentation for the Yocto Project 1.5 and 1.6 releases ==
The document shows the content structure of Toaster in the 1.6 release.
== Other design documentation ==
* Visualisations - an inventory of data visualisations we aim to include in the first release of Toaster
* - the roadmap for Toaster development produced by the London-based agency Tobias&Tobias
* - different design approaches to handle multi-user scenarios
* - Toaster information architecture, as it came out from the design project with Tobias&Tobias
== Old design documents ==
* Web_Hob_design_project_with_T%26T - The outcome of the design project with the external agency Tobias&Tobias
* A preliminary design project by Jim Kosem
This page is about the Web Hob project. Web Hob is a web-based interface to the Yocto Project. 
General discussion about Web Hob happens on a dedicated mailing list: https://lists.yoctoproject.org/listinfo/webhob
There have been 2 main pieces of work related to Web Hob so far:
* A design project with the London-based agency Tobias & Tobias
* A preliminary design project by Jim Kosem
== Web Hob information architecture ==
This document represents the content structure of the Web Hob application.
== Different approaches to multi-user workflows ==
This document outlines the different approaches we have uncovered so far to facilitate multi-user and team work with Web Hob. 
* 
== Visualisations index ==
The build analysis functionality in Web Hob will include several graphical presentations of build data. The first step to design them is listing them all.
Toaster travis testing

When a patch comes in on the mailing list a bot monitoring patchwork using git-pw checks out poky-contrib toaster-next and applies the patches it also applies a patch to add a .travis.yml file to the root of the repository. These then get pushed to a github repository and the travis CI system then triggers these tests.
.travis.yml
language: python
python: "3.5"
sudo: required # We don't actually need sudo but this forces the selection of the trusty beta image
dist: trusty # We have to use trusty for the newer glibc that is needed by geckodriver
addons:
 firefox: "47.0"
cache: pip
git:
 depth: 3
install:
 - virtualenv --python=python3 $HOME/virtualenv/
 - virtualenv --python=python2 $HOME/virtualenv/
 - source $HOME/virtualenv/bin/activate
 - pip3 install -r ./bitbake/toaster-requirements.txt
 - pip3 install -r ./bitbake/lib/toaster/tests/toaster-tests-requirements.txt
 - pip3 install flake8
 - export DISPLAY=:99.0
 - sh -e /etc/init.d/xvfb start
 - sleep 3 # give xvfb some time to start
 - mkdir $HOME/bin/
 - curl -L https://github.com/mozilla/geckodriver/releases/download/v0.8.0/geckodriver-0.8.0-linux64.gz | zcat > $HOME/bin/wires
 - chmod +x $HOME/bin/wires
before_script:
 - export PATH=$PATH:$HOME/bin/
 - export TOASTER_TESTS_BROWSER=marionette
 - firefox --version
 - env
 - wires --help # verify binary runs OK
script:
 - ./bitbake/lib/toaster/manage.py test tests.browser
 - ./bitbake/lib/toaster/manage.py test toastergui
 - flake8 ./bitbake/lib/toaster/ --select F --exit-zero # We have too many errors at the moment
Training

This page collects training materials as contributed by the community.
== Embedded Linux Conference 2011 ==
Thank you to Free-Electrons.com for the sweet contribution of these videos!
Link to the Free-Electrons.com web page
* Building Custom Embedded Images with Yocto (slides)
* Building Custom Embedded Images with Yocto (450x800 video)
* Yocto Project: Practical Kernel Development Tutorial (slides)
* Yocto Project: Practical Kernel Development Tutorial (450x800 video)
* The Yocto Project and its Application Development Toolkit (ADT) (slides)
* The Yocto Project and its Application Development Toolkit (ADT) (450x800 video)
* Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking (slides)
* Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking (450x800 video)
== Intel Developer Forum 2011 ==
* Create a Custom Embedded Linux OS for Any Embedded Device Using the Yocto Project (hands-on lab, PDF slides, 2011-09)
== Miscellaneous ==
* Using Custom Users/Groups in Yocto 1.1 (PDF slides, 2011-08-10)
User-contrib

Yocto project supports user created repositories at git.yoctoproject.org. To create a repo you must have had your public key key added to our system. Richard Purdie or Michael Halstead can add your public key if needed.
The following command will initialize an empty repository and clone it:
 git clone git@git.yoctoproject.org:user-contrib/[username]/[reponame]
If you already have a repository and want to push it for the first time you can instead add a new remote and push to it.
 git remote add yocto git@git.yoctoproject.org:user-contrib/[username]/[reponame]
 git push yocto
By default these repositories are not public displayed. In order to make your repo public contact Michael Halstead with a description. Have a look at the Layer_Publishing_Guide to see what sections of apply to your repository.
Using the Wiki

A few basic instructions for how to use the Yocto wiki.
==Creating a Page==
Before creating a new page, you should first make sure that a page on your topic does not already exist:
# In the search box in the upper right corner, enter your topic.
# If the exact topic exists, the page will open.
# If there are related pages, you will get a search results page. Check if your topic is in the results.
# If your topic does not exist, choose create this page.
==How to edit a page==
If you'd like to change a page.
# Make sure that you are logged in.
# Click the Edit link.
# Enter your changes in the box.
# In the Summary box, enter a short explanation of what you did.
# Click Show preview if you want to check your changes.
# Click Save page.
==Formatting==
The Yocto Project wiki uses MediaWiki formatting (the same as used on Wikipedia, for example). For simple formatting, use the buttons above the edit box. For more information see:
* Cheatsheet
* General MediaWiki user help
* MediaWiki manual
* Embedding Video
Credit: These instructions were based on the MeeGo Wiki contribution guidelines used under the Creative Commons Attribution 3.0 License
Using virtualenv

Category:Toaster
Toaster brings in extra Python dependencies that the Bitbake core doesn't need in order to run. As such, it is expected that some Python packages required by Toaster may not be installed on the systems that currently run Bitbake without issues.
In order to make it easy to run Toaster, a requirements file is provided; this file, named "toaster-requirements.txt", in the root directory of bitbake, lists dependencies in a pip install-compatible format.
The recommend usage is to install these dependencies in a Python virtual environment using pip.
== How to ==
1. create a virtual environment and activate it:
 $ virtualenv venv
 $ source venv/bin/activate
2. use pip to install needed packages
 $ pip install -r bitbake/toaster-requirements.txt
3. use toaster normally, either in 
* interactive mode
 $ source oe-init-build-env
 $ source toaster start
* managed mode
 
 $ bitbake/bin/toaster
Happy virtualenv-ing !
Validation and Infrastructure Team Bug Triage

= New Team Bugs =
== New Team Bugs (No Priority) ==
== New Team Bugs (No Milestone) ==
= Current Bugs =
== High/Medium+ Bugs ==
== Need Info ==
== Reopened ==
== Old Milestone ==
= Team Member Bugs =
== Joshua Bugs ==
== Tracy Bugs ==
== Stephano Bugs ==
== Ee Peng Bugs ==
= Individual Components =
== Automated Build Testing ==
== Automated Runtime Testing ==
== Release Process ==
== Test Plans/Suite ==
== Testopia ==
Visualisations

Category:Toaster
This is a list of the graphical presentations that will be part of the Web Hob build analysis functionality. It is work in progress: feel free to contribute suggestions and examples.
What 	For 	How 	Answers 	Example 	Bugzilla
Brought in by relationships	Recipes 	Network graph 	Why is this recipe included in my build? 	Network graph example	4301
Brought in by relationships	Packages 	Network graph 	Why is this package being built? 	Network graph example	4400
Dependencies 	Recipes 	Network graph 	What does this recipe add to my build? 	Network graph example	4399
Dependencies & recommends 	Packages 	Network graph 	What does this package add to my build? What should I consider including with this package? 	Network graph example	4329
Size 	All packages 	Treemap 	Why is my image this size? 	Treemap example 	4330
Size 	One package 	Sunburst diagram 	What files does this package bring to my image? 	 	4331
Dependencies 	Tasks 	Hierarchical tree 	Which tasks ran before and after this one? 	 	4285
Build time 	Tasks 	Floating bar chart	Where are the performance bottlenecks in this build? How much parallelism happened during the build? Which tasks ran before and after other tasks?	 	4384
Build time 	Recipes 	Treemap 	Where are the performance bottlenecks in this build? 	Treemap example 	4384
CPU usage 	Build hardware	Histogram 	How is the CPU of my hardware being used during the build? 	Histogram example 	4387
Disk I/O 	Build hardware	Histogram 	How is the disk of my hardware being used during the build? 	Histogram example 	4387
Vmstat

=System monitoring with vmstat=
The following results were obtained based on data collected using vmstat, a tool that reports a system's virtual memory statistics. 
These plots were produced using the scripts located on the bb-perf repository.
=System Characteristics=
===Distro===
 CentOS Linux release 7.3.1611 (Core)
 Linux version 3.10.0-514.6.1.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Wed Jan 18 13:06:36 UTC 2017
===RAM===
 MemTotal: 131814472 kB
 MemFree: 70067576 kB
 MemAvailable: 127241460 kB
===Processor===
 Architecture: x86_64
 CPU op-mode(s): 32-bit, 64-bit
 Byte Order: Little Endian
 CPU(s): 48
 On-line CPU(s) list: 0-47
 Thread(s) per core: 2
 Core(s) per socket: 12
 Socket(s): 2
 NUMA node(s): 2
 Vendor ID: GenuineIntel
 CPU family: 6
 Model: 62
 Model name: Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
 Stepping: 4
 CPU MHz: 1263.621
=Vmstat Output=
== Processing Jobs==
 Procs
 r: The number of runnable processes (running or waiting for run time).
 b: The number of processes in uninterruptible sleep.
== Memory Usage==
 Memory
 swpd: the amount of virtual memory used.
 free: the amount of idle memory.
 buff: the amount of memory used as buffers.
 cache: the amount of memory used as cache.
== IO Activity==
 IO
 bi: Blocks received from a block device (blocks/s).
 bo: Blocks sent to a block device (blocks/s).
== System Operations==
 System
 in: The number of interrupts per second, including the clock.
 cs: The number of context switches per second.
== CPU Resources==
 CPU
 These are percentages of total CPU time.
 us: Time spent running non-kernel code. (user time, including nice time)
 sy: Time spent running kernel code. (system time)
 id: Time spent idle. Prior to Linux 2.5.41, this includes IO-wait time.
 wa: Time spent waiting for IO. Prior to Linux 2.5.41, included in idle.
 st: Time stolen from a virtual machine. Prior to Linux 2.6.11, unknown.
=Reproducibility=
The overall behavior of each plot is the same when the monitoring script (vmstat.sh) is ran several times in the same machine; however, there are two cases where the plots mismatched with each other.
== IO Activity ==
The IO Activity plots are rather similar, but the Reading activity has different ranges as it is shown below.
Image:Vmstat-io-minimal.png|Results obtained running the script for the first time
Image:Vmstat-io-minimal-2.png|Results obtained running the script for the second time
== CPU Resources ==
Although the behavior is quite similar between the plots, the CPU waiting time curve has different ranges as it is shown below.
Image:Vmstat-cpu-minimal.png|Results obtained running the script for the first time
Image:Vmstat-cpu.png|Results obtained running the script for the second time
WW02 - 2019-01-09 - Full Test Cycle 2.6.1 RC1

=Testing data= 
 
 Test type: Full Test Cycle
 Branch: Thud
 Build name: yocto_2.6.1_rc1
 poky commit: 1cab405d88149fd63322a867c6adb4a80ba68db3
 Autobuilder images repository: https://autobuilder.yocto.io/pub/releases/yocto-2.6.1.rc1
 Distributions tested: 
 CentOs 7
 Debian 9
 Fedora 26
 Fedora 27
 OpenSuse 42.3
 Ubuntu 16.04
 Ubuntu 17.10 
 
{|
|
{|
|
= Bugs Found during QA Test =
== New issues Found during QA Test & Community ==
== High and M+ issuesFound during QA Test (NOT NEW) ==
== Other Bugs found during QA Test (NOT NEW) ==
= Current community Open Bugs - Medium+/High =
Overview of the open bugs opened against current milestoneor release which are Medium+ or High and are not targetedfor the next milestones
== Bug Trend ==
An overview of thisweek's Yocto Bug Trend charts can be accessed on thefollowing 
= Build Performance Test =
Detailed description on how performance test is run canbe found on the Performance Test wiki.
The belowcharts are displaying the build performance trend for 2.1M4 to 2.3 M3. Performance execution has had 2 stages, one executed from 1.6 to 2.1 in RO and executed from 1.6 to 2.1in RO and are differences between HW used in bothlocations, hence the numbers are different.
* RO Charts
* GDC Charts
Below chars are showing the latestperformance results taken from the current milestone.
== Performance Charts==
File:WW03-2k19_-_table_2.6.1.rc1.PNG
=pTest for genericx86-64 on NUC=
== open bugs ==
== results ==
=Detailed Report=
==Package Management Issues==
Status
Bugs
Agenda
==BitBake==
Status
Bugs
Agenda
==BSPs==
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
==OE-Core==
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
==Runtime==
Status
Bugs
Agenda
==Toaster==
Status
Bugs
Agenda
Status
Bugs
Agenda
==ADT==
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
Status
Bugs
Agenda
==CROPS==
Status
Bugs
Agenda
==Eclipse Plugin==
Status
Bugs
Agenda
Status
Bugs
Agenda
==eSDK==
Status
Bugs
Agenda
Status
Bugs
Agenda
==Kernel==
Status
Bugs
Agenda
==General Runtime==
Status
Bugs
Agenda
WW03 - 2014-01-14 - Full Pass Release 1.6 M2.rc1

=Testing data=
 
 Test type: Full Pass Release Test
 Branch: master
 Milestone: M2
 Build name: 1.6_M2.rc1
 poky commit: e4c23f7bcb79072ea6028fbdf8f3f0dc17a63371
 Eclipse Plugin commit Kepler: c73c6e4510c42601854f3c542ca6e14b4510380c
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/releases/1.6_M2.rc1/
 Distributions tested: Ubuntu 13.10 64bit, Fedora 19 64bit, Fedora 20 32bit, Opensuse 12.3 64bit, CentOS 6.5 64 bit 
=Summary Report=
	
=Detailed Report=
WW03 - 2014-01-14 - meta-intel - Full Pass Release 1.6 M2.rc1

=Testing data=
 
 Test type: Full Pass Release
 Branch: master
 Milestone: M2
 Build name: full pass release
 poky commit: e4c23f7bcb79072ea6028fbdf8f3f0dc17a63371
 meta-intel commit: 11fc51c05f378b7fef2f5879e8e1f11d7046e85b
=Summary Report=
	
=Detailed Report=
WW04 - 2014-01-23 - Full Pass Release 1.6 M2.rc2

=Testing data=
 
 Test type: Full Pass Release Test
 Branch: master
 Milestone: M3
 Build name: 1.6_M3.rc1
 poky commit: b70a10ca3ee4a0add90d387e2c8288e531aaa47c
 Eclipse Plugin commit Kepler: f4d8e9243f9355424a01e2d72fd1abbf68d3bb7c
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20140213-1
 Distributions tested: Ubuntu 13.10 64bit, Fedora 19 64bit, Fedora 20 32bit, Opensuse 12.3 64bit, CentOS 6.5 64 bit 
=Summary Report=
	
=Detailed Report=
WW05 - 2016-01-28 - Full Pass 2.1 M2.rc1

=Testing data=
 
 Test type: Full Pass Release Test
 Branch: master
 Build name: 2.1_M2.rc1
 poky commit: 3d2c0f5902cacf9d8544bf263b51ef0dd1a7218c
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M2.rc1/
 Distributions tested: Ubuntu 15.04 64 bit, Ubuntu 14.04 64bit, Fedora 21 64bit, Fedora 22 64bit, Opensuse 13.2 64bit, CentOS 7 64 bit 
=Test Run Summary Report=
= Bugs Found during QA Test =
== New and notable issues Found during QA Test & Community ==
== Other Bugs found during QA Test ==
== pTest open bugs ==
= Current community Open Bugs - Medium+/High =
Overview of the open bugs opened against current milestone or release which are Medium+ or High and are not targeted for the next milestones
== Bug Trend ==
An overview of this week's Yocto Bug Trend charts can be accessed on the following page
= Build Performance Test =
Detailed description on how performance test are run can be found on Performance Test wiki.
The below charts are displaying the build performance trend for 1.8 by milestone starting 1.6 on Master. The charts by Milestone can be accessed at this link where you can view more detailed information or by clicking on the images which will open a new window with the interactive chart.
== Performance Charts==
For Bitbake core-image-sato with rm_work
 1280px | link=https://wiki.yoctoproject.org/charts/perf_milestone/bitbake-core-image-sato-rmwork.html 
Building the Virtual kernel
 1280px | link=https://wiki.yoctoproject.org/charts/perf_milestone/bitbake-virtual-kernel.html
Building the rootfs
 1280px | link=https://wiki.yoctoproject.org/charts/perf_milestone/bitbake-core-image-sato-rootfs.html
=pTest results for genericx86-64 on NUC=
|}
=Detailed Report=
WW05 - 2017-01-24 - Full Test Cycle 2.3 M2 rc1

=Testing data=
 
 Test type: Full Test Cycle
 Branch: master
 Build name: 2.3 M2 rc1
 poky commit: 62d7d4130202d8ede16abf9e7d779361ca70847e
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3_M2.rc1/
 Distributions tested: 
 -Ubuntu 16.04
 -Ubuntu 14 04 
 -OpenSuse 421
 -Opensuse 13.2 
 -Debian 8
 -Centos 7
 -Fedora 23
 -Fedora 24 
=Test Run Summary Report=
 NOTE: There were missing Test Runs due the lack of resources for the execution.
= Bugs Found during QA Test =
== New issues Found during QA Test & Community ==
== High and M+ issues Found during QA Test (NOT NEW) ==
== Other Bugs found during QA Test (NOT NEW) ==
= Current community Open Bugs - Medium+/High =
Overview of the open bugs opened against current milestone or release which are Medium+ or High and are not targeted for the next milestones
== Bug Trend ==
An overview of this week's Yocto Bug Trend charts can be accessed on the following page
= Build Performance Test =
Detailed description on how performance test are run can be found on Performance Test wiki.
The below charts are displaying the build performance trend for 2.1 M4 to 2.3 M1. Performance execution has 2 stages, one executed form 1.6 to 2.1 in RO and another one started on 2.1 from GDC, there are difference between HW used in both location hence the numbers are different.
* RO Charts
 
* GDC Charts
Below chars are showing the latest performance results taken from current milestone
== Performance Charts==
 
NOTE: During the 2.3 M2 QA cycle period, Fedora machine was under debugging activities to investigate more on bug 10884 hence only results for Ubuntu machine are displayed on the charts.
== Performance Charts==
For Bitbake core-image-sato with rm_work
 1280px | link=https://wiki.yoctoproject.org/charts/perf_milestone_GDC/bitbake-core-image-sato-rmwork.html 
Building the Virtual kernel
 1280px | link=https://wiki.yoctoproject.org/charts/perf_milestone_GDC/bitbake-virtual-kernel.html
Building the rootfs
 1280px | link=https://wiki.yoctoproject.org/charts/perf_milestone_GDC/bitbake-core-image-sato-rootfs.html
Building core-image-sato
 1280px | link=https://wiki.yoctoproject.org/charts/perf_milestone_GDC/bitbake-core-image-sato.html
eSDK Deploy time
 1280px | link=https://wiki.yoctoproject.org/charts/perf_milestone_GDC/bitbake-eSDK.html
=pTest for genericx86-64 on NUC=
== open bugs ==
== results ==
 Results
=Detailed Report=