[yocto] QA cycle report for 2.6 M2 RC1

2018-08-08 Thread Yeoh, Ee Peng
Hello All,



This is the full report for 2.6 M2 RC1:

https://wiki.yoctoproject.org/wiki/WW32_-_2018-08-07_-_Full_Test_Cycle_2.6_M2_rc1



=== Summary 



All planned tests were executed except a few SDK automated tests were skipped 
in Autobuilder (testrun# 9830-9836, 9796-9797).  Team found that these SDK 
automated tests were running successfully in core-image-sato-sdk image but not 
the existing core-image-sato used by Autobuilder, investigating why these 
automated tests were skipped in core-image-sato and no message available in 
testsdk logfile to explain why it was skipped.  Team also found that eSDK 
devtool automated testcase(s) were skipped unexpectedly due to the unknown 
error on testcase dependency logic, temporary removing the dependency logic and 
successfully executed the devtool tests.



There were zero high milestone defect.  Team had found 3 new defects,  where 
buildhistorydifftest and wic test_fix_size failure [9] [10] and ptest for 
libxml failed in current release but passed in previous 2.6 M1 rc1.



=== QA-Hints



No high milestone defect.



=== Bugs 



New Bugs

[1] Bug 12866 - [2.6 M2 rc1] wic test_fix_size failed

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12866



[2] Bug 12864 - [2.6 M2 rc1] buildhistorydifftest failed

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12864



[3] Bug 12869 - [2.6 M2 rc1] libxml test cases failed

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12869



Regards

Yeoh Ee Peng



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-intel] Getting black screen for Install option

2018-08-08 Thread Dhanasekar Jaganathan
Hi Anuj,

As per your suggestion, I have made the changes for "install option, Still
I am getting black screen,





Thanks,
Dhanasekar

On Wed, Aug 8, 2018 at 9:01 PM, Dhanasekar Jaganathan <
jdhanasekar...@gmail.com> wrote:

> Hi Anuj. You want me to add this change in systemd-boot..? If wrong ,
> please correct me.
>
> On Wed 8 Aug, 2018, 7:10 PM Anuj Mittal,  wrote:
>
>> On 08/08/2018 08:58 PM, Dhanasekar Jaganathan wrote:
>> >
>> > Hi All,
>> >
>> > I have created yocot bootable USB live image by this command "*sudo dd
>> > if=core-image-sato-intel-core2-32.hddimg of=/dev/sdb1"*
>> > "
>> >
>> > After power on my system, I have got three options,
>> >
>> > 1. boot
>> > 2. install
>> > 3. Reboot into firmware.
>> >
>> >
>> > When I select "install" to install yocto on mSata, I am getting black
>> > screen.
>> > I am using com port serial console for video propose. My board has no
>> > support for onboard or offboard VGA.
>> >
>>
>> May be try adding serial console 'console=ttyS0,115200' in kernel boot
>> line when using 'install'.
>>
>>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] uBoot, kernel and device tree files

2018-08-08 Thread Srinivasan, Raja
All

We are using rocko.on variscite var-som-mx6.

In order to increase the security of our system (during a system upgrade), we 
are looking to merge uImage (kernel image) and the device tree file into 1 
file. Currently these are 2 different files and are worried that a file copy 
operation might get aborted.

My research so far indicates mkuboot can be used to merge these. but having 
trouble making this work.

Need some ideas.

Any pointers appreciated. srini





CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-intel] Getting black screen for Install option

2018-08-08 Thread Dhanasekar Jaganathan
Hi Anuj. You want me to add this change in systemd-boot..? If wrong ,
please correct me.

On Wed 8 Aug, 2018, 7:10 PM Anuj Mittal,  wrote:

> On 08/08/2018 08:58 PM, Dhanasekar Jaganathan wrote:
> >
> > Hi All,
> >
> > I have created yocot bootable USB live image by this command "*sudo dd
> > if=core-image-sato-intel-core2-32.hddimg of=/dev/sdb1"*
> > "
> >
> > After power on my system, I have got three options,
> >
> > 1. boot
> > 2. install
> > 3. Reboot into firmware.
> >
> >
> > When I select "install" to install yocto on mSata, I am getting black
> > screen.
> > I am using com port serial console for video propose. My board has no
> > support for onboard or offboard VGA.
> >
>
> May be try adding serial console 'console=ttyS0,115200' in kernel boot
> line when using 'install'.
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [layerindex-web][PATCH 00/31] Distro comparisons (cover letter only)

