Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Yeoh Ee Peng <ee.peng.yeoh@intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] oe-selftest: runqemu: add tests for qemu boot and shutdown
Date: Tue, 10 Apr 2018 10:29:51 +0300	[thread overview]
Message-ID: <00d1380c-5cd8-b062-1abf-b09b330b04a8@linux.intel.com> (raw)
In-Reply-To: <1523295825-118054-1-git-send-email-ee.peng.yeoh@intel.com>

On 04/09/2018 08:43 PM, Yeoh Ee Peng wrote:
> QA team were testing qemu boot image and shutdown on each
> qemu architecture manually. Add automated test to test qemu boot on
> ext4 and nfs, finally check that it can shutdown properly.
> 
> Original runqemu tests was dedicated for MACHINE=qemux86-64 and
> it was testing various live image (iso and hddimg) will be able
> to boot while live image was not supported on all qemu architecture.
> 
> The new tests were designed as a separate class as this tests
> focus on testing qemu boot and shutdown on each qemu architecture.
> Furthermore, this tests focus on testing qemu could shutdown
> as expected.

1. I believe the clock on the machine that you use to send the patches 
isn't set correctly, it seems to be several hours in the past.

2. What I meant is that you comment the source code itself, not write a 
longer commit message. So that anyone reading the actual file can 
quickly figure out why there are two classes and what they test. 
Basically take the above, and write it down as comments in the actual 
file; take your time to write a nice, clear explanation (similar to what 
we discussed). Then the commit message can be more brief, basically the 
first paragraph above is enough.

The reason for this is that commit history is less obvious or convenient 
to use when you want to find explanations. You can certainly use 'git 
log <filename>', but it comes with lots of irrelevant commits, and if 
the code was restructured in the past, then the history of changes stops 
there.

Alex


  parent reply	other threads:[~2018-04-10  7:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 17:43 [PATCH] oe-selftest: runqemu: add tests for qemu boot and shutdown Yeoh Ee Peng
2018-04-10  1:01 ` Yeoh, Ee Peng
2018-04-10  7:00 ` Anuj Mittal
2018-04-10  7:24   ` Yeoh, Ee Peng
2018-04-10  7:29 ` Alexander Kanavin [this message]
2018-04-10  7:39   ` Yeoh, Ee Peng
2018-04-10  9:41 ` Richard Purdie
2018-04-10 10:01   ` Yeoh, Ee Peng
  -- strict thread matches above, loose matches on Subject: below --
2018-04-10  1:28 Yeoh Ee Peng
2018-04-20  7:15 ` Richard Purdie
2018-04-20  8:27   ` Yeoh, Ee Peng
2018-04-09  3:32 Yeoh Ee Peng
2018-04-09 12:34 ` Alexander Kanavin
2018-04-10  0:57   ` Yeoh, Ee Peng

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=00d1380c-5cd8-b062-1abf-b09b330b04a8@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=ee.peng.yeoh@intel.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox