2020-07-23T02:10:02 *** okurz_ is now known as okurz 2020-07-23T07:57:33 *** ldevulder_ is now known as ldevulder 2020-07-23T14:37:42 hi @here: don't be surprised if you can not log in to our internet Gitlab instance any longer. In this case, you probably missed an Email which asked you to re-confirm your Email address.... 2020-07-23T14:38:09 Looks like this is a new "feature" in the latest version, to close an old security bug. 2020-07-23T14:38:37 Please check for such an Email, if gitlab.i.o.o does not let you in (and you are sure you have the right pw) 2020-07-23T14:39:10 The Email contains a special link to confirm your Email address. Once you clicked on that link, you should be able to log in agin 2020-07-23T15:20:14 kl_eisbaer1: I assume it will take a second to get that email 2020-07-23T15:20:20 because I didn't yet 2020-07-23T17:44:51 kl_eisbaer1: I'd like to merge !429, but gitlab prevents me from doing that 2020-07-23T17:46:04 my _guess_ is that the failure in the initial pipeline (which also let the automerge fail) caused this, but after a re-run it's green, and I have no idea what could still be wrong 2020-07-23T19:37:59 cboltz: let me close it and do it again 2020-07-23T19:45:38 the error message is gone, and I see a "Merge when pipeline succeeds" button - which I just clicked ;-) 2020-07-23T19:48:16 cboltz: merci. JFYI: I just removed an empty line and re-submitted.... 2020-07-23T19:48:52 yes, I've noticed that ;-) 2020-07-23T19:49:46 and I still wonder what caused the problem with the initial commit 2020-07-23T19:50:48 (especially why merging was blocked after re-running the pipeline and making it green) 2020-07-23T19:53:06 merged :-) 2020-07-23T20:33:26 software, you know? 2020-07-23T20:34:50 yeah, but I expect that most software (well, excluding games and crypto) doesn't use /dev/random for its behaviour ;-) 2020-07-23T20:36:59 cboltz: sounds like you are not working long enough with $oftware ;-) 2020-07-23T20:37:06 MergeRequests: 0 2020-07-23T20:38:29 nice :-) 2020-07-23T20:38:48 ...and just 3 issues left. 2020-07-23T20:40:08 Fro the latest one, there is already https://build.opensuse.org/package/show/openSUSE:infrastructure:gitlab/container-gitlab-runner 2020-07-23T20:41:47 But I haven't tested it, yet... 2020-07-23T20:42:37 maybe s/15.1/15.2/ ;-) 2020-07-23T20:42:53 yeah - but it's time to go to bed now. 2020-07-23T20:43:09 Another home office/schooling day is waiting for me tomorrow... 2020-07-23T20:43:54 Feel free to take over and check https://gitlab.infra.opensuse.org/infra/salt/-/blob/production/.gitlab-ci.yml against the list of packages in the container file 2020-07-23T20:44:14 I tried to have one container for all 2020-07-23T20:44:36 but meanwhile I think it might make more sense to have one container for each of the test* definitions in the .gitlab-ci.yml 2020-07-23T20:44:57 with my docker "knownledge", I better don't touch it ;-) 2020-07-23T20:45:18 well: i also use this as test-bed for my training ;-) 2020-07-23T20:45:54 What's important: all the "zypper" lines in the scripts should end up in the container file 2020-07-23T20:45:56 especially https://gitlab.infra.opensuse.org/infra/salt/-/blob/production/bin/prepare_test_env.sh 2020-07-23T20:46:14 Just think about: each current test is 2020-07-23T20:46:21 a) powering up a standard 15.2 container 2020-07-23T20:46:31 b) executing the prepare_test_env.sh script 2020-07-23T20:46:41 c) start with the individual test defined in gitlab-ci.yml 2020-07-23T20:47:14 if we can get rid of most of the parts from the prepare_test_env.sh, our runners should become much faster already 2020-07-23T20:48:29 small steps, as usual. And each step will already bring us some speed up 2020-07-23T20:49:46 but anyway - CU tomorrow ;-) 2020-07-23T20:49:52 yes, and the "zypper in" step is probably the one that brings the most benefit 2020-07-23T20:50:04 good night! 2020-07-23T20:50:11 exactly :D