[yocto] M+ & H bugs with Milestone Movements WW38

[Stephen Jolley]

All,

YP M+ or high bugs which moved to a new milestone in WW38 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  13533

Devtool finish on _git package with SRCPV in PV points to wrong WORKDIR

richard.pur...@linuxfoundation.org

saul.w...@windriver.com

3.4 M3

3.4 M4


 

  14040

recipetool: creating binary recipe from upstream git repo without explicit PV 
causes circular reference in SRC_URI

richard.pur...@linuxfoundation.org

saul.w...@windriver.com

3.4 M3

3.4 M4


 

  14491

[QA 3.4_M2.rc1] - stap.StapTest.test_stap failure

richard.pur...@linuxfoundation.org

anuj.mit...@intel.com

3.4 M3

3.3.4

Thanks, 

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com  

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54776): https://lists.yoctoproject.org/g/yocto/message/54776
Mute This Topic: https://lists.yoctoproject.org/mt/85753533/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW38!

[Stephen Jolley]

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


richard.pur...@linuxfoundation.org

4


michael.opdenac...@bootlin.com

1


alexandre.bell...@bootlin.com

1


yi.z...@windriver.com

1


to...@cybernetics.com

1


qi.c...@windriver.com

1


r...@burtonini.com

1


Grand Total

10

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54775): https://lists.yoctoproject.org/g/yocto/message/54775
Mute This Topic: https://lists.yoctoproject.org/mt/85753510/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 3.4

[Stephen Jolley]

All,

Below is the list as of top 50 bug owners as of the end of WW38 of who have
open medium or higher bugs and enhancements against YP 3.4.   There are 28
possible work days left until the final release candidates for YP 3.4 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

37


r...@burtonini.com

31


david.re...@windriver.com

22


randy.macl...@windriver.com

15


trevor.gamb...@windriver.com

12


bruce.ashfi...@gmail.com

11


richard.pur...@linuxfoundation.org

11


timothy.t.orl...@intel.com

9


bluelightn...@bluelightning.org

7


kai.k...@windriver.com

7


mhalst...@linuxfoundation.org

5


hongxu@windriver.com

4


qi.c...@windriver.com

4


saul.w...@windriver.com

3


mingli...@windriver.com

3


jpewhac...@gmail.com

3


chee.yang@intel.com

3


ms...@mvista.com

2


tony.tascio...@windriver.com

2


yf...@uwaterloo.ca

2


alejan...@enedino.org

2


alexandre.bell...@bootlin.com

2


akuster...@gmail.com

2


yoctoproj...@cookiesoft.de

1


douglas.ro...@taitradio.com

1


yi.z...@windriver.com

1


sangeeta.j...@intel.com

1


fransmeulenbro...@yahoo.com

1


ydir...@free.fr

1


paul.gortma...@windriver.com

1


pokyli...@reliableembeddedsystems.com

1


sakib.sa...@windriver.com

1


open.sou...@oleksandr-kravchuk.com

1


jay.shen.t...@intel.com

1


raj.k...@gmail.com

1


mark.ha...@kernel.crashing.org

1


alex.kana...@gmail.com

1


john.kaldas.e...@gmail.com

1


martin.ja...@gmail.com

1


devendra.tew...@gmail.com

1


jeanmarie.lemeta...@gmail.com

1


diego.sue...@arm.com

1


aeh...@gmail.com

1


kerg...@gmail.com

1


matthew...@posteo.net

1


p...@pbarker.dev

1


jae...@xilinx.com

1


vinay.m.e...@gmail.com

1


nicolas.deche...@linaro.org

1


pgowda@gmail.com

1


shac...@vdoo.com

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54774): https://lists.yoctoproject.org/g/yocto/message/54774
Mute This Topic: https://lists.yoctoproject.org/mt/85753421/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[Stephen Jolley]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 389
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.4", "3.5, "3.99" and "Future", the more pressing/urgent issues
being in "3.4" and then "3.5".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54773): https://lists.yoctoproject.org/g/yocto/message/54773
Mute This Topic: https://lists.yoctoproject.org/mt/85753401/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-rockchip][PATCH] use uuid instead of hard-coding root device

[Trevor Woerner]

