cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From DaanHoogland <>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-9334: Support jenv and pyenv t...
Date Thu, 14 Apr 2016 08:16:27 GMT
Github user DaanHoogland commented on the pull request:
    so it was a timeout:
    [INFO] Apache CloudStack Plugin - Quota Service ........... SUCCESS [ 44.634 s]
    [INFO] Apache CloudStack Framework - Spring Module ........ SUCCESS [ 38.721 s]
    [INFO] Apache CloudStack Secondary Storage Controller ..... FAILURE [10:04 min]
    [INFO] Apache CloudStack Client UI ........................ SKIPPED
    [INFO] Apache CloudStack Console Proxy - RDP Client ....... SKIPPED
    [INFO] Apache CloudStack Console Proxy .................... SKIPPED
    [INFO] Apache CloudStack Console Proxy - Server ........... SKIPPED
    [INFO] Apache CloudStack Framework - QuickCloud ........... SKIPPED
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 01:25 h
    [INFO] Finished at: 2016-04-13T22:08:13+00:00
    [INFO] Final Memory: 249M/4518M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.1:findbugs
(findbugs) on project cloud-controller-secondary-storage: Execution findbugs of goal org.codehaus.mojo:findbugs-maven-plugin:3.0.1:findbugs
failed: Timeout: killed the sub-process -> [Help 1]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR] For more information about the errors and possible solutions, please read the
following articles:
    [ERROR] [Help 1]
    [ERROR] After correcting the problems, you can resume the build with the command
    [ERROR]   mvn <goals> -rf :cloud-controller-secondary-storage
    Build step 'Invoke top-level Maven targets' marked build as failure
    [CHECKSTYLE] Skipping publisher since build result is FAILURE
    [FINDBUGS] Skipping publisher since build result is FAILURE
    [PMD] Skipping publisher since build result is FAILURE
    [DRY] Skipping publisher since build result is FAILURE
    Archiving artifacts
    Skipping Cobertura coverage report as build was not UNSTABLE or better ...
    Publishing Clover coverage report...
    No Clover report will be published due to a Build Failure
    Putting comment on the pull request
    Finished: FAILURE

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