| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
cloudstack-pull-requests #491 SUCCESS |
Sorry, something went wrong.
|
Travis is still not looking very well :( will resume soon |
Sorry, something went wrong.
|
7 successes in a row is looking better :) |
Sorry, something went wrong.
|
Are you done with this @rsafonseca ? As in; should I merge? |
Sorry, something went wrong.
|
@DaanHoogland LGTM, altough travis has been very stable today :) https://travis-ci.org/apache/cloudstack/jobs/67514846 ==== Marvin Init Successful ==== |
Sorry, something went wrong.
|
Perfect, last travis failure was just what i was referring to in the last comment, after_failure.sh printed full marvin logs, we can properly troubleshoot that issue now :) |
Sorry, something went wrong.
|
It seems like this test sometimes fails because the SSVM takes a while to startup.. the test/integration/smoke/test_secondary_storage.py:159 asserts that "Starting" != "Running" and just exits there. |
Sorry, something went wrong.
|
cloudstack-pull-requests #493 SUCCESS |
Sorry, something went wrong.
|
Mentioned issue fixed in #493 |
Sorry, something went wrong.
|
Ever since i first saw this failure I wondered... why is this considered a success?!? === TestName: test_02_sys_template_ready | Status : EXCEPTION === Fixed in the latest commit. |
Sorry, something went wrong.
|
It seems latest fix uncovered tests that were failing but actually reporting success! |
Sorry, something went wrong.
|
cloudstack-pull-requests #512 FAILURE |
Sorry, something went wrong.
|
cloudstack-pull-requests #516 FAILURE |
Sorry, something went wrong.
|
I'd say this now downloads around 99% of project dependencies before build starts |
Sorry, something went wrong.
|
cloudstack-pull-requests #519 FAILURE |
Sorry, something went wrong.
|
cloudstack-pull-requests #522 FAILURE |
Sorry, something went wrong.
|
cloudstack-pull-requests #530 FAILURE |
Sorry, something went wrong.
|
cloudstack-pull-requests #531 FAILURE |
Sorry, something went wrong.
|
cloudstack-pull-requests #532 FAILURE |
Sorry, something went wrong.
|
cloudstack-pull-requests #525 SUCCESS |
Sorry, something went wrong.
|
cloudstack-pull-requests #523 SUCCESS |
Sorry, something went wrong.
|
cloudstack-pull-requests #520 SUCCESS |
Sorry, something went wrong.
|
cloudstack-pull-requests #521 SUCCESS |
Sorry, something went wrong.
|
cloudstack-pull-requests #529 SUCCESS |
Sorry, something went wrong.
|
cloudstack-pull-requests #524 SUCCESS |
Sorry, something went wrong.
|
cloudstack-pull-requests #533 FAILURE |
Sorry, something went wrong.
Add extra echo command to make sure there's data in the pom
Add some verbosity for status checking
…uts on this phase Travis is using maven 3.2.5 and this script was setting an alternate maven path before running script Setting CATALINA_BASE and CATALINA_HOME is of no consequence while running jetty, just adds more problems
…is unavailable Check if DNS resolution is working properly when failure occurs
…rough the while loop. This will make sure nc gets restared to retry in case something nasty is happening in the running process host command not present in build env, switch to getent second phase of dep download turning some error, print failure log
This version didn't like missing <version> tag on artifacts
Sometimes after a full successful run, travis will fail due to not being able to parse tests output
Add urandom as random source in before_script.sh Remove commented lines in before_script.sh Remove commented lines in install.sh
…wn during test! Revert the fix to throw failed test on exception, will fix that in a separate branch so all the other fixes can be committed already and not raise failure on an old intermittent issue that was hidden
…ersion too low for marvin, nosetests wouldn't run and result would be success
…e dependency:resolve-plugins mojo This adds a couple more dark magic sprinkles to make sure no dependencies will be downloaded at build time
Add download for midonet and juniper stuff, this increases runtime for a few minutes, may remove in future if travis show too much overhead
|
LGTM waiting for travis to agree |
Sorry, something went wrong.
|
cloudstack-pull-requests #548 SUCCESS |
Sorry, something went wrong.
|
cloudstack-pull-requests #549 SUCCESS |
Sorry, something went wrong.
Signed-off-by: Daan Hoogland <daan@onecht.net> This closes apache#482
Fixes #466 Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
| Back | FazBrowse Home | New Git URL |
Most of the failures have been due to transient network failures, that are causing dependency artifact downloads to fail
Maven does not have a way to retry this without restarting the whole build, so the mvn dependency plugin is the best bet
Unfortunately, running a dependency:resolve on the project returns yet to be compiled dependencies, and causes it to fail...
There is an option to excludeGroupIds and excludeArtifactIds in the docs for this goal, but unfortunately they don't seem to work
This drafts a dummy pom in a quick and dirty way, just to download all the deps in one go, while retrying for RETRY_COUNT times if it fails
UPDATE: this is no longer a quick fix, as it fixes several issues with travis ;)