nyuuzyou/wikis huggingface dataset:
WW50 2015-12-10 FullPass 2.1 5e3e2e0cbb0a49986f4653e64c4c8d2b5461645e

=Testing data=
 
 Test type: Full Pass Release (Beta)
 Branch: master
 Build name: 2.1
 poky commit: 5e3e2e0cbb0a49986f4653e64c4c8d2b5461645e 
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0_M1.rc1
 Distributions tested: Ubuntu 14.04 64bit, Fedora 21 64bit, Opensuse 13.2 64bit, CentOS 7 64 bit 
=Test Run Summary Report=
= 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.
=Detailed Report=
{{#if: |
==ADT==
WW51 - 2015-12-18 - Full Pass - 2.1 M1.rc1 - meta-intel

=Testing data=
 
 Test type: Full Pass
 Branch: master
 Release: met-intel release
 Build name: full pass release
 poky: 5e3e2e0cbb0a49986f4653e64c4c8d2b5461645e
 meta-intel: 
 meta-qt3: 
=Summary Report=
	
=Detailed Report=
WW51 - 2018-12-21- Full Test Cycle - 2.6 rc2 - meta-intel 10.0

=Testing data= 
 
 Test type: Full Test Cycle
 Branch: master 
 Release: meta-intel
 Autobuilder images repository: http://yocto-ab-master.jf.intel.com/pub/releases/yocto-meta-intel-10.0
 Build hash information: 
 meta-intel : 7ea89b9ddcdd3de1629bae1465425c8077c5aa06 
 meta-dpdk : cf8e415965e364dba9ccc83b205e24d9c830e0b9 
 poky : 01b405fb70a7ba51197a5cc99b0260206e269508
 
{|
|
{|
|
= 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==
For Bitbake core-image-sato withrm_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 ==
{{:Ptest <ADD HERE THE PROOPER COMMIT>}}
=Detailed Report=
==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
WW52 - 2016-12-19 - Full Test Cycle 2.3 M1 rc1

=Testing data=
 
 Test type: Full Test Cycle
 Branch: master
 Build name: 2.3 M1 rc1
 poky commit: 573c646d4cc62dcd0c230381df4940bdf314d495
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3_M1.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=
= Bugs Found during QA Test =
NOTE:
There is workaround for [10826] and [10873], those are happening due special settings for QA purposes on Autobuilders, doing the below steps the execution of oe-selftest are running correctly 
 - uninstall "unittest-xml-reporting" form the worker on AB
 - set max_user_watches=65535 (64K) 
== 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) ==
== 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 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: 
Due bug 10285 performance results for "bitbake core-image-sato -c rootfs" measurements were failing on 2.2_M3.rc1, hence the numbers shown in the charts for that particular milestone are the ones reported on logs just before of the failure. 
== 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-rootfs.html
=pTest results for genericx86-64 on NUC=
=Detailed Report=
WW52 2015-12-21 FullPass 2.2 5e3e2e0cbb0a49986f4653e64c4c8d2b5461645e

=Testing data=
 
 Test type: Full Pass Release (Beta)
 Branch: master
 Build name: 2.2
 poky commit: 5e3e2e0cbb0a49986f4653e64c4c8d2b5461645e 
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M1.rc2
 Distributions tested: Ubuntu 14.04 64bit, Fedora 21 64bit, Opensuse 13.2 64bit, CentOS 7 64 bit 
=Test Run Summary Report=
= 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.
=Detailed Report=
{{#if: |
==ADT==
Watch Yocto Bugs

Yocto bugzilla adds a lot of fake users for each product and classification as components' default CC user. If developer/tester want to get some components intime bug update, (s)he can Watch related fake user. 
* How to Watch?
# Login Yocto bugzilla.
# Click user Preferences
# Select Email Preferences
# Find fake user email address and Add users to my watch list
* Fake user email address and Classification/Product list
Classification 	Product 	Fake user
Yocto Projects 	 	yp.watcher@fake.user
 	Cross-prelink 	yp.cp.watcher@fake.user
 	Swabber 	yp.swabber.watcher@fake.user
 	Pseudo 	yp.pseudo.watcher@fake.user
 	Eclipse Plugin	yp.ep.watcher@fake.user
 	Anjuta Plugin 	yp.ap.watcher@fake.user
 	Kernel 	yp.kernel.watcher@fake.user
 	Test Suite 	yp.test.watcher@fake.user
 	BSPs 	yp.bsp.watcher@fake.user
 	SDK tools 	yp.sdk.watcher@fake.user
Infrastructure 	 	Infras.watcher@fake.user
 	Autobuilder 	infras.ab.watcher@fake.user
 	Website 	infras.web.watcher@fake.user
 	Bugzilla 	infras.bug.watcher@fake.user
Poky 	 	poky.watcher@fake.user
 	Build System 	poky.bs.watcher@fake.user
 	Documentation 	poky.doc.watcher@fake.user
 	ADT 	poky.adt.watcher@fake.user
 	Security 	N/A
Yocto Metadata Layers	 	meta.watcher@fake.user
 	Meta Recipes 	meta.mr.watcher@fake.user
 	Layers 	meta.layer.watcher@fake.user
Wayland

== Current Status ==
Wayland protocol libraries and the reference Weston compositor are integrated as packages in the core-oe meta/ layer.
The packages can be build against targets that accept mesa-dri. For example, intel-specific emgd drivers that override
mesa-dri cannot be used to build Weston. 
=== Enable Wayland in a image ===
The wayland compositor can be enabled by listing it as a DISTRO_FEATURE; there are two steps: 
==== Enable building ====
* Wayland - If "wayland" flag in DISTRO_FEATURES is set, Mesa builds the wayland-egl platform
* Weston compositor - 
** If "wayland flag in DISTRO_FEATURES is set, Weston will build with KMS support. 
** Also, if X11 is enabled, as in the x11 DISTRO_FEATURES flag is set, weston will be build with X11 support.
The preferred way to enable building is
DISTRO_FEATURES_append = " wayland x11"
==== Enable installing in an image ====
To set installation in an image, you need to add the following parameters in conf/local.conf:
* CORE_IMAGE_EXTRA_INSTALL += "wayland weston" 
=== Running Weston ===
To run Weston inside X11, simply adding weston to the image will be sufficient. Under Sato there will be a Weston launcher in the Utility category. 
Wayland/Weston work in still developer-oriented. The best way to run them is through CLI. As we fine tune the way to run Weston and setting policies,
scripts to automate this work will be provided.
==== Environment setup ====
Please do export XDG_RUNTIME_DIR:
* mkdir -p /tmp/$USER-weston
* chmod 0700 /tmp/$USER-weston
* export XDG_RUNTIME_DIR=/tmp/$USER-weston
==== Launch ====
* weston
== Current working status ==
=== QEMU ===
Weston 1.0.3 will not run directly on the emulated QEMU hardware, due to lack of EGL support.
Weston will run under X emulation without issues.
=== Physical Machines ===
There is no embedded-class physical machine yet verified to run Weston to top of hardware.
Current efforts focus on enabling FRI2. 
== Plan ==
* Upgrade Weston to a version that can run only on framebuffer (e.g. pixman)
* Image that boots Weston on KMS
* Enable GTK+ 3 Wayland support
* Enable Qt Wayland support
* Enable Clutter Wayland support
WebHob Design

== Screencast for WebHob 1.3 design ==
File:Yocto_webHob.1.9_screencast.0.2.mov‎
This is a design prototype for the web application version of the Yocto Hob application.
There are a number of differences with the GTK or desktop-based version, and most of these difference revolve around the use of Projects to organise people working on a build, Groups and the ability to schedule and run builds on a server. The design also concentrates on collaborative features such as being able to report on and share builds as well as incorporating help and news alongside the functionality.
Its also important to note that this is a design and not a set of final requirements. There a lot of things (such as the Deploy function) which are ideas more than anything and there to see how the Yocto community responds and to gather feedback. So if you have ideas and comments, please add them.
Web Hob Contexts

As part of the Web Hob strategy and roadmap exercise carried out in late 2012, three contexts of use were identified following interviews with stakeholders and potential users. 
The ultimate goal of the Web Hob is to support all three contexts, each of which has its own fairly distinct set of use cases. 
==Contexts==
The contexts are summarised below.
===1. Local Web Hob===
The Web Hob is running on localhost, on a single machine, and is not being accessed over the network. It acts as essentially a front-end layer for BitBake in a single-user context.
The user must be capable of installing Web Hob on their own machine. 
===2. Team Web Hob===
Web Hob is installed on to a private server within an organisation's network and is then used by multiple engineers or developers. The organisation is responsible for maintenance of the Web Hob install. By running Web Hob behind the firewall, the organisation is able to harness its collaborative capabilities while maintaining security and keeping source code on its own infrastructure.
There must be people within the organisation who are able to install, configure and run the Web Hob server, but once it is in place other users (such as developers) can access its features over its web interface.
===3. Public Web Hob===
Web Hob runs on a publicly accessible website, on infrastructure owned and maintained by the Yocto Project. Visitors to the website can create accounts and use Web Hob features without having to carry out any local installation.
==Relevance to implementation==
The contexts defined above have some relevance to the implementation roadmap for Web Hob. The initial focus will be on the Local Web Hob context as the use cases that support it are more suited to early implementation. It will then serve as the basis for the first Team Web Hob release, which will introduce a new set of use cases and technical requirements. The Public Web Hob context might be seen as a more long-term aspiration which will only be achievable once Team Web Hob reaches a certain level of maturity.
Webhob REST API Packages

Category:REST API Contracts
=== Endpoints ===
Method	Endpoint	Body	Description 	Comments
GET 	/builds 	JSON	Returns page size limited and search criteria filtered amount of builds from the data base	-
=== Parameters ===
Name 	Type 	Description 	Comments
limit 	number	The amout of builds to be displayed in one page 	-
offset 	number	Represents the position of the first record in the page 	If limit is 1, end point will target the findOne functionality and the offset will act as the actual build id
search 	string	Search string for all fields 	-
filter 	string	Consists of a string used to filter results 	The general form: "<FIELD>:<VALUE>".
orderby	string	the name of the field that determens the soring of the resuls.	"<FIELD>:<ORDER_DIRECTION>"
=== Response ===
Name 	Type 	Dimension	Required	Default value(s)	Description 	Comments
[Object Root] 	object 	- 	YES 	- 	- 	-
[Object Root].count 	number 	- 	YES 	- 	Total amount of builds to be displayed (according to filter parameter)	-
[Object Root].list 	object array 	- 	YES 	- 	- 	To describe a generic object element of the array, the refference to it's root is "list[]"
[Object Root].list[].pk 	number 	- 	YES 	- 	- 	-
[Object Root].list[].model 	string 	- 	YES 	- 	- 	-
[Object Root].list[].fields 	object 	- 	YES 	- 	- 	-
[Object Root].list[].fields.outcome 	number 	2 	YES 	- 	Signals successful or failed build 	0 - the build has failed, 1 - successful build
[Object Root].list[].fields.target 	string 	- 	YES 	- 	The name of the build target(s) 	-
[Object Root].list[].fields.machine 	string array 	- 	YES 	- 	The selected hardware 	-
[Object Root].list[].fields.started_on 	number representation of date	- 	YES 	- 	Marks the moment the process is started 	-
[Object Root].list[].fields.completed_on 	number representation of date	- 	YES 	- 	Marks the moment the process is completed 	-
[Object Root].list[].fields.errors_no 	number 	- 	YES 	- 	Number of errors thrown by the build 	-
[Object Root].list[].fields.warnings_no 	number 	- 	YES 	- 	Number of warnings thrown by the build 	-
[Object Root].list[].fields.cooker_log_path	string 	- 	YES 	- 	Path to log file 	-
[Object Root].list[].fields.image_fstypes 	string array 	- 	YES 	- 	The extensions of the root file systems produced by the build 	-
Weekly 18e902b2dc17746af453869bcc1fba4dbae7c94f

< Back
{| class="wikitable"
|+Results
|- style="background-color:#F0F8FC; padding:10px;"
|Package Name ||Tests ran ||Passed ||Failed ||Passrate ||Last Passrate ||Run difference
|-
|qemux86 ||57 ||style="background-color:#C4FF33;" |57 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|No
|-
|genericx86_minnowmax ||56 ||style="background-color:#C4FF33;" |55 ||style="background-color:#C4FF33;" |1 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|No
|-
|qemux86_64 ||57 ||style="background-color:#C4FF33;" |57 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|No
|-
|qemuarm ||57 ||style="background-color:#C4FF33;" |57 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|No
|-
|qemumips ||57 ||style="background-color:#C4FF33;" |57 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|No
|-
|qemuppc ||57 ||style="background-color:#C4FF33;" |57 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|No
|-
|genericx86-64_minnowmax ||56 ||style="background-color:#C4FF33;" |55 ||style="background-color:#C4FF33;" |1 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|No
|-
|genericx86-64_nuc ||56 ||style="background-color:#C4FF33;" |55 ||style="background-color:#C4FF33;" |1 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|96.0 ||style="background-color:#F78D72;"|YesResults for genericx86-64_nuc weekly runtime 2015-06-25:********************************Tests that failed now and worked last time: 0Tests that passed now and and failed last time: 0Tests that were skipped now and worked last time: 1testcase-1059Tests that were skipped last time and worked now: 0
|-
|genericx86_minnowmax ||56 ||style="background-color:#C4FF33;" |55 ||style="background-color:#C4FF33;" |1 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|No
|-
|genericx86-64_nuc ||57 ||style="background-color:#C4FF33;" |55 ||style="background-color:#C4FF33;" |2 ||style="background-color:#C4FF33;"|96.0 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#F78D72;"|YesResults for genericx86-64_nuc weekly runtime 2015-06-25:********************************Tests that failed now and worked last time: 1testcase-1059Tests that passed now and and failed last time: 0Tests that were skipped now and worked last time: 0Tests that were skipped last time and worked now: 1testcase-1059
Weekly 21823cb466e79540567ad1a43ae6f93d850e4057

< Back
Ran on a qemux86 and compared with commit 8debfea81e69d038bd2d56314b272cb74f5582ed
{| class="wikitable"
|+Results
|- style="background-color:#F0F8FC; padding:10px;"
|Package Name ||Tests ran ||Passed ||Failed ||Passrate ||Last Passrate ||Run difference
 |-
 |qemux86 ||55 ||style="background-color:#C4FF33;" |55 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|No
 |-
 |qemux86_64 ||55 ||style="background-color:#C4FF33;" |55 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|No
 |-
 |genericx86-64_nuc ||55 ||style="background-color:#C4FF33;" |54 ||style="background-color:#F78D72;" |1 ||style="background-color:#C4FF33;"|98.0% ||style="background-color:#C4FF33;"|96.0% ||style="background-color:#F78D72;"|YesResults for genericx86-64_nuc weekly runtime 2016-03-28:********************************Tests that failed now and worked last time: 1testcase-1059Tests that passed now and and failed last time: 2testcase-1096testcase-723Tests that were skipped now and worked last time: 0Tests that were skipped last time and worked now: 0Tests that failed now: 1testcase-1059
 |-
 |qemuarm ||55 ||style="background-color:#C4FF33;" |55 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|No
 |-
 |genericx86-64-lsb_nuc ||57 ||style="background-color:#C4FF33;" |56 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|98.0% ||style="background-color:#C4FF33;"|96.0% ||style="background-color:#F78D72;"|YesResults for genericx86-64-lsb_nuc weekly runtime 2016-03-28:********************************Tests that failed now and worked last time: 0Tests that passed now and and failed last time: 1testcase-1059Tests that were skipped now and worked last time: 0Tests that were skipped last time and worked now: 0Tests that failed now: 0
 |-
 |qemumips ||55 ||style="background-color:#C4FF33;" |55 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|No
 |-
 |qemuppc ||55 ||style="background-color:#C4FF33;" |55 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|No
 |-
 |wic_NUC_1 ||43 ||style="background-color:#C4FF33;" |43 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|98.0% ||style="background-color:#F78D72;"|YesResults for wic_NUC_1 weekly runtime 2016-03-28:********************************Tests that failed now and worked last time: 0Tests that passed now and and failed last time: 1testcase-1059Tests that were skipped now and worked last time: 0Tests that were skipped last time and worked now: 0Tests that failed now: 0
Weekly 3363837b39366d21ac9cf3b16d10563a6edc19df

< Back
{| class="wikitable"
|+Results
|- style="background-color:#F0F8FC; padding:10px;"
|Package Name ||Tests ran ||Passed ||Failed ||Passrate ||Last Passrate ||Run difference
 |-
 |qemux86 ||58 ||style="background-color:#C4FF33;" |58 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|No
Weekly 370a2916c4559c17952392b872322e8e490b124c

< Back
Ran on a genericx86-64_minnowmax and compared with commit 370a2916c4559c17952392b872322e8e490b124c
{| class="wikitable"
|+Results
|- style="background-color:#F0F8FC; padding:10px;"
|Package Name ||Tests ran ||Passed ||Failed ||Passrate ||Last Passrate ||Run difference
 |-
 |genericx86-64_minnowmax ||57 ||style="background-color:#C4FF33;" |55 ||style="background-color:#F78D72;" |2 ||style="background-color:#C4FF33;"|96.0% ||style="background-color:#C4FF33;"|96.0% ||style="background-color:#C4FF33;"|NoResults for genericx86-64_minnowmax weekly runtime 2015-11-01:********************************Tests that failed now and worked last time: 0Tests that passed now and and failed last time: 0Tests that were skipped now and worked last time: 0Tests that were skipped last time and worked now: 0
 |-
 |qemux86 ||57 ||style="background-color:#C4FF33;" |57 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|100.0% ||style="background-color:#C4FF33;"|No
Weekly 413e814b33206ec60a5607f6c909adc845b6971c

< Back
{| class="wikitable"
|+Results
|- style="background-color:#F0F8FC; padding:10px;"
|Package Name ||Tests ran ||Passed ||Failed ||Passrate ||Last Passrate ||Run difference
 |-
 |qemux86 ||58 ||style="background-color:#C4FF33;" |58 ||style="background-color:#C4FF33;" |0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|100.0 ||style="background-color:#C4FF33;"|No