On Mon, Mar 23, 2020 at 7:46 PM Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
---- On Mon, 23 Mar 2020 17:00:40 -0500 Artom Lifshitz <alifshit@redhat.com> wrote ----
Hey all,
A recent change in the whitebox-tempest-plugin [1] has broken the tempest-tox-plugin-sanity-check job (ex: [2]). The cause is a skipCheck that uses a whitebox-specific config option that had no default value and is obviously not set in any jobs outside of whitebox itself. When attempting to compare a None and an int, a TypeError is thrown. This has been fixed in [3]. The disruption should be minimal, but please don't:
1. recheck tempest until [3] merges 2. blacklist whitebox from the tempest-tox-plugin-sanity-check job :)
Thanks artom for information. We do not usually balcklist plugins until we do not know who maintain that or cannot be fixed soon. Later is rare case as sanity job just check the installation part of plugins which inclide import and config things.
Thanks for the clarification! [3] has merged, so things should be back to normal with the tempest gate.
-gmann
Cheers!
[1] https://review.opendev.org/#/c/699864/ [2] https://review.opendev.org/#/c/711049/8 [3] https://review.opendev.org/#/c/714539/