From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Owen Hilyard <ohilyard@iol.unh.edu>
Cc: "dts@dpdk.org" <dts@dpdk.org>,
"lijuan.tu@intel.com" <lijuan.tu@intel.com>
Subject: RE: [PATCH v3 2/3] update files depending on tests/util
Date: Wed, 20 Apr 2022 08:45:35 +0000 [thread overview]
Message-ID: <8ce8a0874e4744ab8f56b5ca6163bc64@pantheon.tech> (raw)
In-Reply-To: <CAHx6DYC=b58zA+YG9wZ-We28ESf6nZtxdxxr96HAzF7gAZZ6Pw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]
From: Owen Hilyard <ohilyard@iol.unh.edu>
Sent: Thursday, April 14, 2022 9:54 PM
To: Juraj Linkeš <juraj.linkes@pantheon.tech>
Cc: dts@dpdk.org; lijuan.tu@intel.com
Subject: Re: [PATCH v3 2/3] update files depending on tests/util
I moved the files over and ran the formatter, which produced a diff large enough that the mailing list rejected it when I bundled it with the first commit. I could split things up more, but that would lead to an extra 2 or 3 patches in this series that contain formatting unrelated to the problem, simply because unformatted patches are getting merged. I hadn't anticipated needing granularity in the formatter because nothing except what you just worked on was supposed to be changing when you ran it, and the tools we're using don't support parts of a file.
[Juraj] Well you could've just changed this one thing manually. The formatting of whole files shouldn't be done here.
I don't want to have to keep submitting "ran the formatter" patches every week or two, since that will lead to a very messy git history. I could submit one more and rebase this series on top of it, which would let me send it in as two organized commits. Thoughts?
[Juraj] What we should do is have a system that prevents unformatted files from being accepted (I understand we formatted the and now they're improperly formatted - that shouldn't happen, although that could be because Lijian ran format.sh without pylama config?). A CI check which we're working on is sufficient with maintainers adhering to it (i.e. notifing authors that it's indeed necessary to properly format their submissions). Once we have the CI check, only then it makes sense to reformat everything. After that, we should notify the authors of patches in review to rebase and reformat their patches.
On Thu, Apr 14, 2022 at 1:40 AM Juraj Linkeš <juraj.linkes@pantheon.tech<mailto:juraj.linkes@pantheon.tech>> wrote:
> diff --git a/framework/dut.py b/framework/dut.py index 6a8fc957..83f0d7a2
> 100644
> --- a/framework/dut.py
> +++ b/framework/dut.py
> @@ -46,7 +46,7 @@ from .settings import LOG_NAME_SEP, NICS from
> .ssh_connection import SSHConnection from .test_result import ResultTable
> from .utils import RED, remove_old_rsa_key -from .virt_resource import
> VirtResource
> +from framework.virt_resource import VirtResource
And this also didn't get addressed, I guess you just added the commit in v3.
[-- Attachment #2: Type: text/html, Size: 6375 bytes --]
next prev parent reply other threads:[~2022-04-20 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 14:54 [PATCH v3 1/3] framework: Move test-specific files to test directory ohilyard
2022-04-13 14:54 ` [PATCH v3 2/3] update files depending on tests/util ohilyard
2022-04-14 5:40 ` Juraj Linkeš
2022-04-14 19:53 ` Owen Hilyard
2022-04-20 8:45 ` Juraj Linkeš [this message]
2022-04-13 14:54 ` [PATCH v3 3/3] all: ran formatter ohilyard
2022-04-14 5:39 ` [PATCH v3 1/3] framework: Move test-specific files to test directory Juraj Linkeš
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=8ce8a0874e4744ab8f56b5ca6163bc64@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=ohilyard@iol.unh.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).