public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers3@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: fstests@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: [PATCH] xfstests-bld: document how to add debian packages to GCE image
Date: Wed, 21 Dec 2016 10:06:28 -0800	[thread overview]
Message-ID: <1482343592-135031-2-git-send-email-ebiggers3@gmail.com> (raw)

From: Eric Biggers <ebiggers@google.com>

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 Documentation/gce-xfstests.md | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/Documentation/gce-xfstests.md b/Documentation/gce-xfstests.md
index becc23d..1b7fa3e 100644
--- a/Documentation/gce-xfstests.md
+++ b/Documentation/gce-xfstests.md
@@ -306,12 +306,14 @@ to be unpacked into a directory in /tmp instead.
 
 By default gce-xfstests uses the prebuilt image which is made
 available via the xfstests-cloud project.  However, if you want to
-build your own image, you must first build the xfstests tarball as
-described in the [instructions for building
-xfstests](building-xfstests.md).  Then run the command "gce-xfstests
-create-image".  This will create a new GCE image with a name such as
-"xfstests-201608132226" where 201608132226 indicates when the image
-was created (in this case, August 13, 2016 at 22:26).
+build your own image, you must first build a 64-bit (amd64) xfstests
+tarball as described in the [instructions for building
+xfstests](building-xfstests.md).  Then copy any additional Debian
+packages, for the amd64 architecture, you want to include in the GCE
+image into the root directory of GS_BUCKET.  Then run the command
+"gce-xfstests create-image".  This will create a new GCE image with a
+name such as "xfstests-201608132226" where 201608132226 indicates when
+the image was created (in this case, August 13, 2016 at 22:26).
 
 This image will be created as part of an image family called xfstests.
 By default, when you start a test using gce-xfstests, the most
-- 
2.8.0.rc3.226.g39d4020


             reply	other threads:[~2016-12-21 18:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 18:06 Eric Biggers [this message]
2016-12-22 17:04 ` [PATCH] xfstests-bld: document how to add debian packages to GCE image Theodore Ts'o
2016-12-28 21:21   ` Eric Biggers
2016-12-31 15:52     ` Theodore Ts'o
2017-01-07 17:00       ` Theodore Ts'o

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=1482343592-135031-2-git-send-email-ebiggers3@gmail.com \
    --to=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=fstests@vger.kernel.org \
    --cc=tytso@mit.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