IRC logs for #buildstream for Tuesday, 2019-04-23

*** nimish2711 has joined #buildstream02:03
*** tristan has quit IRC04:56
*** tristan has joined #buildstream05:18
*** kapil___ has joined #buildstream05:39
*** alatiera has joined #buildstream06:20
*** bochecha has joined #buildstream06:41
*** ChanServ sets mode: +o tristan06:47
tristanHmmm, here is another INTERNALERROR> https://gitlab.com/BuildStream/buildstream/-/jobs/20060065206:52
tristanAlso, whats with this buildstream-bastion-overnight runner ? taking soo long to start: https://gitlab.com/BuildStream/buildstream/-/jobs/20060066206:53
tristanMaybe it *really* only runs in the nighttime ?06:53
tristanHmmm, any idea about this bastion ?07:21
tristanI'm seeing: ERROR: Preparation failed: exit status 107:21
tristanafter not starting in a long time07:21
*** tristan has quit IRC07:32
*** toscalix has joined #buildstream07:52
*** tristan has joined #buildstream07:53
*** ChanServ sets mode: +o tristan07:58
*** rdale has joined #buildstream08:26
*** tpollard has joined #buildstream09:03
*** jonathanmaw has joined #buildstream09:07
gitlab-br-botphildawson opened MR !1307 (phil/move-integration-cache-to-testing->master: Make Integration cache fixture available in testing package) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/130709:18
phildawson_Do the buildstream/buildstream:nightly docker images get automatically updated or need manually updating?09:45
phildawson_Either way, I need there to be a new nightly image, does anyone know how I can go about making this happen?09:47
benschubertphildawson_: hey, do you remember why you added ïnclude_package_data"in setup.py ?10:05
phildawson_Let me take a quick look to remind myself10:07
phildawson_Okay, so I added when making the templated source tests available. I think I added it to quickly make the data files necessary for the templated source tests in buildstream.testing be installed along with buildstream. I meant to go back and do that properly before making an MR out of it, but clearly missed it :/10:13
*** cs-shadow has joined #buildstream10:14
*** alatiera has quit IRC10:15
*** alatiera_ has joined #buildstream10:15
*** alatiera_ is now known as alatiera10:16
*** tristan has quit IRC10:22
*** tristan has joined #buildstream10:24
benschubertphildawson_: ok, because it's preventing me from packaging BuildStream using source distributions (wheels do work fine though??) and I don't really know what's the problem, just know that removing it will allow me to run buildstream x)10:31
benschubertphildawson_: what are the things you wanted to cleanup there?10:31
phildawson_benschubert, I'll quickly tidy that up now.10:31
benschubertoh ok great, let me know when you have a PR :)10:31
phildawson_Will do :)10:31
phildawson_I wonder what's going on there though10:32
benschubertI wish I knew10:32
cs-shadowphildawson_: the nightly images do get rebuilt. They sometimes get hit by flaky CI, as they did today10:33
cs-shadowhttps://gitlab.com/BuildStream/buildstream/issues/1008 for the missing package data in case you hadn't noticed before10:34
phildawson_Cheers cs-shadow.10:35
* cs-shadow just hit the rebuild button10:35
phildawson_I wasn't sure, because it had been 10 days since the latest version.10:36
cs-shadowyeah, the CI failures happen more often than ideal :/ If i find time at some point, i need to look into that10:37
* cs-shadow isn't sure what to do when `dnf install` seg faults : https://gitlab.com/BuildStream/buildstream-docker-images/-/jobs/200757345 10:38
phildawson_erm, that's worrying.10:39
cs-shadowseems to happen rather consistently, on the same fedora 30 image. that also explains no updates for the past week or so10:41
* phildawson_ wonders if it could be to do with this: https://bit.ly/2W10fwH10:51
benschubertphildawson_: last updated upstream: 19 days ago for the fedora docker image, seems consistent10:54
phildawson_That was my thought. I don't really understand the issue, but the symptoms and timing seem to match up.10:58
benschubertbasically, they introduced a new compression mechanism that ended up segfaulting and they had to disable it on the repos and update the client before reenabling, but if you are on a bad version now, you need to explicitely disable to be able to update -_-''11:07
cs-shadowi'd have hoped that the they will publish a new base image with the fix11:23
gitlab-br-bottristanvb opened MR !1308 (tristan/fdsdk-ci-refresh->master: .gitlab-ci.yml: Updating overnight tests to test ported freedesktop-sdk) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/130811:25
*** ChanServ sets mode: +o tristan11:26
tristanphildawson_, So that mr above ^^ should make the overnight tests work again... unless there is a bug still in my port of the flatpak_image but I doubt it11:27
tristanphildawson_, I left you hanging on that issue/mr about tests - I am personally really keen on having something more explicit as I described (have an external plugin declare a test case and call an explicit API handing over a repo implementation and plugin kind, instead of some mysterious hooks triggering tests)11:28
tristanphildawson_, but I dont want to push more work onto you because of that, so I hope maybe I can help out and try to figure out a more nicely integrated API surface for source tests, if you'll allow me :)11:29
*** tristan has quit IRC11:53
*** lachlan has joined #buildstream11:58
*** tristan has joined #buildstream11:58
*** lachlan has quit IRC12:02
laurencejonathanmaw, jennis - I'm wondering if we want to trim the table in the weekly performance email a little12:32
laurencei usually just look at the last 4 or 5 rows12:33
phildawson_tristan, it'll be nice to have the overnight test working again :) About the source tests, I freely accept that it's a little bit magic and I'm definitely happy to discuss improvements. As you say though, I'm not sure quite how much time I'll be able to spend on it.12:38
jennislaurence, yeah nice idea, it's getting quite long13:01
*** lachlan has joined #buildstream13:03
phildawson_+1 it's easy enough to go looking for the historical data if you want to :)13:08
*** lachlan has quit IRC13:11
gitlab-br-botphildawson opened MR !1309 (phil/1008->master: setup.py: Include buildstream.testing datafiles in package_data) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/130913:15
phildawson_^benschubert13:16
benschubertphildawson_: great thanks !13:24
benschubertlet me test this13:25
*** phil has joined #buildstream13:32
*** phildawson_ has quit IRC13:33
gitlab-br-botBenjaminSchubert approved MR !1309 (phil/1008->master: setup.py: Include buildstream.testing datafiles in package_data) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/130913:46
*** lachlan has joined #buildstream13:53
*** lachlan has quit IRC13:58
gitlab-br-botphildawson opened issue #1009 (CI doesn't test sdist packaging includes necessary data files) on buildstream https://gitlab.com/BuildStream/buildstream/issues/100914:04
*** lachlan has joined #buildstream14:04
*** lachlan has quit IRC14:09
laurencejennis, also, and this may be a dumb question, but we still have 'show' and 'show with cache' columns14:12
laurencedo we need both?14:12
laurencei guess it can't hurt, but i was a little surprised we still tested with a hot cache - isn't it redundant now? or doesn't it add an overhead?14:13
benschubertguess we can drop it in the next email :)14:15
jonathanmawtristan: do you have https://gitlab.com/BuildStream/buildstream/merge_requests/1299 on your agenda at some point? I'd like a sanity check if you have time.14:33
*** lachlan has joined #buildstream14:33
jennislaurence, yeah it was just legacy stuff14:47
jennisWill also drop this in the next email14:48
tpollardis there any reason that we 'force' certain abstract methods to be implemented by certain subclasses, but don't use @abstractmethod to enforce it?14:48
*** lachlan has quit IRC14:51
gitlab-br-botabderrahimk reopened issue #990 (BUG in push with non-strict mode) on buildstream https://gitlab.com/BuildStream/buildstream/issues/99014:55
*** phil is now known as phildawson15:02
*** toscalix has quit IRC15:19
*** alatiera has quit IRC15:22
*** toscalix has joined #buildstream15:27
*** toscalix has quit IRC15:27
*** alatiera has joined #buildstream15:28
gitlab-br-botmarge-bot123 closed issue #1008 (Data files are missing from python package) on buildstream https://gitlab.com/BuildStream/buildstream/issues/100815:55
gitlab-br-botmarge-bot123 merged MR !1309 (phil/1008->master: setup.py: Include buildstream.testing datafiles in package_data) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/130915:55
gitlab-br-botjennis opened MR !1310 (jennis/revert_gc_management->master: Revert !1164 - Manage GC during pipeline load) on buildstream https://gitlab.com/BuildStream/buildstream/merge_requests/131016:00
tpollardcs-shadow: around?16:51
cs-shadowtpollard: hey! yes16:51
tpollardcool :)16:51
tpollardcs-shadow: I'm currently trying to get !1292 over the line, after recently rebasing it against master it now has a single test failure. Working my way back and cherry picking the the patchset it occurs when https://gitlab.com/BuildStream/buildstream/commit/1cbc5e63dc10c7676237fa923273a3937d6977ca lands16:53
gitlab-br-botMR !1292: Artifact as a Proto: rework https://gitlab.com/BuildStream/buildstream/merge_requests/129216:53
tpollardany ideas?16:53
cs-shadowinteresting, is the failure in a CI job somewhere?16:54
tpollardhttps://gitlab.com/BuildStream/buildstream/-/jobs/200866731 is an instance of the failure16:54
tpollardbut it occurs locally too16:54
tpollardthe MR applied on top of the previous commit to that one linked it passes fine16:54
cs-shadowlet me have a look. We did stop creating an empty `bst` directory so if anything was relying on that directory being there, it might be affected16:55
tpollardThat's my current thought16:56
tpollard`git cherry-pick e2285e58472633b7cf836c9c950e32507231190a^..744ca6b9c7cd99af8439db761390f2dfd3ab9140` for the set16:56
tpollardalso this isn't my MR, so makes it even more fun :)16:57
*** lachlan has joined #buildstream17:03
*** jonathanmaw has quit IRC17:05
*** lachlan has quit IRC17:08
cs-shadowtpollard: my testing setup is somewhat busted at the moment (different story) but my suspicion is that the tests needs to be updated. We are asserting that the size of our output is non-zero. This is fine for a stack element, which is what are seeing in the CI. `assert directory_hash and directory_size` fails because the size is 017:14
cs-shadowI think this is because of the changes in _artifact.py related to how the size is calculated.17:14
tpollardyes I think it's stemming from cache() in _artifact.py17:15
tpollardhmm17:17
cs-shadowI don't have a place to test it somewhere but I'd be tempted to see what the size is at the moment. Maybe it is taking into account the size of the parent directory or something like that17:20
*** nimish2711 has quit IRC18:08
*** alatiera has quit IRC18:59
*** kapil___ has quit IRC19:02
*** bochecha has quit IRC22:06
*** rdale has quit IRC23:36
*** benschubert has quit IRC23:48

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!