Marcel Kost

There was a similar issue described in #1763, the fix however is already in the version we use.

@eribeiro Can you add the changes @ChTimTsubasa requested?

I can remember that I also noticed this problems months ago, but I never found a solution for this. It seems that travis just sometimes looses triggers and Github then...

Let's wait for the next time this occurs and then check the trigger history. (I didn't know about that)

@poojanilangekar told me it happened again: https://github.com/cmu-db/peloton/pull/1302#issuecomment-385267457 @pervazea Can you check the Github trigger history and see if we can see something there?

I see a lot of builds that get not triggered right now, even on *my* fork. I guess we can't do anything about that...

@chenboy can you take a look at this?

Great, thank you!

@pmenon I just wanted to show you that this happens already when specifying it in the travis file. But then I saw that in fact it *does* happen, but the...

The tests fail because of an incompatibility between the pre-compiled tensorflow version and protobuf, which is already discussed on the mailing list. I will leave this open, until we have...