All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jain, Sangeeta" <sangeeta.jain@intel.com>
To: "richard.purdie@linuxfoundation.org"
	<richard.purdie@linuxfoundation.org>,
	 "Jolley, Stephen K" <stephen.k.jolley@intel.com>,
	"Eggleton, Paul" <paul.eggleton@intel.com>,
	"Graydon, Tracy" <tracy.graydon@intel.com>,
	 "Erway, Tracey M" <tracey.m.erway@intel.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Cc: "Kirkiris, Nectar" <nectar.kirkiris@intel.com>
Subject: Re: QA cycle report for 2.4.4 RC1
Date: Wed, 28 Nov 2018 07:07:18 +0000	[thread overview]
Message-ID: <015AB11D45F2C442929CB2765DAE738634CF2AD2@PGSMSX110.gar.corp.intel.com> (raw)
In-Reply-To: <5a3e9c82256c75c451d6a406fe5b16db394ff9d7.camel@linuxfoundation.org>

The test cases run for 2.4.4 RC1 are same as run for 2.4 release. 


>-----Original Message-----
>From: richard.purdie@linuxfoundation.org <richard.purdie@linuxfoundation.org>
>Sent: Saturday, 24 November, 2018 12:07 AM
>To: Jain, Sangeeta <sangeeta.jain@intel.com>; Jolley, Stephen K
><stephen.k.jolley@intel.com>; Eggleton, Paul <paul.eggleton@intel.com>;
>Graydon, Tracy <tracy.graydon@intel.com>; Erway, Tracey M
><tracey.m.erway@intel.com>; yocto@yoctoproject.org
>Cc: Sangal, Apoorv <apoorv.sangal@intel.com>; Kirkiris, Nectar
><nectar.kirkiris@intel.com>
>Subject: Re: QA cycle report for 2.4.4 RC1
>
>On Fri, 2018-11-23 at 03:23 +0000, Jain, Sangeeta wrote:
>>
>> Hello All,
>>
>> This is the full report for 2.4.4 RC1:
>>
>https://wiki.yoctoproject.org/wiki/WW46_-_2018-11-14_-
>_Full_Test_Cycle_2.4.4_RC1
>>
>>
>> Summary
>>
>> All planned tests were executed.
>>
>> Total Test Executed – 3330
>> Passed Test – 3318
>> Failed Test – 8
>> Blocked Test - 4
>>
>> There were zero high priority defect.  Team had found 2 new defects.
>>
>> New Bugs
>>
>> [1] Bug 13033 -  [2.4.4RC1] [Bitbake] [Case 142] PR number is not
>> getting increased with remote server/local client mode
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13033
>>
>>  [2]Bug 13038 - [2.4.4RC1][Package Management][Getting Error Message
>> "Failed to synchronize cache for repo 'repository'"]
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13038
>
>Thanks for running the QA for this. I do have some questions/observations.
>
>Firstly, this report is a little misleading as there are only two bugs mentioned but 8
>failures. The full report shows other bugs which were for example reopened or
>already open.
In report, only new bugs are mentioned. All the bugs which are reopened/already existing are not listed in report mail but can be seen in full report.
However, if its creating any confusion/inconvenience, going forward I can mention all the failing bugs in report.

>
>Taking the above bugs first, I believe they're both manual versions of tests which
>are already automated. I believe the automated tests have passed and there
>appears to be some kind of problem with the manual execution such as the
>wrong process being documented. I'm not quite sure why these are being run
>manually? Was the list of manual tests we received from Intel incorrect?
The list manual test we run for 2.4.4 is same as we run for 2.4 release. This test case is automated later than 2.4 release and is still manual as per 2.4 test plan in Testopia. It's an irony that in Yocto Project we don't have any tracking of a test case converting into automated in which release, and no system that we can update test cases in Dot releases. I am trying to streamline the tracking of test case evolution, so as to avoid such scenarios in future.


>
>Looking at other bugs in the QA report:
>
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=12670
>
>It was reopened as it had been fixed in sumo onwards but not rocko.
>I've backported the fix to the rocko branch. I don't believe its a release blocker.
>
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991
>
>This is webkitgtk failing to build in the build-appliance and looks entirely related
>to resources in the VM. How this could have worked in the past yet fail now
>makes me wonder about whether it was in fact tested previously, whether the
>VM configuration changed or quite what happened. I don't believe its a blocking
>bug as it does seem to be a VM resource problem, not a real failure or problem
>with build-appliance.
>Its hard to tell for sure with the limited data we have though.
>
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=12240
>
>A reopened lsb testing bug but its not really showing problems with the actual
>image, just testing difficulties.
>
>
>Based on this, I think 2.4.4 is good to be released, I don't see any blocking issues.
>I would like to understand what tests are actually being run and why though.
>
>Cheers,
>
>Richard
>
Thanks & Regards,
Sangeeta Jain


  reply	other threads:[~2018-11-28  7:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23  3:23 QA cycle report for 2.4.4 RC1 Jain, Sangeeta
2018-11-23 16:07 ` richard.purdie
2018-11-28  7:07   ` Jain, Sangeeta [this message]
2018-12-04 15:57     ` richard.purdie
2018-12-04 17:03       ` Jain, Sangeeta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=015AB11D45F2C442929CB2765DAE738634CF2AD2@PGSMSX110.gar.corp.intel.com \
    --to=sangeeta.jain@intel.com \
    --cc=nectar.kirkiris@intel.com \
    --cc=paul.eggleton@intel.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=stephen.k.jolley@intel.com \
    --cc=tracey.m.erway@intel.com \
    --cc=tracy.graydon@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.