-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Mark supervisorctl tests as unstable #10057
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
Mark supervisorctl tests as unstable #10057
Conversation
|
CC @russoz I haven't used |
Backport to stable-8: 💚 backport PR created✅ Backport PR branch: Backported as #10058 🤖 @patchback |
Mark supervisorctl tests as unstable. (cherry picked from commit a720e99)
Backport to stable-9: 💚 backport PR created✅ Backport PR branch: Backported as #10059 🤖 @patchback |
Mark supervisorctl tests as unstable. (cherry picked from commit a720e99)
Backport to stable-10: 💚 backport PR created✅ Backport PR branch: Backported as #10060 🤖 @patchback |
Mark supervisorctl tests as unstable. (cherry picked from commit a720e99)
…nstable (#10058) Mark supervisorctl tests as unstable (#10057) Mark supervisorctl tests as unstable. (cherry picked from commit a720e99) Co-authored-by: Felix Fontein <[email protected]>
…nstable (#10059) Mark supervisorctl tests as unstable (#10057) Mark supervisorctl tests as unstable. (cherry picked from commit a720e99) Co-authored-by: Felix Fontein <[email protected]>
…unstable (#10060) Mark supervisorctl tests as unstable (#10057) Mark supervisorctl tests as unstable. (cherry picked from commit a720e99) Co-authored-by: Felix Fontein <[email protected]>
Mark supervisorctl tests as unstable.
SUMMARY
They seem to fail when running all tests, but not when only the supervisorctl tests are being run. Also they are disabled for some systems, etc. I think they need a bigger overhaul.
Until that's done, marking them as
unstableshould help CI failing for everyone else because of them.ISSUE TYPE
COMPONENT NAME
supervisorctl