Doing what Giriraj suggest is an uggly hack, so please don't do that. Just
leave the PR and I'll re-start the tests.
On 25 September 2015 at 11:18, Stian Thorgersen <sthorger(a)redhat.com> wrote:
We're currently experiencing some unstability in the tests that
we are
working on. Don't worry about restarting the tests for failed PRs as I can
take care of that.
On 25 September 2015 at 11:11, Giriraj Sharma <giriraj.sharma27(a)gmail.com>
wrote:
> Hi,
>
> I too faced such issues. In order to re run travis-ci, I used to make two
> additional commits on top of the main commit. The first commit involved a
> minor change and the second commit involved revert of first commit. I used
> to then squash the last 3 commits into one i.e., restore the repository to
> original state. In case, if you try to push again to the upstream after
> squashing, travis-ci build will be triggered automatically.
>
> Although this might not be the best possible way, but it's at least a
> workaround.
>
> Cheers,
>
>
>
> On Fri, Sep 25, 2015 at 2:30 PM, Michael Gerber <gerbermichi(a)me.com>
> wrote:
>
>> Hi all,
>>
>> travis fails at my PR but it passes on my branch.
>> Is there a way to restart travis on a PR or do you have to create a new
>> PR?
>>
>> best
>> Michael
>>
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
>
>
>
> --
>
> Giriraj Sharma
> about.me/girirajsharma
> <
http://about.me/girirajsharma?promo=email_sig>
> Giriraj Sharma,
> Department of Computer Science
> National Institute of Technology Hamirpur
> Himachal Pradesh, India 177005
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>