On 18 February 2013 14:56, Mateusz Loskot <[email protected]> wrote: > On 18 February 2013 14:07, Vadim Zeitlin <[email protected]> wrote: >> On Mon, 18 Feb 2013 13:53:27 +0000 Mateusz Loskot <[email protected]> wrote: >> >> ML> It should work automatically. >> >> I didn't realize it was as smart as this, sorry, I should have just waited >> a bit instead of asking. > > Yes, it's pretty & cool :) > > Here is full story: > http://about.travis-ci.org/blog/2012-09-04-pull-requests-just-got-even-more-awesome/ > > The problem is that I don't know how to manually 'refresh' the build > status for a pull. > So, in this case, even if it wasn't your pull request that broken the > build (it was my commit before), > your pull request is still marked as failing, and I don't know how to > get it refreshed. > There are some manual build mechanisms in Travis, but I haven't > learned about them yet. > So, we have to ignore the status below your pull request at > > https://github.com/SOCI/soci/pull/73
By the way, just noticed the build failed status "X Failed — The Travis build failed (Details)" has disappeared. Must be that once pull has been merged, no status is displayed. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
