4 ms·

That's great! I found the piece of code I was looking for inside "tinycv" (about OpenCV): https://github.com/os-autoinst/os-autoinst/blob/3c2f5edda09bff3246f54

That's great! I found the piece of code I was looking for inside "tinycv" (about OpenCV): https://github.com/os-autoinst/os-autoinst/blob/3c2f5edda09bff3246f5438d47ad84123a5cf151/ppmclibs/tinycv_impl.cc#L200 https://github.com/os-autoinst/os-autoinst/blob/3c2f5edda09b... I switched to Debian from Fedora a year ago during the "freeze" in the release cycle. I wonder what is the stability level of Tumbleweed compared to a standard (non-beta) Fedora or a Debian testing. Is it the good repo for Tumbleweed OpenQA test? https://github.com/os-autoinst/os-autoinst-distri-opensuse https://github.com/os-autoinst/os-autoinst-distri-opensuse

rbrownsuse 11y ago
Yes, we share one test repo amongst all the openSUSE distributions and SUSE distributions SUSE use openQA for testing their enterprise distributions too, and keeping all our tests together and reused as heavily as possible really helps in all directions (and proves the argument that maintaining openQA tests isnt hard even when dealing with multiple codebases-under-test all moving at different paces) I use Tumbleweed as my daily driver on all my machines besides my server (Leap). In 2 years I've had no problems that I didnt cause myself (eg. rm -rf /) and even then snapper saved the day and let me rollback to a working snapshot (Tumbleweed, like all openSUSE/SUSE distributions have btrfs snapshots and rollback by default) So I'd say its comparible to Fedora or Debian testing And we'd like to see more contributors, not only adding more packages and maintaining them, but to openQA also so that Tumbleweeds quality doesn't just stay at that level but gets even higher
- vmorgulis 11y ago
  Thank you a lot. I'll try Tumbleweed.