2018-08-08 Thread Paul Eggleton
This set of changes builds upon the OE-Classic support we had previously
to enable importing data from other Linux distributions (or indeed other
operating systems) and linking and comparing the packages there to recipes
in OE. The initial support is just for importing RPM spec files, using
the assumption that they can be brought down locally (and scripts to
fetch them are provided for Fedora and any nominated Github organisation).
There is also basic support for importing Debian package info from a
running system (i.e. from the output of apt-cache show "*").
However, the data is not specific and in theory a script could be
written to import from just about any system.


The following changes since commit fca74f3ac3c6536c50cb0a518fe78447a284dc55:

  Update TODO list (2018-08-06 12:36:31 +0200)

are available in the Git repository at:

  git://git.yoctoproject.org/layerindex-web paule/otherdistro
  http://git.yoctoproject.org/cgit.cgi//log/?h=paule/otherdistro

Paul Eggleton (31):
  forms: clear out comparison recipe/layerbranch if status doesn't accept them
  Add a script to import layers from an existing layer index
  update_classic_status: fix matching on wrong layer
  Add partial path macro for vcs URL fields
  Add support for other distro comparisons
  Add script to import from other distros
  update_classic_status: update for other distro comparisons
  update_classic_status: set cover_pn from pn for direct match
  update_classic_status: use source URLs to match python/perl recipes
  update_classic_status: look for certain prefixes in order to match
  update_classic_status: add skip option
  Allow searching for uncategorised recipes in the comparison search
  Enhance filtering comparisons
  views: fix unknown categories comparison stats graph to include "Not 
available"
  Add "needs attention" flag for comparison recipes
  Add support for importing Debian package info
  Support reversed other distro recipe list / filtering
  Support selecting more than one layer in other distro comparison search form
  Support excluding inherited classes from other distro comparison reversed 
query
  Add basic CSV export for other distro comparisons
  Add ability to store extra URLs to be displayed for comparison recipes
  rrs: show link to other distro comparison pages
  Rename LayerItem classic field to comparison
  Fix comparison layers showing up in dependencies list in edit layer page
  Add ability to trigger comparison updates manually from UI
  Add script to fetch all repos under a github organisation
  Add script to fetch Fedora package sources
  Show source URLs on recipe detail page
  README: add setup info for other distro comparisons
  Add side-by-side comparison detail and enhanced selection
  Show links to include files on recipe detail

 README|  82 ++-
 TODO  |   2 -
 layerindex/admin.py   |   6 +
 layerindex/context_processors.py  |   4 +-
 layerindex/forms.py   |  37 +-
 layerindex/migrations/0015_comparison.py  |  24 +
 .../migrations/0016_classicrecipe_delete.py   |  19 +
 .../0017_classicrecipe_needs_attention.py |  19 +
 .../migrations/0018_layerrecipeextraurl.py|  26 +
 .../0019_layeritem_classic_comparison.py  |  25 +
 layerindex/migrations/0020_update_manual.py   |  50 ++
 layerindex/models.py  | 113 +++-
 layerindex/static/css/additional.css  |  20 +
 layerindex/tasks.py   |  23 +
 layerindex/templatetags/extrafilters.py   |  35 ++
 layerindex/tools/fedora-fetch.py  | 170 ++
 layerindex/tools/github-fetch.py  | 135 +
 layerindex/tools/import_classic.py|   2 +-
 layerindex/tools/import_classic_wiki.py   |   2 +-
 layerindex/tools/import_layers.py | 251 
 layerindex/tools/import_otherdistro.py| 564 ++
 layerindex/tools/lib/__init__.py  |   0
 layerindex/tools/lib/rpmmacros.py |  53 ++
 layerindex/tools/update_classic_status.py | 187 +-
 layerindex/update.py  |   8 +-
 layerindex/urls.py|  48 +-
 layerindex/urls_branch.py |   5 +-
 layerindex/utils.py   |   3 +
 layerindex/views.py   | 502 ++--
 templates/base.html   |   2 +
 templates/base_toplevel.html  |  16 +-
 templates/layerindex/classchecklist.html  |  21 +
 templates/layerindex/classic_base.html|  33 +-
 templates/layerindex/classicrecipedetail.html | 184 ++
 templates/layerindex/classicrecipes.html  | 324 +-
 templates/layerindex/classicrecipes_csv.txt   |   2 +
 templates/layerindex/classicstats.html|  16 +-
 .../layerindex/comparisonrecipebase.html  | 229 +++
 .../layerindex/comparisonrecip

