| gitlab-br-bot | juergbi closed issue #662 (No warning produced for import element with configure-commands set) on buildstream https://gitlab.com/BuildStream/buildstream/issues/662 | 05:10 |
|---|---|---|
| gitlab-br-bot | juergbi merged MR !1141 (juerg/import->master: import.py: Validate config node) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/1141 | 05:10 |
| *** nimish has quit IRC | 06:39 | |
| *** alatiera has joined #buildstream | 07:01 | |
| gitlab-br-bot | juergbi merged MR !1138 (juerg/symlinks->master: Symlink fixes) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/1138 | 07:13 |
| gitlab-br-bot | juergbi opened (was WIP) MR !1139 (juerg/list-all-directories->master: Return all directories in list_relative_paths()) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/1139 | 07:17 |
| *** nimish has joined #buildstream | 07:56 | |
| *** solid_black has joined #buildstream | 08:55 | |
| *** solid_black has quit IRC | 09:06 | |
| *** solid_black has joined #buildstream | 09:06 | |
| gitlab-br-bot | juergbi opened MR !1142 (juerg/buffer-size->master: Increase read buffer size to improve performance) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/1142 | 09:12 |
| gitlab-br-bot | juergbi merged MR !1129 (snakeviz->master: contributing: snakeviz replaces pyflame+flamegraph) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/1129 | 09:20 |
| *** jonathanmaw has joined #buildstream | 09:54 | |
| *** benschubert has joined #buildstream | 09:54 | |
| *** tpollard has joined #buildstream | 10:07 | |
| *** raoul has joined #buildstream | 10:09 | |
| *** rdale has joined #buildstream | 10:14 | |
| *** lachlan has joined #buildstream | 10:38 | |
| *** lachlan has quit IRC | 10:40 | |
| *** jonathanmaw_ has joined #buildstream | 10:41 | |
| *** jonathanmaw has quit IRC | 10:42 | |
| jjardon | Hi, does buildstream releases require anything else than create a tag, create the tarball and put it at https://download.gnome.org/sources/BuildStream/? | 10:42 |
| juergbi | jjardon: if man-pages are in sync, that should be pretty much it | 10:47 |
| juergbi | (+ release mail) | 10:47 |
| *** lachlan has joined #buildstream | 10:57 | |
| *** lachlan has quit IRC | 11:08 | |
| *** lachlan has joined #buildstream | 11:08 | |
| jjardon | I wonder if we can help on release another 1.2.x; we would like to use the latest in that branch in GNOME | 11:31 |
| jjardon | we are about to enter the hard code freeze soon so It would be nice to align if possible | 11:32 |
| juergbi | I see, are further backports pending that you'd want in that release, or is it really just about a release? | 11:34 |
| juergbi | I'm not sure when exactly tristan is travelling, and whether he had planned to include further commits or just spin a release | 11:35 |
| lachlan | Hi, after some sleuthing from tlater[m] it seems that the buildstream/buildstream-fedora image and that it needs rebuilding - can this to be arranged? | 11:47 |
| tlater[m] | lachlan: I believe this has already happened | 11:48 |
| tlater[m] | Is there still trouble with the benchmarks? | 11:48 |
| lachlan | It seems to be still broken, yes | 11:48 |
| lachlan | Sane error | 11:48 |
| lachlan | * Same | 11:48 |
| tlater[m] | Hmm, I'll try to take a look this evening. We are installing the correct packages, so that shouldn't happen. Maybe the tag wasn't assigned correctly? | 11:49 |
| jjardon | juergbi: just about a new release; the bst-1.2 branch has already several fixes interesting for us | 11:49 |
| jjardon | lachlan: what is the problem with the image? | 11:50 |
| lachlan | jjardon: gcc fails | 11:51 |
| jjardon | lachlan: can you paste the logs somewhere, please? | 11:51 |
| jjardon | Can I have reviews of https://gitlab.com/BuildStream/buildstream-docker-images/merge_requests/102 , please? | 11:52 |
| lachlan | I will post the link to the buildstream build (but I have just done it locally) | 11:52 |
| lachlan | https://gitlab.com/BuildStream/benchmarks/-/jobs/159195385 | 11:52 |
| tlater[m] | jjardon (@_gimpnet_jjardon:matrix.org): It looks like the gcc-c++ and python-devel packages aren't installed. | 11:53 |
| juergbi | well, but shouldn't pyroaring be pre-installed? | 11:54 |
| jjardon | lachlan: can you as a test, install those packages manually in the .gitlab-ci.yml, to be sure that is the problem? | 11:54 |
| jjardon | juergbi: yeah, I was just thinking about that | 11:54 |
| tlater[m] | jjardon (@_gimpnet_jjardon:matrix.org): I have already tested exactly that :) | 11:54 |
| jjardon | tlater[m]: ah ok, sorry :) | 11:54 |
| jjardon | tlater[m]: builstream-docker-images has changed quite a bit; are we sure we have pyroaring there now? | 11:55 |
| tlater[m] | My guess originally was that the image failed to build and wasn't uploaded because the pipeline failed. | 11:55 |
| jjardon | yeah | 11:57 |
| jjardon | the latest x86_64 available is old: https://hub.docker.com/r/buildstream/buildstream-fedora/tags | 11:57 |
| jjardon | (23 days old) | 11:57 |
| tlater[m] | Right | 11:57 |
| tlater[m] | Odd, I set it to rebuild and it had been rebuild yesterday. | 11:57 |
| tlater[m] | Well, maybe I didn't check properly | 11:57 |
| jjardon | somehow is not being pushed | 11:58 |
| * jjardon tries to check in the logs | 11:58 | |
| jjardon | lachlan: what docker image version are you using? | 11:58 |
| jjardon | oh | 11:59 |
| lachlan | sha of base image is - a7cc9c40301b8bedaefef2485ee5473495b2a161e4c06492871bd6aa7a36aa75 | 12:00 |
| jjardon | seems we are not pusing to https://hub.docker.com anymore, but the gitlab registry? https://gitlab.com/BuildStream/buildstream-docker-images/-/jobs/159245885 | 12:00 |
| jjardon | here: https://gitlab.com/BuildStream/buildstream-docker-images/container_registry | 12:01 |
| tlater[m] | We were going to deprecate buildstream fedora | 12:01 |
| tlater[m] | Perhaps that's already happened and snuck by me. | 12:02 |
| jjardon | mm, or maybe no; let me check .gitlab-ci | 12:02 |
| jjardon | tlater[m]: are we? | 12:02 |
| jjardon | what is the replacement? | 12:02 |
| tlater[m] | jjardon (@_gimpnet_jjardon:matrix.org): A plain "buildstream" image | 12:02 |
| tlater[m] | With tags for different distros | 12:02 |
| jjardon | cool | 12:02 |
| tlater[m] | And a "latest" tag that points to the 1.2 release. | 12:03 |
| jjardon | Does that exist yet? | 12:03 |
| tlater[m] | I don't think it does | 12:03 |
| tlater[m] | But I've been a bit less attentive lately. | 12:03 |
| tlater[m] | <_gimpnet_lac "sha of base image is - a7cc9c403"> lachlan: On a side note, I think the benchmarks repo should start using a testsuite image anyway. | 12:04 |
| tlater[m] | Because the buildstream-fedora image comes with buildstream installed | 12:04 |
| tlater[m] | So we can't be 100% certain that we're running the correct package | 12:05 |
| tlater[m] | Pip is a little non-deterministic with that. | 12:05 |
| jjardon | lachlan: can you try with "latest" ? | 12:05 |
| lachlan | tlater[m] It should be something to consider certainly. | 12:05 |
| jjardon | image: buildstream/buildstream-fedora:latest | 12:05 |
| lachlan | jjardon: That is the tag that we use when we download the image | 12:06 |
| jjardon | lachlan: ugh, I'd avoid doing that: you can break your CI if you do that (as it seems already happened) | 12:07 |
| tlater[m] | Tbf, in this case the breakage occurred because of a new buildstream requirement. Not because the image changed. | 12:08 |
| tlater[m] | It broke because the image didn't change. | 12:08 |
| jjardon | sure, I think my recommendation still applies though | 12:10 |
| jjardon | so the strange thins is that "latest" is newer that the latest tag here: https://hub.docker.com/r/buildstream/buildstream-fedora/tags?page=1 | 12:10 |
| jjardon | so seems that the repo is not tagget anymore when we push a new image | 12:10 |
| laurence | does anyone have a link to the google docs of the notes from the gathering? | 12:22 |
| juergbi | laurence: https://bit.ly/2019-gathering-notes | 12:26 |
| jjardon | ah, of course | 12:27 |
| jjardon | tlater[m]: lachlan buildstream-fedora is for end users, so It installs buildstream 1.2 (that new dependency is for master only) | 12:28 |
| laurence | jjardon, thanks | 12:29 |
| tlater[m] | <_gimpnet_jja "ah, of course"> jjardon (@_gimpnet_jjardon:matrix.org): Right, that makes sense. So the change I expected half-happened. | 12:34 |
| tlater[m] | lachlan: That means the benchmarks repository must switch to a testsuite image. | 12:34 |
| tlater[m] | This one's probably closest to the current image: https://hub.docker.com/r/buildstream/testsuite-fedora | 12:35 |
| * tlater[m] hurries to a different building for his next lecture | 12:35 | |
| lachlan | tlater[m]: Thanks will have a look later | 12:36 |
| *** raoul has quit IRC | 12:36 | |
| gitlab-br-bot | LaurenceUrhegyi opened issue #901 (Remove BuildStream version 1.2 form Debian Buster packaging) on buildstream https://gitlab.com/BuildStream/buildstream/issues/901 | 12:42 |
| laurence | Regarding removing 1.2 from Debian packaging, what's the best approach? Is there anything in that ticket I've missed off? | 12:45 |
| laurence | jjardon, ? | 12:45 |
| jjardon | I think more that telling each maintainer of each distro to remove a package, the real fix is to fix buildstream docs to clearly state 1.2.x is not recommended for general consumption, and It's going to be deprecated soon | 12:46 |
| jjardon | then is distros jobs to decide | 12:47 |
| jjardon | we have quite a lot of distros packaging bst already: https://buildstream.build/install.html | 12:47 |
| laurence | yeah, that's what made me think of this | 12:48 |
| laurence | jjardon, that makes sense to me, I'll update the ticket | 12:49 |
| *** tristan has joined #buildstream | 12:51 | |
| *** nimish has quit IRC | 13:14 | |
| *** nimish has joined #buildstream | 13:14 | |
| *** tpollard has quit IRC | 13:26 | |
| *** tpollard has joined #buildstream | 13:28 | |
| *** tristan has quit IRC | 13:30 | |
| *** raoul has joined #buildstream | 13:33 | |
| benschubert | BUG: Errno 31, too many links while doing a bst build debian-stack... does someone has a clue? | 13:41 |
| Kinnison | Sounds like you're on a filesystem which limits hard links | 13:41 |
| Kinnison | Currently we link into the CASCache for getting element metadata | 13:42 |
| Kinnison | if you have too much cached, it'll splode with NTFS | 13:42 |
| Kinnison | jonathanmaw_: You did some work to mitigate this, could you explain how to benschubert ? | 13:42 |
| jonathanmaw_ | Kinnison: yep, I'll dig up the details | 13:43 |
| jonathanmaw_ | benschubert: I encountered that when running the profiling suite that Kinnison provided, and outlined how I mitigated it in https://mail.gnome.org/archives/buildstream-list/2019-January/msg00041.html | 13:45 |
| jonathanmaw_ | i.e. have a separate disk, formatted ext4; use ext2fsd to mount it in Windows; mount it into WSL; edit ~/.config/buildstream.conf to have builddir, artifactidr, etc. on the external disk | 13:46 |
| jonathanmaw_ | s/external/separate/ | 13:46 |
| jonathanmaw_ | (with the added complication that I couldn't get it to properly use the ext4 disk as non-root, so I had to install buildstream as root) | 13:47 |
| benschubert | Ah jonathanmaw_ , Kinnison ah, missing information: I'm running it on a RHEL machine :) | 13:48 |
| Kinnison | Could still be a similar issue | 13:48 |
| Kinnison | Just with larger numbers | 13:48 |
| Kinnison | e.g. debian-stack has over 75,000 elements | 13:49 |
| Kinnison | And it's possible max-links is 65536 | 13:49 |
| gitlab-br-bot | juergbi merged MR !891 (aevri/include-error->master: More user-friendly reporting on include errors) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/891 | 13:52 |
| *** nielsdg has joined #buildstream | 13:56 | |
| nielsdg | Hi everyone, I'm using a fresh install of buildstream (using pip3) and am encountering the following error | 13:57 |
| nielsdg | > AttributeError: 'Repo' object has no attribute 'reload_config' | 13:57 |
| nielsdg | Full log for reference: https://paste.gnome.org/p0iwoqmgn | 13:58 |
| benschubert | Kinnison: it's maximum for ext3 correct? not ext4 | 13:58 |
| nielsdg | Anyone who has seen something similar? | 13:58 |
| nielsdg | Python version is also 3.5.3 | 13:58 |
| Kinnison | benschubert: not sure | 13:58 |
| *** raoul has quit IRC | 14:01 | |
| *** phildawson has quit IRC | 14:02 | |
| *** phildawson has joined #buildstream | 14:04 | |
| jjardon | nielsdg: are you using buildstream master or the current release (1.2)? | 14:05 |
| *** rdale has quit IRC | 14:05 | |
| jjardon | nielsdg: If you are trying to build GNOME only 1.2 is supported | 14:05 |
| nielsdg | jjardon: Installed from pip, `bst --version` returns 1.2.3 | 14:06 |
| nielsdg | I assume 1.2.x is also supported? | 14:07 |
| jjardon | nielsdg: yep | 14:07 |
| jjardon | nielsdg: mmm, that should work; what SHA from gnome-build-meta are you trying to build? I will try to reproduce here | 14:08 |
| nielsdg | latest git master of gnome-build-meta, so 23c7e2d1d774f234411fa9452c009f8a239adc64 | 14:08 |
| jjardon | nielsdg: do you have the bst-external plugins installed as well? | 14:10 |
| Kinnison | benschubert: try: | 14:11 |
| nielsdg | jjardon: yes, as outlined in its README (git clone and then pip install) | 14:11 |
| Kinnison | benschubert: find ~/.cache/buildstream/artifacts/extract -type f -links +10000 | 14:11 |
| Kinnison | benschubert: does that show lots of things? if so, boost the 10000 to say 65000 | 14:11 |
| Kinnison | benschubert: if it still shows lots of things, then it's probably the extract hardlinking problem | 14:11 |
| nielsdg | jjardon: it gave the error `The 'buildstream-external' distribution was not found and is required by the application` otherwise | 14:11 |
| jjardon | nielsdg: do you have the ostree pygobject binding installed? | 14:12 |
| jjardon | nielsdg: gir1.2-ostree-1.0 if you use debian | 14:13 |
| jjardon | nielsdg: ostree and python3-gobject packages if you use Fedora | 14:14 |
| nielsdg | jjardon: Apparently: `gir1.2-ostree-1.0 is already the newest version (2016.15-5)` | 14:14 |
| nielsdg | jjardon: Don't know if the version might be too old (a | 14:14 |
| nielsdg | (I assume it might be that the specific property was only added in a later version) | 14:15 |
| jjardon | mmm, not sure if we have any minimum version for that, let me check | 14:16 |
| alatiera | nielsdg: what version of bst-external do you have installed? | 14:16 |
| gitlab-br-bot | jonathanmaw opened issue #902 (Element._update_state() does more stuff than it needs to when it's called) on buildstream https://gitlab.com/BuildStream/buildstream/issues/902 | 14:16 |
| jjardon | nielsdg: in the meantime, can you install the one from stretch-backports ? | 14:16 |
| jjardon | nielsdg: ah | 14:17 |
| jjardon | libostree >= v2017.8 with introspection data | 14:17 |
| nielsdg | alatiera: pip says 0.9.0 | 14:17 |
| jjardon | that was a requirement that seems got lost | 14:17 |
| nielsdg | jjardon: Thanks! I'll get a newer version and check if it works | 14:18 |
| jjardon | nielsdg: see the instructions here: https://buildstream.build/source_install.html#stretch for Stretch | 14:19 |
| jjardon | (you need to activate backports) | 14:19 |
| jjardon | Can I have reviews of https://gitlab.com/BuildStream/website/merge_requests/112, please? | 14:27 |
| benschubert | Kinnison: 65000 doesn't show anything, 64500 shows a lot of stuff :) | 14:29 |
| Kinnison | benschubert: sounds like a nlinks limit of some kind | 14:32 |
| Kinnison | benschubert: unless someone has changed it since, I googlefound: (found in same ext4.h): /* Maximal count of links to a file */ #define EXT4_LINK_MAX 65000 | 14:33 |
| benschubert | link _to_ a file? Why are we having 65k links to the same file Oo | 14:33 |
| Kinnison | Because that's how we check stuff out of the CASCache | 14:34 |
| Kinnison | we just link() to it | 14:34 |
| benschubert | so the same file would be linked out 65k time? how? | 14:35 |
| benschubert | I mean, I understand we would check it out N times, with N the number of builders, but am I missing something? | 14:40 |
| juergbi | it can happen if tons of packages contain identical files | 14:40 |
| juergbi | e.g., empty or dummy test files | 14:41 |
| benschubert | oh and the debian dummy project uses the same file all the time. Got it | 14:41 |
| *** rdale has joined #buildstream | 14:41 | |
| *** phildawson has quit IRC | 14:42 | |
| *** raoul has joined #buildstream | 14:42 | |
| Kinnison | benschubert: worse, we do the same for the metadata files | 14:42 |
| Kinnison | And every successful build has a build-result.yaml with the same content: "description: succeeded\nsuccess: true\n" | 14:42 |
| Kinnison | thassit | 14:43 |
| Kinnison | /o\ | 14:43 |
| benschubert | Is there an issue for this? | 14:43 |
| Kinnison | Dunno, jonathanmaw_ did you make one? | 14:43 |
| * Kinnison is hoping artifactasaproto will correct some of this (by lifting the duplicated metadata) | 14:43 | |
| juergbi | I'm also planning on getting rid of extract directories, reducing hardlinks | 14:44 |
| jonathanmaw_ | Kinnison: I don't think I did | 14:44 |
| juergbi | and with FUSE we shouldn't need any hardlinks anymore | 14:44 |
| *** phildawson has joined #buildstream | 14:45 | |
| benschubert | juergbi: is there a time frame for this? | 14:46 |
| juergbi | getting rid of extract directories: I was planning on doing it shortly after switching to BuildBox, but I'm wondering whether maybe we should already do it before | 14:49 |
| juergbi | I'll likely be working a bit on CAS-optimized code paths soon, maybe I can do it as part of that | 14:49 |
| gitlab-br-bot | jjardon opened MR !1143 (jjardon/distros->master: README.rst: Add table with distros with packaged buildstream) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/1143 | 14:49 |
| jjardon | nielsdg: any luck? | 14:50 |
| *** jonathanmaw_ is now known as jonathanmaw | 14:57 | |
| nielsdg | jjardon: Seems to work now. Thanks :-) | 15:04 |
| jjardon | cool :) | 15:05 |
| gitlab-br-bot | jjardon opened issue #903 (buildstream should inmediatelly fail if ostree < v2017.8 is installed) on buildstream https://gitlab.com/BuildStream/buildstream/issues/903 | 15:10 |
| gitlab-br-bot | willsalmon opened issue #904 (wrong sugestion) on buildstream https://gitlab.com/BuildStream/buildstream/issues/904 | 15:20 |
| *** johnward has left #buildstream | 15:41 | |
| jjardon | what is test-wsl? Seems it can only handle 1 concurrent build, which can be a problem when several branches are running: https://gitlab.com/BuildStream/buildstream/pipelines?scope=running&page=1 | 16:04 |
| *** lachlan has quit IRC | 16:04 | |
| jonathanmaw | jjardon: there should be two concurrent workers at the moment. I'm looking into provisioning some more runners. | 16:05 |
| jonathanmaw | jjardon: test-wsl is a test job that checks that we're not breaking functionality for users that are running buildstream from WSL | 16:07 |
| *** lachlan has joined #buildstream | 16:07 | |
| jjardon | jonathanmaw: can you please add the details about this new runner at https://wiki.gnome.org/Projects/BuildStream/Infrastructure ? | 16:09 |
| juergbi | jonathanmaw: I see only a single WSL runner online | 16:10 |
| juergbi | the 4 other WSL runners are offline | 16:10 |
| jonathanmaw | juergbi: aha, one of the runners is having network troubles | 16:12 |
| *** lachlan has quit IRC | 16:25 | |
| *** lachlan has joined #buildstream | 16:30 | |
| *** raoul_ has joined #buildstream | 16:33 | |
| *** raoul has quit IRC | 16:34 | |
| *** raoul_ has quit IRC | 16:40 | |
| *** raoul_ has joined #buildstream | 17:07 | |
| tpollard | adds68: looking forward to the MR to s/BuildStream/Buildstream ;) | 17:22 |
| adds68 | Yes, we should do that! | 17:22 |
| nielsdg | If I want to have access to systemd/systemctl inside a bst shell, how would I do that? | 17:23 |
| nielsdg | Is it possible? | 17:23 |
| nielsdg | Right now, I'm just getting "System has not been booted with systemd as init system (PID 1). Can't operate" | 17:25 |
| juergbi | adds68: I was about to mention this. inconsistent spelling of the project name is pretty bad, in my opinion. we need to change one or the other before using the logo anywhere | 17:27 |
| juergbi | nielsdg: not sure whether we could easily enable this for non-isolated shell. what's your use case? | 17:28 |
| juergbi | if it's about privileged operations such as starting/stopping services, I don't think we should even attempt to support this | 17:29 |
| adds68 | juergbi, yes i could raise an issue for people to discuss this, however i dislike BuildSream(BS) | 17:30 |
| laurence | Changing the name of the project to Buildstream would require a lot of work | 17:32 |
| laurence | needless work | 17:32 |
| laurence | It should be kept as BuildStream, and used properly and consistently. | 17:33 |
| adds68 | Lets open a ticket | 17:34 |
| laurence | did anyone else get two emails from juergbi on the ML just now? | 17:37 |
| *** lachlan has quit IRC | 17:38 | |
| gitlab-br-bot | adds68 opened issue #905 (Change the project logo away from CamelCase to Pascalcase) on buildstream https://gitlab.com/BuildStream/buildstream/issues/905 | 17:39 |
| jjardon | laurence: Seems there are not recent messages from juergbi : https://mail.gnome.org/archives/buildstream-list/2019-February/thread.html | 17:40 |
| jjardon | sorry: https://mail.gnome.org/archives/buildstream-list/2019-February/date.html | 17:40 |
| *** raoul_ has quit IRC | 17:42 | |
| laurence | I am talking about 'Re: [BuildStream] Artifact as a Proto plan ' | 17:42 |
| juergbi | laurence: I also got my own mail twice via ML, but I sent it only once and it's only once in the archive *shrug* | 17:42 |
| laurence | juergbi, ah, ok, no probs | 17:42 |
| valentind | On master there is import of "pyroaring". | 17:43 |
| laurence | at least it's not just me... | 17:43 |
| valentind | What is this? | 17:43 |
| juergbi | roaring bitmap library, optimization to reduce memory usage | 17:43 |
| valentind | juergbi, is not it missing from requirements? | 17:44 |
| valentind | I would expect tox can download it automatically. | 17:44 |
| valentind | But it does not | 17:44 |
| juergbi | no, it should be there | 17:44 |
| juergbi | do you see the issue with tox? | 17:44 |
| valentind | Strange | 17:44 |
| juergbi | if tox issue, try: tox --recreate | 17:44 |
| juergbi | pip3 install should also cover it for non-tox use | 17:45 |
| valentind | juergbi, OK thank you. Did not know about it. | 17:45 |
| valentind | I thought tox was smart enough to not need that. | 17:46 |
| *** lachlan has joined #buildstream | 17:47 | |
| *** raoul_ has joined #buildstream | 17:48 | |
| gitlab-br-bot | valentindavid opened MR !1144 (valentindavid/pull-chmod-bug->master: buildstream/_artifactcache/cascache.py: Set 0644 rights to pulled files) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/1144 | 17:54 |
| juergbi | jonathanmaw: do you know if the WSL runner is stuck? https://gitlab.com/BuildStream/buildstream/-/jobs/159524820 seems to be the runner's active job but still initializing after 2 hours according to the log | 18:14 |
| juergbi | other MRs in queue for nearly 4 hours | 18:15 |
| juergbi | we may want to temporarily make the test non-gating until we sort out the runner situation | 18:15 |
| jonathanmaw | juergbi: looked to be a network problem with that runner | 18:25 |
| jonathanmaw | I've taken it down since I don't have time to debug it | 18:25 |
| jonathanmaw | +1 on making the tests non-gating until we've sorted them out properly | 18:26 |
| *** jonathanmaw has quit IRC | 18:27 | |
| *** raoul_ has quit IRC | 18:44 | |
| *** johnward has joined #buildstream | 18:51 | |
| gitlab-br-bot | jjardon opened MR !1145 (jjardon/allow_fail_WSL->master: .gitlab-ci.yml: allow "test-wsl" to fail until runner problems are sorted out) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/1145 | 19:14 |
| *** lantw44 has quit IRC | 19:47 | |
| *** lantw44 has joined #buildstream | 20:00 | |
| *** lachlan has quit IRC | 20:17 | |
| gitlab-br-bot | juergbi merged MR !1145 (jjardon/allow_fail_WSL->master: .gitlab-ci.yml: allow "test-wsl" to fail until runner problems are sorted out) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/1145 | 21:29 |
| gitlab-br-bot | jjardon opened (was WIP) MR !1137 (jjardon/fedora_29->master: .gitlab-ci.yml: Test with current fedora release: 29) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/1137 | 21:32 |
| *** jonathanmaw has joined #buildstream | 21:43 | |
| *** jonathanmaw has quit IRC | 21:43 | |
| *** nimish has quit IRC | 21:44 | |
| *** erle- has joined #buildstream | 22:02 | |
| *** alatiera has quit IRC | 23:22 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!