| Message ID | 20240508153131.94270-3-ninette@thehoodiefirm.com |
|---|---|
| State | New |
| Headers | show |
| Series | M12: Improve the Charts in the Metrics View | expand |
On Wed, 2024-05-08 at 17:31 +0200, Ninette Adhikari via lists.yoctoproject.org wrote: > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#93): > https://lists.yoctoproject.org/g/yocto-patches/message/93 > Mute This Topic: https://lists.yoctoproject.org/mt/105983324/1686473 > Group Owner: yocto-patches+owner@lists.yoctoproject.org > Unsubscribe: > https://lists.yoctoproject.org/g/yocto-patches/leave/13162210/1686473/1677322349/xyzzy > [richard.purdie@linuxfoundation.org] > -=-=-=-=-=-=-=-=-=-=-=- This patch and patches 4, 7 and 8 all appeared to come through as empty unfortunately (messages with nothing in them other than the list footer). Any idea what happened to them? Cheers, Richard
Hi Richard, This is really strange that the patches are coming through as empty for you. Sorry about that! Just to be sure that we understood correctly do you mean your email client actually doesn’t display the patches? because we can see them in the email you replied to. I followed this documentation <https://docs.yoctoproject.org/contributor-guide/submit-changes.html?highlight=pull+request#sending-the-patches-via-email> to send the patches and it worked fine for previous patches. We have also pushed the patches to the yocto metrics contributors branch <https://git.yoctoproject.org/yocto-metrics/log/?h=contrib/jacobabrandner/improve_chart_page> in case you can't view the email patches. Please let me know if there is any other way to share the patches or if I should rensend the patches. Thanks so much! Best, Ninette On Thu, May 9, 2024 at 12:53 PM Richard Purdie < richard.purdie@linuxfoundation.org> wrote: > On Wed, 2024-05-08 at 17:31 +0200, Ninette Adhikari via > lists.yoctoproject.org wrote: > > > > > > -=-=-=-=-=-=-=-=-=-=-=- > > Links: You receive all messages sent to this group. > > View/Reply Online (#93): > > https://lists.yoctoproject.org/g/yocto-patches/message/93 > > Mute This Topic: https://lists.yoctoproject.org/mt/105983324/1686473 > > Group Owner: yocto-patches+owner@lists.yoctoproject.org > > Unsubscribe: > > > https://lists.yoctoproject.org/g/yocto-patches/leave/13162210/1686473/1677322349/xyzzy > > [richard.purdie@linuxfoundation.org] > > -=-=-=-=-=-=-=-=-=-=-=- > > > This patch and patches 4, 7 and 8 all appeared to come through as empty > unfortunately (messages with nothing in them other than the list > footer). > > Any idea what happened to them? > > Cheers, > > Richard > > > >
They came through empty for me too. And you can see that on the mailing list archive: https://lists.yoctoproject.org/g/yocto-patches/message/93 Try sending them to an external private email first. Alex On Mon, 13 May 2024 at 12:58, Ninette Adhikari via lists.yoctoproject.org <ninette=thehoodiefirm.com@lists.yoctoproject.org> wrote: > > Hi Richard, > > This is really strange that the patches are coming through as empty for you. Sorry about that! Just to be sure that we understood correctly do you mean your email client actually doesn’t display the patches? because we can see them in the email you replied to. > I followed this documentation to send the patches and it worked fine for previous patches. We have also pushed the patches to the yocto metrics contributors branch in case you can't view the email patches. > > Please let me know if there is any other way to share the patches or if I should rensend the patches. Thanks so much! > > Best, > Ninette > > On Thu, May 9, 2024 at 12:53 PM Richard Purdie <richard.purdie@linuxfoundation.org> wrote: >> >> On Wed, 2024-05-08 at 17:31 +0200, Ninette Adhikari via lists.yoctoproject.org wrote: >> > >> > >> > >> >> >> This patch and patches 4, 7 and 8 all appeared to come through as empty >> unfortunately (messages with nothing in them other than the list >> footer). >> >> Any idea what happened to them? >> >> Cheers, >> >> Richard >> >> >> > > _._,_._,_ > ________________________________ > Links: > > You receive all messages sent to this group. > > View/Reply Online (#117) | Reply To Group | Reply To Sender | Mute This Topic | New Topic > Your Subscription | Contact Group Owner | Unsubscribe [alex.kanavin@gmail.com] > > _._,_._,_
On Mon, 2024-05-13 at 12:57 +0200, Ninette Adhikari wrote: > Hi Richard, > > This is really strange that the patches are coming through as empty > for you. Sorry about that! Just to be sure that we understood > correctly do you mean your email client actually doesn’t display the > patches? because we can see them in the email you replied to. > I followed this documentation to send the patches and it worked fine > for previous patches. We have also pushed the patches to the yocto > metrics contributors branch in case you can't view the email patches. > > Please let me know if there is any other way to share the patches or > if I should rensend the patches. Thanks so much! It isn't just my email client, the mailing list archives also show an empty message: https://lists.yoctoproject.org/g/yocto-patches/message/93 https://lists.yoctoproject.org/g/yocto-patches/message/98 This means the messages really are coming through as empty. Ideally you'd fix the issue and then resend but failing that you can share a git branch of the patches somewhere (github or contrib repos). It isn't how we normally review patches, it makes it harder for people. Cheers, Richard
Thanks Richard and Alex for your quick response. I tested the patches to an external email and sent the patches to the mailing list again. Hope it works this time! Thanks for your patience:) Best, Ninette On Mon, May 13, 2024 at 1:05 PM Richard Purdie < richard.purdie@linuxfoundation.org> wrote: > On Mon, 2024-05-13 at 12:57 +0200, Ninette Adhikari wrote: > > Hi Richard, > > > > This is really strange that the patches are coming through as empty > > for you. Sorry about that! Just to be sure that we understood > > correctly do you mean your email client actually doesn’t display the > > patches? because we can see them in the email you replied to. > > I followed this documentation to send the patches and it worked fine > > for previous patches. We have also pushed the patches to the yocto > > metrics contributors branch in case you can't view the email patches. > > > > Please let me know if there is any other way to share the patches or > > if I should rensend the patches. Thanks so much! > > It isn't just my email client, the mailing list archives also show an > empty message: > > https://lists.yoctoproject.org/g/yocto-patches/message/93 > https://lists.yoctoproject.org/g/yocto-patches/message/98 > > This means the messages really are coming through as empty. > > Ideally you'd fix the issue and then resend but failing that you can > share a git branch of the patches somewhere (github or contrib repos). > It isn't how we normally review patches, it makes it harder for people. > > Cheers, > > Richard > >
diff --git a/README b/README new file mode 100644 index 00000000..ac2ee186 --- /dev/null +++ b/README @@ -0,0 +1,64 @@ +# yocto-metrics +Yocto Project autobuilder gathered metrics, CVEs etc. + +## Local setup +1. Clone repositories + + Clone both the report and data repo: + + ```sh + # clone yocto-autobuilder-helper + git clone git://git.yoctoproject.org/yocto-autobuilder-helper.git + + # clone yocto-metrics + git clone git://git.yoctoproject.org/yocto-metrics + ``` + +2. Generate chart data + At first we have to generate the necessary data for the charts. + For this we have to go the autobuilder repository and generate chart data. + + Go to your local clone of the autobuilder repository + Then run the following to generate the data and save it in your local yocto-metrics/patch-status directory: + + _Possibly you have to adapt your local path to yocto-metrics._ + ```sh + cd yocto-autobuilder-helper + ./scripts/patchmetrics-generate-chartdata --json "../yocto-metrics/patch-status.json" --outputdir "../yocto-metrics/patch-status/" + ``` + +3. Generate CVE report data + We need to generate CVE report data for each branch. + The following is an example showing data generated for the master branch. + You will need to run this for _every branch you need CVE data_ for. + +