>>>>> Steinar Bang <[email protected]>: > I emailed support at travis, and the travis-ci people enabled debug on > my build. > https://docs.travis-ci.com/user/running-build-in-debug-mode/
> With the debug mode I could ssh in and run the individual steps of the > build. > What I saw when debugging, was that the build progresses right through > the place it was stuck in the regular build. [snip!] So I tried just triggering the build again, and this time the build ran right through the pax exam test that had timed out earlier, and failed in the deploy (because the deploy repository had been lost in the merge of the react branch into master). I triggered the build again and this time it failed because an experiment with using rest-maven-plugin to "ping" karaf that a new snapshot has arrived that had been removed from master was reintroduced by the merge. I triggered the build for the third time and this time it worked without failing.
