Skip to content
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

Fixes #15653: Missing migration script for vacuum change #2056

Conversation

fanf
Copy link
Member

@fanf fanf commented Sep 6, 2019

@Normation-Quality-Assistant
Copy link
Contributor

This PR breaks qa-test

-- stdout -- 
Branch 'branches/rudder/5.0' set up to track remote branch 'branches/rudder/5.0' from 'NRM'.
Your branch is up to date with 'NRM/branches/rudder/5.0'.
Already up to date.
Already up to date.
[...]
   b680d9b7..b2485e27  branches/rudder/5.1 -> NRM/branches/rudder/5.1
   b680d9b7..b2485e27  master              -> NRM/master
 * [new tag]           5.0.13-6            -> 5.0.13-6
 * [new tag]           5.0.13-7            -> 5.0.13-7
Switched to branch 'branches/rudder/5.0'
Switched to a new branch '5.0_test'
+ find ./rudder-server-relay/SOURCES/relay-api/relay_api -name '*.py'
+ xargs pylint -E --disable=C,R,no-member,no-name-in-module --persistent=n
No config file found, using default configuration

You should run ./qa-test in your repository to make sure it works.
You can also run rudder-dev merge https://github.com/Normation/rudder-packages/pull/2056 --test to test with upmerging.
After this, you can remove the qa: Can't merge ta
-- Your faithful QA (https://ci.normation.com/jenkins/job/merge-accepted-pr/14530/console)

@fanf
Copy link
Member Author

fanf commented Sep 6, 2019

OK, merging this PR

@fanf fanf merged commit 305e411 into Normation:branches/rudder/5.0 Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants