-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Db 11134 4 #5697
base: master
Are you sure you want to change the base?
Db 11134 4 #5697
Conversation
jenkins please test upgrades @cdh6.3.0 |
TEST SUCCEEDED +1 |
…nes/upgrade-testing - check_upgrade.sh {VERSION} {additional start-splice-cluster parameters}" - create_upgrade_targz.sh {VERSION} {test/upload} {additional start-splice-cluster parameters}
jenkins please test upgrades @cdh6.3.0 |
TEST SUCCEEDED +1 |
jenkins please test upgrades @cdh6.3.0 |
TEST SUCCEEDED +1 |
jenkins please test upgrades @cdh6.3.0 |
TEST SUCCEEDED +1 |
jenkins please test upgrades @cdh6.3.0 |
TEST SUCCEEDED +1 |
3 similar comments
TEST SUCCEEDED +1 |
TEST SUCCEEDED +1 |
TEST SUCCEEDED +1 |
@@ -495,6 +497,10 @@ | |||
<includes> | |||
<include>**/*IT.java</include> | |||
</includes> | |||
<excludes> | |||
<exclude>com/splicemachine/derby/impl/sql/execute/upgrade/UpgradeTestIT.java | |||
</exclude> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can rename UpgradeTestIT to a name not ending with IT or Test, to avoid excluding it from IT
* as they are only mean to be run with the check_upgrade.sh script. | ||
* | ||
* e.g. | ||
* bash pipelines/upgrade-testing/check_upgrade.sh 3.1.0.2000 -T 4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran this command, but -T option is not accepted by ./start-splice-cluster
./start-splice-cluster: illegal option -- T
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, -T was only introduced in 3.x.0.2001, so this doesn't work.
cat platform_it/splice.log | grep 'Running upgrade script' | ||
else | ||
echo "!!! UPGRADE FAILED !!!" | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sometimes an upgrade problem shows up after a restart. It would be nice if you can restart splice and run the test again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well i thought what i am doing IS a restart, no?
do you mean i should do
- get the platform_it of 3.1.0.1971
- start-splice-cluster -l
- start-splice-cluster -l # again
?
jenkins please test branch @cdh6.3.0,skipTestsLongerThan2Minutes #upgrade:3.2.0.2000 |
jenkins please test branch @cdh6.3.0,skipTestsLongerThan2Minutes #upgrade:3.1.0.2000 |
TEST SUCCEEDED +1 |
jenkins please test branch @cdh6.3.0,skipTestsLongerThan2Minutes #upgrade:3.1.0.2000 |
TEST SUCCEEDED +1 |
test