/test

Better check with @marcov that the original delete was not intentional (I think it was not... but... ;-) )

@jodh-intel Ahhhhh, that explained why I spent the whole morning searching repo with chrome and couldn't find the commit. I really need to learn how to use git to do the search.

@Pennyzct - yes, git is the best way. But there is a bit of indirection since you can't search for the PR number (although you can search for the issue ;)

What I generally do is:

• Run git log -p to show the commits and the changes.
• Search (using /) for one of the the lines that is removed (in red) - for example chrony_systemd_service=.
• Then, search backwards (using ?) for ^commit to find the closest commit to that which should have the Fixes #XXX comment.

travis on ppc64le timed out.

$ .ci/setup.sh
$ travis_wait 50 .ci/run.sh


Still running (48 of 50): .ci/run.sh

The job exceeded the maximum time limit for jobs, and has been terminated.

any idea? @nitkon

Weird that ARM job passed on #312, seems like it tested master instead of the PR?

ohh, nevermind, the thing is that this workflow does not run the docker check dmesg logs errors test

I've restarted the firecracker and travis job which timed out.

Restarting travis

@Pennyzct: Yes, observed this in other projects as well. For some reason, Travis ppc64le CI runs are timing out today.

So it's all green now!

Thank you for the catch @Pennyzct. That was a rebasing mistake.