On Fri 2021-09-17 @ 06:01:21 PM, Trevor Woerner via lists.yoctoproject.org 
wrote:
> Recent upstream kernel changes have made the mmc probing order unpredictable.
> Therefore, boards with both an emmc and sdmmc interface aren't guaranteed to
> boot with a hard-coded root device selected.
> 
> For example, on the rock64, with linux-yocto 5.10.y, using the uSD card (i.e.
> the sdmmc interface) about 50% of the time the boot would succeed, and roughly
> 50% of the time it wouldn't:
> 
>   ...
>   [0.612233] Waiting for root device /dev/mmcblk1p7...
>   [0.634551] mmc_host mmc1: Bus speed (slot 0) = 30Hz (slot req 
> 30Hz, actual 30HZ div = 0)
>   [0.639064] mmc_host mmc0: Bus speed (slot 0) = 5000Hz (slot req 
> 5000Hz, actual 5000HZ di)
>   [0.640007] mmc0: new high speed SDXC card at address 5048
>   [0.641176] mmcblk0: mmc0:5048 SD64G 58.0 GiB
>   [0.647610] random: fast init done
>   [0.648279] GPT:Primary header thinks Alt. header is not at the end 
> of the disk.
>   [0.648941] GPT:376479 != 121634815
>   [0.649252] GPT:Alternate GPT header not at the end of the disk.
>   [0.649796] GPT:376479 != 121634815
>   [0.650106] GPT: Use GNU Parted to correct GPT errors.
>   [0.650598]  mmcblk0: p1 p2 p3 p4 p5 p6 p7
> 
> NOTE the discrepancy between the kernel waiting for device /dev/mmcblk1p7,
> which comes from the hard-coded kernel cmdline, and the kernel probing putting
> the sdmmc on mmcblk0.
> 
> With linux-yocto 5.13.y on the rock64 using the uSD card the board would never
> boot, the sdmmc always appears on mmcblk0.
> 
> Instead of simply changing the hard-coded root device (i.e. from mmcblk0 to
> mmcblk1) switch to using partition UUIDs instead. Hard-coding the boot device
> would work with 5.13.y but would fail 50% of the time with 5.10.y; who knows
> what other kernels will do?
> 
> In any case, switching to UUIDs works regardless of board, kernel, or
> available mmc interfaces.
> 
> Boot tested on:
> - rock64
> - nanopi-m4-2gb
> - tinker-board
> - rock-pi-e
> - rock-pi-4b
> 
> Signed-off-by: Trevor Woerner 
> ---
>  conf/machine/include/nanopi-m4.inc|  2 --
>  conf/machine/include/rock-pi-4.inc|  2 --
>  conf/machine/include/rockchip-wic.inc |  4 
>  conf/machine/rock64.conf  |  3 ---
>  conf/machine/tinker-board-s.conf  |  2 --
>  conf/machine/vyasa-rk3288.conf|  2 --
>  wic/rockchip.wks  | 16 
>  7 files changed, 8 insertions(+), 23 deletions(-)

Applied to meta-rockchip master.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54772): https://lists.yoctoproject.org/g/yocto/message/54772
Mute This Topic: https://lists.yoctoproject.org/mt/85688479/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Sharing sstate cache across build nodes

[Ross Burton]

On Thu, 16 Sept 2021 at 05:34, Rusty Howell  wrote:
> Can SSTATE_DIR be shared across build hosts with different OS's  (Ubuntu 
> 18.04, ubuntu 20.04, etc, RHEL)?

If you don't use uninative, then the sstate can be in a single
directory but artifacts won't be shared. If you use uninative then the
native will be shared between the build hosts.

Basically, there's no situation where you can't use a single sstate directory.

Ross

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54771): https://lists.yoctoproject.org/g/yocto/message/54771
Mute This Topic: https://lists.yoctoproject.org/mt/85515144/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [PATCH v2 ptest-runner 2/2] main: Do not return number of failed tests when calling ptest-runner

[Alexander Kanavin]

I think we might be having an 'unresponsive maintainer' situation? How can
Anibal be reached?

Alex

On Mon, 20 Sept 2021 at 11:19, ?ukasz Majewski  wrote:

