-
Notifications
You must be signed in to change notification settings - Fork 143
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
[requests/providers_spec.rb] Jansa approved spec #946
Conversation
There has been a bit of a saga with these specs: - ManageIQ#933 (comment) - ManageIQ#933 (comment) And it mostly ties in with some code that was updated for kasparov and up for `aggregate_vm_cpus`, but wasn't backported to `jansa` (which was probably the right choice). However, it caused the specs to behave differently on the two branches, and thus fail on `jansa`. The nice part about these originally is that these specs very much replicated what we were seeing here: ManageIQ#923 (comment) But since that isn't valid for both branches, it is better to use specs that are suited for both branches.
@miq-bot add_label test Hey LJ, I think you are best suited for double checking that these new specs are representative of what we ran into with #923 previously. I need to re-run this spec on |
Checked commit NickLaMuro@6d858a3 with ruby 2.6.3, rubocop 0.82.0, haml-lint 0.35.0, and yamllint |
@jrafanie also, here are some hopefully easier instructions for setting up an environment to test what I was talking about in #946 (comment)
From there, you should be able to repeat the testing you did for #923 but just change the attributes in the request to what is in the specs here:
|
/cc @simaishi |
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 have confirmed that this PR recreates nearly the same exact problem from #923. I'm good with making the test master / jansa compatible to avoid pulling back other changes to jansa elsewhere for the purposes of a single set of tests.
Oh right, I forgot |
[requests/providers_spec.rb] Jansa approved spec (cherry picked from commit 4303f09)
Jansa backport details:
|
[requests/providers_spec.rb] Jansa approved spec (cherry picked from commit 4303f09)
Kasparov backport details:
|
There has been a bit of a saga with these specs:
And it mostly ties in with some code that was updated for kasparov and up for
aggregate_vm_cpus
, but wasn't backported tojansa
(which was probably the right choice).However, it caused the specs to behave differently on the two branches, and thus fail on
jansa
. The nice part about these originally is that these specs very much replicated what we were seeing here:#923 (comment)
But since that isn't valid for both branches, it is better to use specs that are suited for both branches.
Links
jansa
branch failure report: [Renderer] Fix duplicate includes with extra_cols #933 (comment)jansa
: change aggregation mixin methods into virtual attributes manageiq#20149QA steps
Pull down a local copy of this repo
Checkout the merge commit prior to my fix from [Renderer] Fix duplicate includes with extra_cols #933 being added to
master
Override the
manageiq-api
gem inbundler.d/
From there, you should be able to repeat the testing you did for #923 but just change the attributes in the request to what is in the specs here: