beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <>
Subject [GitHub] incubator-beam pull request #1135: Add timestamps to maven output on Travis ...
Date Wed, 19 Oct 2016 21:41:38 GMT
GitHub user kennknowles opened a pull request:

    Add timestamps to maven output on Travis CI

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [x] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    I'm hoping to get some insight into the stalls, plus logs should always have timstamps
    R: @dhalperi or any committer
    Note from my random sampling of what is up with the flakiness: 100% of sampled builds
died from 10 minutes of no output during `javadoc:jar`. We really don't need Travis to be
running that anyhow, but I thought I'd add some more details to the investigation first.

You can merge this pull request into a Git repository by running:

    $ git pull travis-log

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1135
commit 00b2e8976b229706521799d839affbb8c45f5925
Author: Kenneth Knowles <>
Date:   2016-10-19T21:34:17Z

    Add timestamps to maven output on Travis CI


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message