> Hi Anibal,
>
> > Hi Anibal,
> >
> > > Up till now ptest-runner2 returns number of failed tests with its
> > > exit status code. Such use case is not recommended [1] and may cause
> > > issues when there are more than 256 tests to be executed.
> > >
> > > To alleviate this issue the number of total tests with number of
> > > failed ones is printed before exit. To be more specific - failure of
> > > tests (one or more) causes ptest-runner to provide exit code of 1.
> > >
> > > One can test this change with executing:
> > > ./ptest-runner -d tests/data fail
> >
> > Gentle ping on this patch.
> >
>
> Gentle ping on this patch.
>
> Is it OK to be applied?
>
> > >
> > > Links:
> > > [1] -
> > > https://www.gnu.org/software/libc/manual/html_node/Exit-Status.html
> > >
> > > Signed-off-by: Lukasz Majewski 
> > > ---
> > > Changes for v2:
> > > - When number of failed tests is N, the ptest-runner returns value
> > > of 1 to indicate error in the execution
> > > ---
> > >  main.c | 3 +++
> > >  1 file changed, 3 insertions(+)
> > >
> > > diff --git a/main.c b/main.c
> > > index 890bc6a..bcec844 100644
> > > --- a/main.c
> > > +++ b/main.c
> > > @@ -220,6 +220,9 @@ main(int argc, char *argv[])
> > > ptest_list_remove(run, opts.exclude[i], 1);
> > >
> > > rc = run_ptests(run, opts, argv[0], stdout, stderr);
> > > +   fprintf(stdout, "TOTAL: %d FAIL: %d\n",
> > > ptest_list_length(run), rc);
> > > +   if (rc > 0)
> > > +   rc = 1;
> > >
> > > ptest_list_free_all(&run);
> > >
> >
> >
> >
> >
> > Best regards,
> >
> > Lukasz Majewski
> >
> > --
> >
> > DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
> > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> > Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email:
> > lu...@denx.de
>
>
>
>
> Best regards,
>
> Lukasz Majewski
>
> --
>
> DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lu...@denx.de
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54770): https://lists.yoctoproject.org/g/yocto/message/54770
Mute This Topic: https://lists.yoctoproject.org/mt/84946492/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [PATCH v2 ptest-runner 2/2] main: Do not return number of failed tests when calling ptest-runner

[?ukasz Majewski]

Hi Anibal,

> Hi Anibal,
> 
> > Up till now ptest-runner2 returns number of failed tests with its
> > exit status code. Such use case is not recommended [1] and may cause
> > issues when there are more than 256 tests to be executed.
> > 
> > To alleviate this issue the number of total tests with number of
> > failed ones is printed before exit. To be more specific - failure of
> > tests (one or more) causes ptest-runner to provide exit code of 1.
> > 
> > One can test this change with executing:
> > ./ptest-runner -d tests/data fail  
> 
> Gentle ping on this patch.
> 

Gentle ping on this patch.

Is it OK to be applied?

> > 
> > Links:
> > [1] -
> > https://www.gnu.org/software/libc/manual/html_node/Exit-Status.html
> > 
> > Signed-off-by: Lukasz Majewski 
> > ---
> > Changes for v2:
> > - When number of failed tests is N, the ptest-runner returns value
> > of 1 to indicate error in the execution
> > ---
> >  main.c | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/main.c b/main.c
> > index 890bc6a..bcec844 100644
> > --- a/main.c
> > +++ b/main.c
> > @@ -220,6 +220,9 @@ main(int argc, char *argv[])
> > ptest_list_remove(run, opts.exclude[i], 1);
> >  
> > rc = run_ptests(run, opts, argv[0], stdout, stderr);
> > +   fprintf(stdout, "TOTAL: %d FAIL: %d\n",
> > ptest_list_length(run), rc);
> > +   if (rc > 0)
> > +   rc = 1;
> >  
> > ptest_list_free_all(&run);
> >
> 
> 
> 
> 
> Best regards,
> 
> Lukasz Majewski
> 
> --
> 
> DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email:
> lu...@denx.de




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lu...@denx.de


pgpCDv9dmg7p4.pgp
Description: OpenPGP digital signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#54769): https://lists.yoctoproject.org/g/yocto/message/54769
Mute This Topic: https://lists.yoctoproject.org/mt/84946492/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-