Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73702 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37498 invoked from network); 15 Apr 2014 16:34:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Apr 2014 16:34:14 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.83 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.83 smtp83.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.83] ([108.166.43.83:43424] helo=smtp83.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 10/D0-30922-68F5D435 for ; Tue, 15 Apr 2014 12:34:14 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 2A2F0505D9; Tue, 15 Apr 2014 12:34:11 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id AB828511A9; Tue, 15 Apr 2014 12:34:09 -0400 (EDT) Message-ID: <534D5F7F.5080604@sugarcrm.com> Date: Tue, 15 Apr 2014 09:34:07 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Julien Pauli CC: PHP Internals References: <534C2133.8010402@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] keeping unit tests green From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > So I'm OK, as soon as it is simple. > For example, I dont know Travis. So when opening the Travis page about > PHP, I see many things, red or green, and feel like lost in all those > informations. Travis is pretty simple as such - you go to https://travis-ci.org/php/php-src/builds and check out your branch (branch name is in Commit column). If it's not green, you click on the build number and get the log which says what went wrong. The failed tests are usually at the very end, and once you know the names of the tests failed, look them up in the log to find the details. With pulls on github, you just click on "Details" link and it gets you to the same log page. Setting up a fork requires some configs, but Travis docs are good enough. I might also add a wiki page on how to set up the fork in Travis a bit later. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227