From owner-freebsd-current@freebsd.org Wed Jun 6 16:26:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35E0FFD45E9 for ; Wed, 6 Jun 2018 16:26:23 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-io0-f174.google.com (mail-io0-f174.google.com [209.85.223.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C80F67C527 for ; Wed, 6 Jun 2018 16:26:22 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-io0-f174.google.com with SMTP id r24-v6so8290785ioh.9 for ; Wed, 06 Jun 2018 09:26:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=RN74gV13qn/TvWitDti1pzmTiJiW42FQvwr16ZwF/pM=; b=Nu6/M4iGXK3X58Mlfsx4WRggQUeRhCKXjLIDloC65mMasRffWeInpkFJil6KXtgHa6 oWDCi92r94T8+09YJ1rz4xbi+9FXdA/6D1f1r+zxsJXRVqzTbHG465g+q7eDQk1aye18 ELPrfl7HcYI4MlskzyLEyLH++LV3uRWpWbsq+d74Qx26SxsxDOJacnh8w6OYk0rNPncD hj7D3p985XBKb0/spoxYyWaS3TDuZ0JZy3ViSbS1fhy7AEHgziSTl/ZO32Ig2uRwargN LpabjBjiBIlq24JmEz6O6uFejPZ6Qc7xJPcXYAMzafPDl3JkzGOW2+qvS1yJ5os4p8H1 Zv3A== X-Gm-Message-State: APt69E2ZP3DfxnL1JaJ+IuRzZpLw271B2jUIkgMWJgFVkCBBhQ/EDL0s gZcbm3iY4Bp5M4jW4FUsOC/iaZit X-Google-Smtp-Source: ADUXVKLa78bC10AlQZJPw56u2SJUMbqeBg14EBxdidB9pzXALLis38haz+wLdgyZLjroc2FpRmVopg== X-Received: by 2002:a6b:3110:: with SMTP id j16-v6mr3532635ioa.249.1528302000007; Wed, 06 Jun 2018 09:20:00 -0700 (PDT) Received: from mail-io0-f172.google.com (mail-io0-f172.google.com. [209.85.223.172]) by smtp.gmail.com with ESMTPSA id s9-v6sm4516500ioa.66.2018.06.06.09.19.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jun 2018 09:19:59 -0700 (PDT) Received: by mail-io0-f172.google.com with SMTP id e15-v6so8301197iog.1 for ; Wed, 06 Jun 2018 09:19:59 -0700 (PDT) X-Received: by 2002:a6b:b5c1:: with SMTP id e184-v6mr3673706iof.267.1528301999735; Wed, 06 Jun 2018 09:19:59 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:5995:0:0:0:0:0 with HTTP; Wed, 6 Jun 2018 09:19:59 -0700 (PDT) In-Reply-To: <20180606011218.GA72167@kduck.kaduk.org> References: <20180606011218.GA72167@kduck.kaduk.org> From: Conrad Meyer Date: Wed, 6 Jun 2018 09:19:59 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: how do I use the make universe machines? To: Rick Macklem Cc: "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 16:26:23 -0000 On Tue, Jun 5, 2018 at 6:12 PM, Benjamin Kaduk wrote: > On Wed, Jun 06, 2018 at 12:47:17AM +0000, Rick Macklem wrote: >> I've heard mention of "make universe" machines multiple times, >> but have no idea how to use them? >> Is there doc on this? >> >> Thanks, rick >> ps: I'll admit I haven't looked at the developer's guide in a long time. > > I think https://www.freebsd.org/internal/machines.html sounds like > the page you're looking for. (universe is just a top-level make > target like buildworld, but will take a while on non-beefy > hardware.) Hi Rick, Yep, those are the machines you want. Note those host names listed are subdomains below the top-level freebsd.org domain. All of the 'universeNNa' hostnames are jails on a single, relatively beefy server running CURRENT, and the 'universeNNb' hostnames are all jails on a different, relatively beefy server running CURRENT. SSH credentials are the same as for freefall. Conveniently, motd on these machines contains the usual convention for running the universe target on them: Hint: env MAKEOBJDIRPREFIX=/scratch/tmp/$USER/obj \ make -s -j8 __MAKE_CONF=/dev/null tinderbox I would modify that slightly, replacing -j8 with -j$(sysctl -n hw.ncpu), in the usual case that no one else is utilizing the machine at the same time. -DNO_CLEAN might be quite useful for incremental polishing work on a patch for any previously failed arches. The clean build should finish in under an hour, IIRC. Best, Conrad