Re: [OE-core] Yocto Project Status WW07'20

[Jain, Sangeeta]

Planned upcoming dot releases:

  *   YP 2.7.3 built and in QA

I didn't see any notification for this build. Am I missing something?

Thanks,
Sangeeta

From: openembedded-core-boun...@lists.openembedded.org 
 On Behalf Of 
sjolley.yp...@gmail.com
Sent: Wednesday, 19 February, 2020 12:10 AM
To: yo...@yoctoproject.org; openembedded-core@lists.openembedded.org
Subject: [OE-core] Yocto Project Status WW07'20


Current Dev Position: YP 3.1 M3

Next Deadline: YP 3.1 M3 build date 2/24/2020


Next Team Meetings:

  *   Bug Triage meeting Thursday Feb. 20th  at 7:30am PDT 
(https://zoom.us/j/454367603)
  *   Monthly Project Meeting Tuesday Mar. 3rd  at 8am PDT 
(https://zoom.us/j/990892712)
  *   Weekly Engineering Sync Tuesday Feb. 18th at 8am PDT 
(https://zoom.us/j/990892712)
  *   Twitch - Next event is Tuesday Mar. 10th at 8am PDT 
(https://www.twitch.tv/yocto_project)


Key Status/Updates:

  *   The project recently updated its git hosting infrastructure and there 
were some issues encountered with the cgit http/https repository sharing. Those 
issues should now be resolved, apologies if they caused issues for anyone. The 
git:// protocol sharing was unaffected.
  *   YP 3.0.2 rc2 is in QA with the report due soon.
  *   We continue to see a small number of reproducibility issues with master 
which need resolving for green builds (in particular gstreamer and perl).
  *   A significant memory usage issue was identified during bitbake parsing 
where memory usage would grow in each parser thread linearly per number of 
recipes parsed. This would therefore particularly affect large numbers of 
layers, multilibs and multiconfig. The fix has merged into bitbake along with 
the corresponding zeus and warrior branches. For one test case it reduced peak 
memory usage during parsing for 5 multiconfigs from 20GB to 2GB.
  *   Warrior patches for 2.7.3 are out for review.
  *   With the git infrastructure issue updated, we now have centos8 workers 
added to the autobuilder.
  *   We are making various queued changes to the autobuilder configuration to 
fix bugs, improve efficiency and test coverage but this may result in some test 
result instability as we test and resolve issues.
  *   We're collecting a list of companies, products and projects which use the 
Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users 
Please add any you know are missing (or email Richard/Stephen who can add).
  *   The triage team is worried about attendance at triage meetings and the 
project is finding it hard to find people to help fix bugs. If anyone is 
willing to work on bugs, assistance would be greatly appreciated.


YP 3.1 Milestone Dates:

  *   YP 3.1 M3 build date 2/24/2020
  *   YP 3.1 M3 release date 3/6/2020
  *   YP 3.1 M4 build date  3/30/2020
  *   YP 3.1 M4 release date  4/24/2020


Planned upcoming dot releases:

  *   YP 2.7.3 built and in QA
  *   YP 2.7.3 release date 2/21/2020
  *   YP 3.0.2 build date  2/3/2020
  *   YP 3.0.2 release date 2/14/2020


Tracking Metrics:

  *   WDD 2710 (last week 2728) 
(https://wiki.yoctoproject.org/charts/combo.html)
  *   Poky Patch Metrics

 *   Total patches found: 1360 (last week 1361)
 *   Patches in the Pending State: 546 (40%) [last week 547 (40%)]


The Yocto Project's technical governance is through its Technical Steering 
Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC


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!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
*Cell:(208) 244-4460
* Email:  sjolley.yp...@gmail.com

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] QA cycle report for 2.7 RC2

[Jain, Sangeeta]

Hi Armin,

From: akuster808 
Sent: Friday, 26 April, 2019 10:30 PM
To: Jain, Sangeeta ; 'yo...@yoctoproject.org' 
; Eggleton, Paul ; 
'richard.pur...@linuxfoundation.org' ; 
'Michael Halstead' ; Erway, Tracey M 
; 'sjolley.yp...@gmail.com' 
; openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] QA cycle report for 2.7 RC2

Sangeeta,

On 4/25/19 11:27 PM, Jain, Sangeeta wrote:

QA cycle report for 2.7 RC2:


  1.  No high milestone defects.
  2.  Test results are available at following location:
*For results of all automated tests, please refer to results at public 
AB [1].
*For other test results, refer to attachment [2].
*For test report for test cases run by Intel and WR team, refer 
attachment [3]
Since "compliance-test.compliance-test.LSB_subset_test_suite" was run, can you 
share the changes made to /opt/lsb-test/session file?

For "compliance-test.compliance-test.LSB_subset_test_suite", we follow the 
procedure as mentioned at https://wiki.yoctoproject.org/wiki/BSP_Test_Plan
Under compliance section.  Changes to /opt/lsb-test/session file are also 
handled by script "compliance_test.py" (link to which you can find in wiki page 
mentioned)


Can I get clarification on how 
"compliance-test.compliance-test.stress_test_-_ltp_-Beaglebone" was run?

To run stress test, we use "./runltp -f crashme" command.
Stress test for Beaglebone is run by Windriver team. Adding Yi Zhao in mail.



Regards,
Armin

*For full test report, refer attachment [4]

  1.  No new defects are found in this cycle.
  2.  No existing issues observed in this release
  3.  No ptests are failing in this release which were passing in previous 
release. No timeout issues.

QA Hint: One failure was observed on public AB:

testseries | result_id : qemuppc | oeselftest_centos-7_qemuppc_20190414221329
runqemu.QemuTest.test_qemu_can_shutdown


No bug filed for this issue, as it appears to be an intermittent failure and 
worked on rc1 test run.

=== Links 

Link to testresults:

[1] - https://autobuilder.yocto.io/pub/releases/yocto-2.7.rc2/testresults/

[2] - 2.7_RC2_results_merged.zip

[3] - 2.7_ rc2_intel_wr_merged_report

[4] - 2.7 _rc2_full_report

Thanks & Regards,
Sangeeta Jain




-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] QA cycle report for 2.7 RC2

[Jain, Sangeeta]

QA cycle report for 2.7 RC2:


  1.  No high milestone defects.
  2.  Test results are available at following location:
*For results of all automated tests, please refer to results at public 
AB [1].
*For other test results, refer to attachment [2].
*For test report for test cases run by Intel and WR team, refer 
attachment [3]
*For full test report, refer attachment [4]

  1.  No new defects are found in this cycle.
  2.  No existing issues observed in this release
  3.  No ptests are failing in this release which were passing in previous 
release. No timeout issues.

QA Hint: One failure was observed on public AB:

testseries | result_id : qemuppc | oeselftest_centos-7_qemuppc_20190414221329
runqemu.QemuTest.test_qemu_can_shutdown


No bug filed for this issue, as it appears to be an intermittent failure and 
worked on rc1 test run.

=== Links 

Link to testresults:

[1] - https://autobuilder.yocto.io/pub/releases/yocto-2.7.rc2/testresults/

[2] - 2.7_RC2_results_merged.zip

[3] - 2.7_ rc2_intel_wr_merged_report

[4] - 2.7 _rc2_full_report

Thanks & Regards,
Sangeeta Jain

<>


2.7_rc2_intel_wr_merged_report
Description: 2.7_rc2_intel_wr_merged_report


2.7_rc2_full_report
Description: 2.7_rc2_full_report
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core