From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: pradeep <psuriset@linux.vnet.ibm.com>,
KVM mailing list <kvm@vger.kernel.org>,
Amos Kong <akong@redhat.com>, Jason Wang <jasowang@redhat.com>
Subject: Re: ethtool
Date: Sun, 02 Oct 2011 23:16:28 -0300 [thread overview]
Message-ID: <4E891AFC.40909@redhat.com> (raw)
In-Reply-To: <20111001090036.59dd37a5@skywalker>
On 10/01/2011 12:30 AM, pradeep wrote:
>
>
> Hello Amos, Lmr
>
> Couple of networking tests like ethtool, file_transfer..etc are not
> doing cleaning properly. Huge files are not getting deleted after the
> test. So guest running out of space for next tests.
I will investigate Pradeep, thanks for reporting the problems, recently
I have made the files created by the file transfer test smaller, to
resolve guest disk fillup problems.
https://github.com/dds/autotest/commit/a90d8905a960a39628977209e5f4531a4051b25f
I will review the tests to see if we are doing proper cleanup of the
temporary files created.
prev parent reply other threads:[~2011-10-03 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 9:57 [Autotest PATCH] virt: Only update macaddr cache when capture dhcp ACK packet Amos Kong
2011-10-01 3:30 ` ethtool pradeep
2011-10-03 2:16 ` Lucas Meneghel Rodrigues [this message]
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=4E891AFC.40909@redhat.com \
--to=lmr@redhat.com \
--cc=akong@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=psuriset@linux.vnet.ibm.com \
/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.