W3C home > Mailing lists > Public > public-test-infra@w3.org > October to December 2016

Re: [ACTION REQUIRED] Re: Stability testing of PRs

From: Shane McCarron <shane@spec-ops.io>
Date: Sat, 22 Oct 2016 16:20:01 -0500
Message-ID: <CAJdbnOAcsZHm7jSetmzq7VNrXYatx8c_rRrLsotnZQ2junMa3g@mail.gmail.com>
To: James Graham <james@hoppipolla.co.uk>
Cc: public-test-infra <public-test-infra@w3.org>
Oh dear.   I didn't know about that restriction.

Aren't most submitters working from forks?  And shouldn't they be?

On Sat, Oct 22, 2016 at 4:16 PM, James Graham <james@hoppipolla.co.uk>

> On 22/10/16 10:41, James Graham wrote:
> The script was failing for some reason on a number of PRs (invalid
>> responses from GitHub, mostly). I've just pushed a commit that moves
>> most of the logic into python which I hope will be more robust, or at
>> least easier to debug if things go wrong.
>> Please rebase your failing PRs on to master so that they run with the
>> latest changes.
> OK, this is still a little broken. I had forgotten that for rather obvious
> security reasons, travis doesn't share encrypted environment variables with
> PRs from forks. I'll try to think of a solution for this that doesn't make
> the experience for submitters working in forks too terrible.

Shane McCarron
Projects Manager, Spec-Ops
Received on Saturday, 22 October 2016 21:20:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:12 UTC