Revision history [back]

first: don't worry !

it happens, it's not your fault, and devs know about it.

usually, failed tests restart again, after some time.

if you're in a hurry, you could do a

git commit --amend

(this will trigger an interactive rebase) , then a forced push:

git push -f origin my-branch

first: don't worry !

it happens, it's not your fault, and devs know about it.

usually, failed tests restart again, after some time.

just wait a bit, if you're in a hurry, they don't restart on their own, you could do a

git commit --amend

(this will trigger an interactive rebase) , then a forced push:

git push -f origin my-branch

first: don't worry !

it happens, it's not your fault, and devs know about it.it

(there is justice in nature here, it happens to them, too ;).

usually, failed tests restart again, after some time.

just wait a bit, if they don't restart on their own, you could do a

git commit --amend

(this will trigger an interactive rebase) , then a forced push:

git push -f origin my-branch

to re-trigger the buildbots.

first: don't worry !

it happens, it's not your fault, and devs know about it

(there is justice in nature here, it happens to them, too ;).

usually, failed tests restart again, after some time.

just wait a bit, if they don't restart on their own, you could do a

git commit --amend

(this will trigger an interactive rebase) , then a forced push:

git push -f origin my-branch

to re-trigger the buildbots.