August 2017

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 14 Aug '17

14 Aug '17

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (187 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-autoinstallation: - Caasp merge (6 days) https://github.com/yast/… [View More]

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 11 Aug '17

11 Aug '17

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (184 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-bootloader: - don't create grub_installdevice and let perl-Bootloader … [View More]

1 0

[yast-devel] article about measuring memory for part of code
by Josef Reidinger 10 Aug '17

10 Aug '17

Hi, I see this interesting article about measuring memory consumption in ruby for given part of code. Which is interesting if we want to measure memory consumption in installer and to proof if we suspect something to eat a lot of memory. Enjoy reading: https://robots.thoughtbot.com/a-crash-course-in-analyzing-memory-usage-in-r… Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] YaST: highlights of development sprint 40
by Imobach González Sosa 10 Aug '17

10 Aug '17

Hi all, We've just published the report of YaST latest development sprint with more information about the new storage layer (the merge is around the corner), dropping support for SUSE tags, etc. https://lizards.opensuse.org/2017/08/10/highlights-of-yast-development-spri… Enjoy it! Regards, Imo -- Imobach González Sosa YaST team at SUSE LINUX GmbH Blog: https://imobachgs.github.io/ Twitter: @imobachgs

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 10 Aug '17

10 Aug '17

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (183 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-bootloader: - don't create grub_installdevice and let perl-Bootloader … [View More]

1 0

[yast-devel] Re: [yast-internal] Version numbers post-SP3 (Factory / SLE-15)
by Imobach Gonzalez Sosa 09 Aug '17

09 Aug '17

On 08/09/2017 01:19 PM, Stefan Hundhammer wrote: > > The SP3 branch uses 3.2.x . > > When we keep using 3.2.x in master as well, we need to start using a > fourth digit in that branch: 3.2.x.1 etc. > > Since we are not targeting a new product, we might want to bump one of > the numbers in master: > > (a) Start with 3.3.1 > > (b) Start with 15.xxx as Jiri suggested: > (b1) 15.1 ? > (b2) 15.0.1 ? > (b3) 15.1.1 ? I like this … [View More]

1 1

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 09 Aug '17

09 Aug '17

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (182 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-apparmor: - Remove perl code dependency (5 days) https://github.com/… [View More]

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 08 Aug '17

08 Aug '17

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (181 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (18 days) … [View More]

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 07 Aug '17

07 Aug '17

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (180 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (17 days) … [View More]

1 0

[yast-devel] Defensive programming or "it doesn't change that often"?
by Lukas Ocilka 04 Aug '17

04 Aug '17

Dear Developers, I've just seen another PR fixing `The World Has Changed` issue at https://github.com/openSUSE/installation-images/pull/192 It's indeed a simple fix, no brainer, but it's not the first time I see such fix. That again raised a question that comes to my mind from time to time: Should YaST blindly write "something somewhere and just wish that it will work"? There is another way - Defensive Programming which checks that what we write actually makes sense/exists/... In this case, … [View More]

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 04 Aug '17

04 Aug '17

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (177 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (14 days) … [View More]

1 0

[yast-devel] Review Request: yast-apparmor
by Goldwyn Rodrigues 03 Aug '17

03 Aug '17

Hi, I understand you get a list of projects pending review. I am sending this across as a gentle reminder for its dependency on FATE#323380. -- Goldwyn -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 3

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 03 Aug '17

03 Aug '17

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (176 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-apparmor: - Remove perl code dependency (5 days) https://github.com/… [View More]

1 0

[yast-devel] PoC: Running integration tests / smoke tests at Travis
by Ladislav Slezak 02 Aug '17

02 Aug '17

Hi all, Short Background ----------------- I fixed a trivial bug in the Rear YaST module [1]. The module did not work at all and crashed with "Internal error" right at the start because some files were missing in the RPM package. The nasty thing is that the bug was unnoticed for 6(!!) months. And we got a bug report just after the SP3 was released... :-( Improving it ------------ So I was thinking how to improve the situation, if anybody did a smoke test and just try to run the module the … [View More]bug would have been found. That means we would need an integration test. openQA was my first idea but it's hard to maintain and we would get the result too late. But since we use Docker at Travis and we already build the YaST packages there then it should be easy to install the package and run it. Proof of Concept ---------------- I have implemented a trivial openQA equivalent using the "tmux" package which is similar to "screen". That means the tests are run using the ncurses UI which is lightweight and should work fast in Travis. Currently I can dump the screen to the Travis log (see the examples below) check what's on the screen, send keyboard presses and navigate in the workflow. For the rear module I can verify that the module starts properly, I can even change a value in the configuration, save it and then start the module again to verify it has been saved properly. This initial run shows that the module is broken [1] and displays the "Internal error" popup as reported in bugzilla. After merging the fix [2] it runs properly and runs the save and load workflow as expected, check the screen dumps in the log [3]. The integration test is implemented in a shell script [4]. It's still just a proof of concept, there are a lot of TODOs, the structure does not look nice, some functions should be moved to a separate shared file, etc... But it really shows that it could improve the test automation a lot. Advantages ---------- - Runs at Travis, the tests are run early, even _before_ we actually merge the change - Uses ncurses UI and simple "grep", no fragile screenshot comparing (It's still not ideal, but should be good enough at this point.) - You can run the same tests locally using the same Docker image => easy debugging, stable environment (more or less) - Writing smoke tests is easy even for legacy modules Disadvantages ------------- - Cannot run full installation, only modules in the installed system - So AutoYaST cannot be tested as well. On the other hand AY allows system cloning and can apply a profile to the running system so we could at least partly test the AY functionality at Travis. And many modules support interactive "configuration" mode. - Docker is container based, no HW virtualization provided, that means it cannot test HW related modules. But we can still run at least simple smoke tests that verify the module starts and displays "No printer detected" or something like that. That still makes sense. TODO/Ideas ---------- - The common functions should be shared (in yast2-devtools?), add helpers for common testing scenarios. - A shell script might not be the best tool, maybe rspec or serverspec [5] might be better. On the other hand a simple shell script has less dependencies and could be easily shared with openQA. It could run the same tests to ensure YaST still works when the external dependencies are changed. - For mocking the external tools in complex scenarios we could use shellmock [6]. What do you think about it? Any ideas, comments? Thank you in advance! [1] https://travis-ci.org/yast/yast-rear/builds/259803414#L681 [2] https://github.com/yast/yast-rear/pull/7 [3] https://travis-ci.org/yast/yast-rear/builds/260086828#L670 [4] https://github.com/yast/yast-rear/pull/8 [5] http://serverspec.org/ [6] https://github.com/gooddata/shellmock -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org [View Less]

3 4

[yast-devel] yast-rake update: send SP3 and Leap 42.3 to :Updates
by Ladislav Slezak 02 Aug '17

02 Aug '17

Hello, SLE-12-SP3 and Leap 42.3 have been released so I have updated the YaST rake tasks to submit to :Updates OBS projects now. Fixed in yast-rake-0.2.17 [1], you can install the package from YaST:Head [2] as usually. [1] https://github.com/yast/yast-rake/pull/44 [2] https://build.opensuse.org/project/show/YaST:Head -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact … [View More]

1 0

[yast-devel] want checkbox in file system formatting options for enable/disable 64bit
by Felix Miata 02 Aug '17

02 Aug '17

I would like to see a checkbox for disabling 64bit on format partition to type EXT4 running Yast2 storage. The window is a relatively small 491px tall on a 1050px tall screen, so another option should easily fit. Mke2fs's ^64bit option would not be memorable for use as arbitrary option value even if there were such a field in this window (as exists for fstab options). Most of my installations are modest size, meaning / partitions are no more than 20GB, most less than 8GB. I can't imagine 64 … [View More]

3 3

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 02 Aug '17

02 Aug '17

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (175 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-apparmor: - Remove perl code dependency (4 days) https://github.com/… [View More]

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 01 Aug '17

01 Aug '17

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-add-on: - [WIP] Ask when the added repository is unsigned (bsc#1009127) (174 days) https://github.com/yast/yast-add-on/pull/37 Pending requests in repository yast-bootloader: - Use shared RSpec examples for CWM widgets (11 days) … [View More]

1 0

Main

Development

Information

Community

Social Media

Other

YaST Development