Re: [yocto] [meta-intel] Getting black screen for Install option

2018-08-08 Thread Anuj Mittal
On 08/08/2018 08:58 PM, Dhanasekar Jaganathan wrote:
> 
> Hi All,
> 
> I have created yocot bootable USB live image by this command "*sudo dd
> if=core-image-sato-intel-core2-32.hddimg of=/dev/sdb1"*
> "
> 
> After power on my system, I have got three options,
> 
> 1. boot
> 2. install
> 3. Reboot into firmware.
> 
> 
> When I select "install" to install yocto on mSata, I am getting black
> screen.
> I am using com port serial console for video propose. My board has no
> support for onboard or offboard VGA.
> 

May be try adding serial console 'console=ttyS0,115200' in kernel boot
line when using 'install'.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-intel] Getting black screen for Install option

2018-08-08 Thread Dhanasekar Jaganathan
Hi All,

I have created yocot bootable USB live image by this command "* sudo dd
if=core-image-sato-intel-core2-32.hddimg of=/dev/sdb1"*
"

After power on my system, I have got three options,

1. boot
2. install
3. Reboot into firmware.


When I select "install" to install yocto on mSata, I am getting black
screen.
I am using com port serial console for video propose. My board has no
support for onboard or offboard VGA.

If you have solution for this issue, please provide me.

HW details:

Board : Intel Atom C200 CPU , Mohon Peak
BIOS: Coreboot + UEFI Payload.


Thanks,
Dhanasekar
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Getting black screen for Install option

2018-08-08 Thread Dhanasekar Jaganathan
Hi All,

I have created yocot bootable USB live image by this command "* sudo dd
if=core-image-sato-intel-core2-32.hddimg of=/dev/sdb1"*
"

After power on my system, I have got three options,

1. boot
2. install
3. Reboot into firmware.


When I select "install" to install yocto on mSata, I am getting black
screen.
I am using com port serial console for video propose. My board has no
support for onboard or offboard VGA.

If you have solution for this issue, please provide me.

HW details:

Board : Intel Atom C200 CPU , Mohon Peak
BIOS: Coreboot + UEFI Payload.


Thanks,
Dhanasekar
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [PATCH] run-config: Reverse the oder of remove layers

2018-08-08 Thread Aaron Chan
This patch fixes the "Collection Error during parsing layer conf"
when a parent layer is accidentally added before depend layers.
When removing layers from bblayers, we should not be following
the same sequence of adding the layers, it should be done in a
reversed order. This is an assumption that the layers have their
dependent layers added before the parent layers are added.
In general, the parent layer require to be remove first before
its child dependencies layers.

Signed-off-by: Aaron Chan 
---
 scripts/run-config | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/run-config b/scripts/run-config
index ce40249..9fede1e 100755
--- a/scripts/run-config
+++ b/scripts/run-config
@@ -152,8 +152,8 @@ for stepnum in range(1, maxsteps + 1):
 utils.printheader("Step %s/%s: Running 'plain' command %s" % (stepnum, 
maxsteps, cmd))
 bitbakecmd(builddir, cmd, report, stepnum, oeenv=False)
 
-# Remove any layers we added
-for layer in layers:
+# Remove any layers we added in a reverse order
+for layer in reversed(layers):
 bitbakecmd(builddir, "bitbake-layers remove-layer %s" % layer, report, 
stepnum)
 
 if publish:
-- 
2.16.2.windows.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Copy git hashes of recipes during the image build

2018-08-08 Thread Yuvarajesh Valleru

Hi,

I am building the custom yocto image regularly so that I do have so may 
versions of the image. But when an bug occured in older version images, 
I could not find the changes in source code because of AUTOREV. Is there 
any possibility to copy the hashes during the build and store in another 
recipe, so that I can have all my hashes in my target system.


Thank You,

Regards,

Rajesh




--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto