| *** tristan has quit IRC | 00:17 | |
| *** tristan has joined #buildstream | 03:06 | |
| *** ernestask has joined #buildstream | 05:50 | |
| gitlab-br-bot | buildstream: merge request (show_sources->master: Added a flag to bst show) #222 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/222 | 06:40 |
|---|---|---|
| gitlab-br-bot | buildstream: merge request (fixup_internal->master: _variables: refactor, private 'subst_internal') #150 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/150 | 06:51 |
| gitlab-br-bot | buildstream: issue #191 ("Allow project relative workspace paths") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/191 | 07:04 |
| gitlab-br-bot | buildstream: issue #139 ("Inconsistent error printing at load time") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/139 | 08:02 |
| *** valentind has joined #buildstream | 08:26 | |
| *** jude has joined #buildstream | 09:03 | |
| *** noisecell has joined #buildstream | 09:25 | |
| *** ernestask has quit IRC | 09:31 | |
| *** ssam2 has joined #buildstream | 09:32 | |
| tlater | Are variables supposed to expand in script element scripts? | 09:37 |
| tlater | I.e., the commands in the config section | 09:37 |
| tristan | tlater, Yes. | 09:38 |
| *** jonathanmaw has joined #buildstream | 09:38 | |
| tristan | tlater, That is not to say that `bst show` would ever be able to tell you about how it would expand, though. | 09:38 |
| *** ernestask has joined #buildstream | 09:39 | |
| tlater | Darn... Well, they aren't expanding for me atm, not sure if this could somehow be triggered by how the tests run buildstream. | 09:39 |
| tristan | it could be a bug | 09:39 |
| tristan | but looks like `script` element calls self.node_subst_list() | 09:40 |
| tristan | which should do the subst thing | 09:40 |
| tlater | Hm, I'll try and confirm it outside of the test suite | 09:40 |
| * tlater has a feeling it won't be a bug though | 09:41 | |
| tlater | Ah, nevermind, I changed something about how the test suite runs that changed the way I have to specify variables... | 09:57 |
| tlater | Alright, so the (hopefully) last isue before the new integration tests can go up for review is that the unix tests cannot run the base-platform, because that's an ostree source | 10:04 |
| * tlater thinks this used to work because we had a lingering artifact cache | 10:04 | |
| tristan | Err, that is strange | 10:04 |
| tristan | tlater, I think this is working for another reason | 10:05 |
| tristan | tlater, we currently always test on linux, and force the backend, without uninstalling ostree or such | 10:05 |
| tristan | so we run the unix backend but still use the ostree plugin on linux | 10:05 |
| tristan | tlater, yes that is certainly what happens now; I often see the ostree plugin output on gitlab in the unix tests | 10:06 |
| tlater | That can't be - if that was the case, we would still be running into that | 10:06 |
| tlater | I am running the tests in the same environment, just with better cache management | 10:06 |
| * tlater also remembers having a discussion on how we could avoid this with same | 10:07 | |
| tlater | ssam2: | 10:07 |
| tlater | s/same/ssam2/ | 10:07 |
| *** valentind has quit IRC | 10:08 | |
| tristan | tlater, https://gitlab.com/BuildStream/buildstream/-/jobs/47829255 | 10:09 |
| tristan | tlater, see the lines like: [--:--:--][b9c0de0c][fetch:dependencies/base-sdk.bst ] STATUS Receiving objects: 72% (23055/31817) 224.2 MB | 10:09 |
| tristan | tlater, remember; the local artifact cache != the ostree source plugin | 10:09 |
| tlater | Right, yeah | 10:10 |
| tlater | Hrm | 10:10 |
| tlater | Either way, that seems like a bug - how would we run the tests without the ostree plugin? | 10:10 |
| tristan | tlater, using a tarball hosted somewhere instead | 10:10 |
| tlater | I've been thinking about including the base tarball in the main repo, but that would be 3GB just for integraiton tests | 10:11 |
| tlater | Where else could we host that? | 10:11 |
| ssam2 | do the tests actually need to use the 3GB Freedesktop SDK ? | 10:11 |
| *** tiago has joined #buildstream | 10:11 | |
| tristan | tlater, so hopefully that would be a tarball of the "tiny base runtime" which is being created in the freedesktop-sdk project | 10:11 |
| tristan | No they dont, and even if it's a nice and small 300MB runtime, I dont want it in BuildStream repo | 10:12 |
| ssam2 | of course | 10:12 |
| ssam2 | using Docker Hub is one option | 10:12 |
| ssam2 | or, just any web server that can serve tarballs | 10:12 |
| tristan | Needs a docker source though | 10:12 |
| ssam2 | any buildstream artifact cache server could do that, we just stick the tarballs in a tarballs/ dir and have the existing web server serve it | 10:13 |
| tristan | (or maybe docker does tarballs I dont know) | 10:13 |
| tristan | Yes | 10:13 |
| tlater | Do we have a public cache server that we could use for this? | 10:13 |
| tristan | tlater, So short term: we put a tarball up on gnome7 | 10:13 |
| ssam2 | oh, by the way -- i wrote up https://wiki.gnome.org/Projects/BuildStream/Infrastructure | 10:14 |
| tristan | tlater, Long term; we later switch that to point to an officially hosted (smaller) tarball generated by freedesktop-sdk project | 10:14 |
| tlater | Yeah, that seems like a solution | 10:15 |
| tristan | ssam2, nice | 10:15 |
| tlater | I just need access to gnome7 then to push this tarball | 10:15 |
| tristan | tlater, perhaps also; we use conditional statements to use ostree in the linux tests and tarballs in the unix tests | 10:16 |
| tristan | tlater, ssam2 has access, I'd help but it wouldnt be very efficient at 350ms ping | 10:16 |
| tlater | ssam2: Could I ask you to create the tarball? I have a very poor connection atm as well, unfortunately | 10:17 |
| tristan | looks like I fell short of the mark of restructuring the toplevel documentation into sections... wanted to do that today and get the existing docs patches out of the way... | 10:17 |
| tristan | tomorrow then | 10:18 |
| * tlater will happily make a little mini-script to do it, but would preferably run it somewhere ostree doesn't take 60 minutes | 10:18 | |
| tristan | Ahh that part | 10:18 |
| ssam2 | tlater, what should i create a tarball of ? | 10:19 |
| * tristan was under the impression tlater had a tarball in his possession | 10:19 | |
| * tristan suspects it will be an ostree clone, checkout, and tar | 10:19 | |
| ssam2 | ok, I can do that if you give me the repo and ref | 10:19 |
| tlater | ssam2: Hang on a second, I'll give you my buildstream element | 10:20 |
| tlater | ssam2: https://gitlab.com/BuildStream/buildstream/blob/759cd4c5a4bdb4a80b0056378f43d32cd16620a9/tests/integration/project/elements/base/base-sdk.bst | 10:22 |
| * tlater wonders if we should create tarballs for multiple architectures | 10:22 | |
| tlater | I neglected that for now, but wanted to add it back now that the tests are running | 10:22 |
| tristan | tlater, maybe we can punt that yeah, until freedesktop-sdk provides a nice smaller one | 10:22 |
| tristan | tlater, that said, the smallest runtimes wont necessarily work for our tests; we may consider reducing our tests to avoid depending on such high level things like python | 10:24 |
| tristan | since all the build element code is the same and just different YAML defaults, seems like it would be an okay tradeoff | 10:25 |
| tlater | Hm, we'd miss issues with those defaults, though | 10:26 |
| nexus | Is there a know cause for my pipelines getting an AssertionError in runcli.py:107 ? | 10:26 |
| tristan | Myeah; we're not really testing much relevant stuff with them, we're more concerned that split rules and modifications made in integration commands and such work | 10:27 |
| tristan | that the fuse layer is working well | 10:27 |
| tristan | that the sandboxing works | 10:27 |
| tristan | tlater, consider 'integration tests' as 'anything which requires external stuff', like running against a specific host, or needing an external runtime in order to test the core | 10:27 |
| tristan | tlater, you're correct; that we would not be covering those defaults, but ... eh | 10:28 |
| tristan | anyway; that is out of scope for now | 10:28 |
| tristan | nexus, perhaps with a paste of the output | 10:28 |
| tristan | nexus, and probably you ran it on your machine with `./setup.py test` | 10:28 |
| tristan | so you should be able to debug it | 10:29 |
| * tristan has to head out early today | 10:29 | |
| nexus | https://pastebin.com/chrjz701 | 10:30 |
| tristan | nexus, so assert_main_error() failed | 10:32 |
| tristan | nexus, to find out what that means, you would normally run something like this: | 10:33 |
| tristan | grep -r "assert_main_error" tests/ | 10:33 |
| tristan | nexus, that would end up leading you to where it's declared: https://gitlab.com/BuildStream/buildstream/blob/master/tests/testutils/runcli.py#L87 | 10:34 |
| *** tristan has quit IRC | 10:37 | |
| *** tristan has joined #buildstream | 10:42 | |
| *** mcatanzaro has joined #buildstream | 11:44 | |
| gitlab-br-bot | buildstream: merge request (issue-181_bst_build_--track-except->master: Fix for issue #181) #228 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/228 | 11:57 |
| jjardon[m] | Hi, looking at https://gitlab.com/freedesktop-sdk/freedesktop-sdk/merge_requests/74 : is it expected that no rebuild is needed when upgrading the bst version we use to build? | 12:49 |
| gitlab-br-bot | buildstream: merge request (juerg/source-state->master: source state updates) #230 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/230 | 12:50 |
| juergbi | jjardon[m]: yes, as long as the project wasn't affected by the instability of cache keys for local sources | 12:51 |
| jjardon[m] | juergbi: rigth, thanks | 12:54 |
| *** xjuan has joined #buildstream | 12:59 | |
| * tlater needs to build muscle memory to use tar -vcaf over tar -caf on large directories... | 13:15 | |
| gitlab-br-bot | buildstream: merge request (monkey-patch-setuptools->master: Modify the generated CLI script by monkey patching) #231 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/231 | 13:51 |
| gitlab-br-bot | buildstream: merge request (monkey-patch-setuptools->master: Modify the generated CLI script by monkey patching) #231 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/231 | 14:00 |
| inigomartinez | i don't know if it makes any sense, but is there any way to "mount" somehow the sandbox environment? | 14:01 |
| tlater | inigomartinez: Do `bst shell <element>` or `bst shell -b <element>` do what you want? | 14:02 |
| inigomartinez | i'm porting an application to meson and I would like to compare the tree installed by autotools with meson's installed tree | 14:02 |
| bochecha | inigomartinez: then yes, `bst shell <element>` | 14:03 |
| bochecha | that starts a shell in the sandbox after the element was installed | 14:03 |
| inigomartinez | yes... i still haven't tried it (i'm opening a shell right now), but i think that i would have some issues that way | 14:05 |
| bochecha | what you'll see is the merged filesystem, containing both what was installed for your element, as well as all the dependencies | 14:06 |
| bochecha | when I want to just list the files installed by my element, I add a command at the end of the `install-commands:` list like `find %{install-root}` :P | 14:07 |
| inigomartinez | yes, but i suspect that i'll have a limited set of utilities to compare both trees | 14:07 |
| bochecha | another possibility is `bst checkout <element> <checkout_directory>` | 14:08 |
| tlater | inigomartinez: Could you use `bst checkout` to just checkout the resulting files? | 14:08 |
| tlater | Ah, that^ | 14:08 |
| bochecha | that gives you the whole filesystem tree of your element and its dependencies, checked out in `<checkout_directory>` | 14:08 |
| gitlab-br-bot | buildstream: merge request (monkey-patch-setuptools->master: Modify the generated CLI script by monkey patching) #231 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/231 | 14:09 |
| inigomartinez | ok, that is what i needed, thank you :) | 14:16 |
| inigomartinez | i suppose that this doesn't change on the fly with new builds, isn't it? | 14:16 |
| tlater | inigomartinez: No, you'll have to check out again | 14:17 |
| inigomartinez | ok | 14:18 |
| inigomartinez | what about accessing the host system through the sanboxed environment? is it possible? | 14:19 |
| tlater | No, that is not possible. Buildstream aims to keep builds reproducible, and therefore needs them to be completely independent from the host system. | 14:21 |
| tlater | Why would you want to do that, inigomartinez? | 14:23 |
| * inigomartinez sent a long message: inigomartinez_2018-01-15_14:24:03.txt <https://matrix.org/_matrix/media/v1/download/matrix.org/FwKOLKPpoVDvlDxnTbKHpoFf> | 14:24 | |
| inigomartinez | (though i'm able to do the reverse procedure on the host system) | 14:25 |
| tlater | Why are you avoiding `bst checkout`? There *is* a way to do the above on just the host system, yes, but it involves poking internals. | 14:25 |
| bochecha | tlater: `bst shell` allows getting a shell either before the build (`--build`) or after composing the built element and its dependencies... could it allow getting a shell right after the installation of the element, but while it's all still in %{install-root}? | 14:26 |
| inigomartinez | it's a bit slow here checking out the whole build system and I was trying to think on a faster :/ | 14:27 |
| inigomartinez | *faster alternative | 14:27 |
| tlater | Ah, yeah, I understand that... You can find the artifacts in ~/.cache/buildstream/artifacts before you check them out, but iirc they are still in an ostree repo, which means you have to check them out anyway. | 14:29 |
| tlater | To do the mounty thing without mounting, you can access the sysroot that the shell is launched in in ~/.cache/buildstream/build/ | 14:29 |
| tlater | But this is obviously all reliant on buildstream internals, so may change any time, or be quite unstable. | 14:30 |
| tlater | bochecha: I don't think so, unfortunately - the fastest way to do this probably is poking around in ~/.cache/buildstream/build | 14:31 |
| inigomartinez | the `~/.cache/` alternative looks like a nice alternative at the moment | 14:31 |
| inigomartinez | thx again :) | 14:31 |
| gitlab-br-bot | buildstream: merge request (delay-pkg-resources-import->master: Delay import of pkg_resources) #232 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/232 | 14:34 |
| jonathanmaw | tristan: I don't quite understand the new test scenario in https://gitlab.com/BuildStream/buildstream/merge_requests/181. I'm not sure what ordering you're expecting, but I think it's A above B above C, and you want to be sure that, even when overlaps aren't triggered by an element building that depends on something it overlaps with (i.e. A and B) | 15:07 |
| jonathanmaw | Does it matter whether the dependency is build or runtime? | 15:09 |
| gitlab-br-bot | buildstream: merge request (incremental-build->master: WIP: Add support for doing incremental builds) #126 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/126 | 15:09 |
| gitlab-br-bot | buildstream: merge request (incremental-build->master: WIP: Add support for doing incremental builds) #126 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/126 | 15:10 |
| gitlab-br-bot | buildstream: merge request (175-refactor-integration-tests->master: WIP: Resolve "Refactor integration tests") #233 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/233 | 15:13 |
| gitlab-br-bot | buildstream: merge request (version-read-no-pkg_res->master: Get version number w/o pkg_resources) #234 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/234 | 15:27 |
| gitlab-br-bot | buildstream: merge request (version-read-no-pkg_res->master: Get version number w/o pkg_resources) #234 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/234 | 15:27 |
| gitlab-br-bot | buildstream: merge request (sam/improve-cache-warnings->master: Shorten the warnings raised when remote cache initialization fails) #235 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/235 | 15:28 |
| ssam2 | jmac, https://gitlab.com/BuildStream/buildstream-tests/commit/d275b2d57c481316a24fa4cf30df38536b7211b6 | 15:31 |
| jmac | Great, thanks ssam2! | 15:31 |
| gitlab-br-bot | buildstream: merge request (version-read-no-pkg_res->master: Get version number w/o pkg_resources) #234 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/234 | 15:47 |
| gitlab-br-bot | buildstream: merge request (modAndTest->master: Making changes to various documents:) #206 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/206 | 16:00 |
| gitlab-br-bot | buildstream: merge request (master->master: WIP: Documentation improvements) #183 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/183 | 16:02 |
| gitlab-br-bot | buildstream: merge request (postbuild->master: Added Postbuild documentation) #236 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/236 | 16:14 |
| gitlab-br-bot | buildstream: merge request (createProject->master: Adding create project document) #237 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/237 | 16:16 |
| gitlab-br-bot | buildstream: merge request (buildproject->master: Added buildproject doc) #238 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/238 | 16:19 |
| gitlab-br-bot | buildstream: merge request (version-read-no-pkg_res->master: Get version number w/o pkg_resources) #234 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/234 | 17:55 |
| *** ssam2 has quit IRC | 17:55 | |
| gitlab-br-bot | buildstream: merge request (juerg/recursive-pipelines->master: WIP: Junctions and subprojects) #160 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/160 | 17:57 |
| *** ernestask has quit IRC | 18:13 | |
| *** jonathanmaw has quit IRC | 18:24 | |
| *** valentind has joined #buildstream | 18:27 | |
| *** ironfoot_ has joined #buildstream | 18:29 | |
| *** noisecell has quit IRC | 18:29 | |
| *** cs_shadow has quit IRC | 18:29 | |
| *** csoriano has quit IRC | 18:29 | |
| *** saxa has quit IRC | 18:29 | |
| *** ptomato[m] has quit IRC | 18:29 | |
| *** waltervargas[m] has quit IRC | 18:29 | |
| *** ernestask[m] has quit IRC | 18:29 | |
| *** m_22[m] has quit IRC | 18:29 | |
| *** pro[m] has quit IRC | 18:29 | |
| *** mrmcq2u[m] has quit IRC | 18:29 | |
| *** cgmcintyre[m] has quit IRC | 18:29 | |
| *** mattiasb has quit IRC | 18:29 | |
| *** kailueke[m] has quit IRC | 18:29 | |
| *** ironfoot has quit IRC | 18:29 | |
| *** jjardon[m] has quit IRC | 18:29 | |
| *** bochecha has quit IRC | 18:29 | |
| *** xjuan has quit IRC | 18:29 | |
| *** mcatanzaro has quit IRC | 18:29 | |
| *** tristan has quit IRC | 18:29 | |
| *** tiago has quit IRC | 18:29 | |
| *** jude has quit IRC | 18:29 | |
| *** adds68__ has quit IRC | 18:29 | |
| *** paulsherwood has quit IRC | 18:29 | |
| *** nexus has quit IRC | 18:29 | |
| *** tlater has quit IRC | 18:29 | |
| *** gitlab-br-bot has quit IRC | 18:29 | |
| *** lantw44 has quit IRC | 18:29 | |
| *** saxa has joined #buildstream | 18:29 | |
| *** noisecell has joined #buildstream | 18:30 | |
| *** csoriano has joined #buildstream | 18:30 | |
| *** xjuan has joined #buildstream | 18:30 | |
| *** mcatanzaro has joined #buildstream | 18:30 | |
| *** tristan has joined #buildstream | 18:30 | |
| *** tiago has joined #buildstream | 18:30 | |
| *** jude has joined #buildstream | 18:30 | |
| *** adds68__ has joined #buildstream | 18:30 | |
| *** paulsherwood has joined #buildstream | 18:30 | |
| *** nexus has joined #buildstream | 18:30 | |
| *** tlater has joined #buildstream | 18:30 | |
| *** gitlab-br-bot has joined #buildstream | 18:30 | |
| *** lantw44 has joined #buildstream | 18:30 | |
| *** cs_shadow has joined #buildstream | 18:30 | |
| *** saxa has quit IRC | 18:32 | |
| gitlab-br-bot | buildstream: merge request (juerg/recursive-pipelines->master: WIP: Junctions and subprojects) #160 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/160 | 18:35 |
| *** mattiasb has joined #buildstream | 18:46 | |
| *** bochecha has joined #buildstream | 19:13 | |
| *** xjuan has quit IRC | 20:14 | |
| *** waltervargas[m] has joined #buildstream | 20:33 | |
| *** ptomato[m] has joined #buildstream | 21:14 | |
| *** noisecell has quit IRC | 21:44 | |
| *** pro[m] has joined #buildstream | 21:59 | |
| *** mrmcq2u[m] has joined #buildstream | 22:00 | |
| *** jjardon[m] has joined #buildstream | 22:15 | |
| *** kailueke[m] has joined #buildstream | 22:43 | |
| *** cgmcintyre[m] has joined #buildstream | 22:54 | |
| *** ernestask[m] has joined #buildstream | 23:09 | |
| *** ernestask[m] is now known as Guest56733 | 23:09 | |
| *** m_22[m] has joined #buildstream | 23:45 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!