[Bug 916364] New: yast tests need to port to rspec 3.1.x or need to evaluate that
http://bugzilla.suse.com/show_bug.cgi?id=916364 Bug ID: 916364 Summary: yast tests need to port to rspec 3.1.x or need to evaluate that Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: mlin@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- In the Staging:B - https://build.opensuse.org/project/show/openSUSE:Factory:Staging:B , that has newer rspec version 3, but yast2-* tests basically unhappy with it, sounds yast tests need to port to adopt with new rspec, or at least to evaluate that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=916364 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor@suse.com --- Comment #1 from Ancor Gonzalez Sosa <ancor@suse.com> --- We are discussing the solution right now. We have being slowly preparing our tests for this, so I hope we can track down all the problems in a reasonable amount of time. BTW, url to inspect the error: https://build.opensuse.org/project/monitor/openSUSE:Factory:Staging:B?arch_x86_64=1&defaults=0&failed=1&repo_standard=1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=916364 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers@suse.de |ancor@suse.com --- Comment #2 from Ancor Gonzalez Sosa <ancor@suse.com> --- The problem was moved to staging C, so we'll have to wait for the list of failures to be ready again, but it was probably this: yast2, yast2-update, yast2-bootloader, yast2-online-update, yast2-kdump, yast2-packager yast2 is already fixed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=916364 --- Comment #3 from Max Lin <mlin@suse.com> --- staging C is totally rebuilding now, but please don't surprise if you see the yast2 had the same failure, that was due to the latest yast2 just got into Factory and I have not yet rebased staging C, I'll did it soon once Ring0 got build done. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=916364 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Ancor Gonzalez Sosa <ancor@suse.com> --- Looks like it passed the staging. Closing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=916364 http://bugzilla.suse.com/show_bug.cgi?id=916364#c6 --- Comment #6 from Swamp Workflow Management <swamp@suse.de> --- This is an autogenerated message for OBS integration: This bug (916364) was mentioned in https://build.opensuse.org/request/show/595936 Factory / yast2-iscsi-client -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com