git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] ci: install P4 from package to fix build error

From
SZEDER Gábor <szeder.dev@gmail.com>
Date
Sep 6, 2019, 10:58 UTC
Message-ID
<20190906105825.GD32087@szeder.dev>
In-Reply-To
<20190906102711.6401-1-szeder.dev@gmail.com>
On Fri, Sep 06, 2019 at 12:27:11PM +0200, SZEDER Gábor wrote:
Show 11 quoted lines
> To test 'git-p4' in the Linux Clang and GCC build jobs we used to
> install the 'p4' and 'p4d' binaries by directly downloading those
> binaries from a Perforce filehost.  This has worked just fine ever
> since we started using Travis CI [1], but during the last day or so
> that filehost appeared to be gone: while its hostname still resolves,
> the host doesn't seem to reply to any download request, it doesn't
> even refuse the connection, and eventually our build jobs time out
> [2].
> 
> Now, this might be just a temporary glitch, but I'm afraid that it
> isn't.

Well, now would you believe it, while I was testing this patch (I even made a gitgitgadget PR to run it on Azure Pipelines! :) and touching up its log message the good old Perforce filehost sprang back to life, and the CI build jobs now succeed again even without this patch.

Show 6 quoted lines
> Let's install P4 from the package repository, because this approach
> seems to be simpler and more future proof.
> 
> Note that we used to install an old P4 version (2016.2) in the Linux
> build jobs, but with this change we'll install the most recent version
> available in the Perforce package repository (currently 2019.1).

So I'm not quite sure whether we really want this patch. It depends on how important it is to test 'git-p4' with an old P4 version, but I don't really have an opinion on that.

Previous: SZEDER GáborNext: Johannes Schindelin
Message 2 of 6 in “ci: install P4 from package to fix build error”
  1. ci: install P4 from package to fix build errorSZEDER Gábor, Sep 6, 2019
  2. SZEDER GáborSep 6, 2019
  3. Johannes SchindelinSep 9, 2019
  4. SZEDER GáborSep 10, 2019
  5. Johannes SchindelinSep 11, 2019
  6. SZEDER GáborSep 12, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.