Details
Minor
Description
See for example here:
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-debian6-x86/builds/2119/steps/test_3/logs/stdio
Unlike other package tests, this one does not use conditional 'galera-' substring in package name, so it attempts to install the standard mariadb-server even on the Galera tree, and fails because it cannot find the package:
Reading package lists... + sudo sh -c 'DEBIAN_FRONTEND=noninteractive MYSQLD_STARTUP_TIMEOUT=180 apt-get install --allow-unauthenticated -y mariadb-server mariadb-test' Reading package lists... Building dependency tree... Reading state information... E: Package 'mariadb-server' has no installation candidate Command exit 100
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Yes, that is what is happening.
For this task, should I go ahead and add the necessary line for mariadb-galera-server-5.5 to be installed? My only hesitation is that if this test passes on non-Galera builds, then there's something in the galera packages that is not right.
Lets not. The test will fail anyway due to MDEV-4228, just like upgrade2 does.
But upgrade2 has this mariadb-
server-5.5 addition, so it only throws the error about mariadb-test:
https://buildbot.askmonty.org/buildbot/builders/kvm-deb-debian6-x86/builds/2136/steps/test_2/logs/stdio
At the same time, 'upgrade' test, which does not attempt to install mariadb-test, works just fine without mariadb-galera-server-5.5:
https://buildbot.askmonty.org/buildbot/builders/kvm-deb-debian6-x86/builds/2136/steps/test_1/logs/stdio
So maybe the two errors in 'nm' test are related and the one about mariadb-galera-server-5.5 will be gone after MDEV-4228 is fixed. At least we'll see right away after the fix if there is another problem or not, so lets keep it as is for now.
this task is complete
>> The second error is different. I tried a run adding mariadb-test-5.5 to the list and got the following error:
>> E: Package 'mariadb-test-5.5' has no installation candidate
>> So my guess is it isn't being created or something.
We have a bug about mariadb-test + mariadb-galera-server, I suppose it's the same one:
MDEV-4228