IRC logs for #buildstream for Sunday, 2018-07-29

*** Miron has joined #buildstream03:58
*** leopi has joined #buildstream04:36
*** leopi has quit IRC05:03
*** xset has joined #buildstream05:27
*** leopi has joined #buildstream06:27
gitlab-br-botbuildstream: merge request (507-some-log-lines-appear-to-be-duplicates->master: Resolve "Some log lines appear to be duplicates") #573 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/57307:52
*** tristan has joined #buildstream08:03
gitlab-br-botbuildstream: merge request (tristan/source-mirrors-backport->bst-1.2: source mirrors backport) #582 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/58208:10
gitlab-br-botbuildstream: merge request (tristan/source-mirrors-backport->bst-1.2: source mirrors backport) #582 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/58208:12
tristanjjardon, do we have a runner down again ?08:26
tristanIt seems we have less parallel jobs available than usual08:26
jjardontristan number of available runners is unlimited; can you be more specific?08:30
jjardonIf the runner that manage the runners is down, you could not build anything at all08:31
tristanjjardon, https://gitlab.com/BuildStream/buildstream/-/jobs/8512572608:35
tristanthis guy is waiting, and afaics there are only 2 other jobs running in BuildStream's pipelines08:35
tristanthose are here: https://gitlab.com/BuildStream/buildstream/pipelines/2670960708:36
tristanthat pipeline also took some time to get started08:36
* jjardon checks08:36
*** bochecha has joined #buildstream08:38
jjardontristan: seems the creation of the new runner was a bit slow, that's all08:41
tristanjjardon, yep, seems to be08:45
tristananyway https://gitlab.com/BuildStream/buildstream/pipelines/26709880 seems to be going alright now08:45
jjardontristan: when there is no runners available yet, and you start to start several job, always expect more time to start them, as the actual runner itself needs to be created, and the docker image doployed on it. This will affect mostly you as you are the first in the morning to start creating jobs :)08:47
jjardon(we have a timeout to keep the runner up for 30 min before killing it, so subsequent jobs will start much faster)08:49
tristanjjardon, Ah that makes sense, this usually happens on the weekend :)08:49
tristanbut yeah maybe first in the morning will often happen to me too indeed08:49
gitlab-br-botbuildstream: merge request (tristan/fix-spurious-errors->master: git.py: Handle concurrent download completions properly) #583 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/58309:17
gitlab-br-botbuildstream: merge request (tristan/fix-spurious-errors-1.2->bst-1.2: git.py: Handle concurrent download completions properly) #584 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/58409:23
gitlab-br-botbuildstream: merge request (tristan/backported-version-updates->master: backported version updates) #585 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/58509:46
gitlab-br-botbuildstream: merge request (tristan/source-mirrors-backport->bst-1.2: source mirrors backport) #582 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/58209:49
gitlab-br-botbuildstream: merge request (tristan/fix-spurious-errors-1.2->bst-1.2: git.py: Handle concurrent download completions properly) #584 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/58409:57
tristanjjardon, I wonder if we can improve the cache creation and reuse on gitlab; so that the cache needs to be recreated less often, do you think ?10:07
tristanjjardon, some of our CI, notably the parts which rely on the external SDK (tests the example of building on a flatpak), would be much more optimized10:08
jjardontristan: yeah10:10
jjardonyou can configure jobs to only pull the cache, not push at all10:11
jjardonif you know is not needed10:11
jjardontristan: check https://docs.gitlab.com/ee/ci/yaml/#cache-policy10:11
tristanjjardon, hmmm, maybe we accidentally have that configured ?10:12
tristanI get the feeling we are reusing a stale cache from before we added the test10:13
tristanwhich requires an SDK download10:13
* jjardon[m] checks10:13
tristanor, the new test with the SDK download requires a cache that exceeds some limit ?10:13
tristanso we always fail to create it maybe ?10:13
jjardontristan: I do not see any use of the cache policies in the buildstream .gitlab-ci.yml10:14
jjardontristan: what job is this?10:14
tristanjjardon, every job I guess - just forget for now and I'll keep it in mind and raise it again; situation will be improved with #503 fixed which is currently being fixed10:16
tristan(but waiting on other pipelines to complete / rebase)10:16
jjardontristan: ok, let me know10:17
*** jjardon sets mode: +o tristan10:17
tristanjjardon, notably I'm talking about the time it takes for tests/examples/flatpak-autotools.py to complete, inside https://gitlab.com/BuildStream/buildstream/-/jobs/85124948 for instance10:17
tristanthat test has always been slow due to the SDK download, so I'm hoping to optimize it with the cache, that's pretty much it10:17
tristanbut I'll investigate more10:18
* tristan has ops when he signs in, but thanks :)10:18
* tristan just usually doesnt sign in10:18
tristanjjardon, I think the caches are alright, this job successfully created it (so it says) https://gitlab.com/BuildStream/buildstream/-/jobs/8512494810:20
gitlab-br-botbuildstream: issue #507 ("Some log lines appear to be duplicates") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/50710:23
gitlab-br-botbuildstream: merge request (507-some-log-lines-appear-to-be-duplicates->master: Resolve "Some log lines appear to be duplicates") #573 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/57310:23
gitlab-br-botbuildstream: merge request (tristan/backported-version-updates->master: backported version updates) #585 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/58510:25
*** shenglong has joined #buildstream10:26
gitlab-br-botbuildstream: merge request (tristan/fix-spurious-errors->master: git.py: Handle concurrent download completions properly) #583 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/58310:26
*** tristan has quit IRC10:32
*** tristan has joined #buildstream10:46
tristanhttps://gitlab.com/BuildStream/buildstream/-/jobs/85139153 tests/examples/flatpak-autotools.py::test_autotools_build still takes a very long time10:46
tristanbut I guess it's more about staging time of the existing large SDK artifact, rather than lack of it in the cache10:46
*** Miklo has joined #buildstream10:50
MikloWant IRC ads? https://williampitcock.com/10:50
*** Miklo has quit IRC10:50
gitlab-br-botbuildstream: merge request (jmac/virtual_directories->master: Abstract directory class and filesystem-backed implementation) #445 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/44511:12
gitlab-br-botbuildstream: merge request (jmac/virtual_directories->master: Abstract directory class and filesystem-backed implementation) #445 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/44511:15
gitlab-br-botbuildstream: merge request (jmac/cas_virtual_directory->jmac/googlecas_and_virtual_directories_2: WIP: CAS-backed virtual directory implementation) #481 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/48111:15
gitlab-br-botbuildstream: issue #503 ("spurious failures in test_build_track") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/50311:18
gitlab-br-botbuildstream: merge request (tristan/fix-spurious-errors->master: git.py: Handle concurrent download completions properly) #583 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/58311:18
*** r00t has joined #buildstream11:46
r00tWant IRC ads? https://williampitcock.com/11:46
*** r00t has quit IRC11:46
*** was has joined #buildstream11:49
wasWant IRC ads? https://williampitcock.com/11:49
*** was has quit IRC11:53
*** Pyrotechno has joined #buildstream11:53
PyrotechnoWant IRC ads? https://williampitcock.com/11:53
*** Pyrotechno has quit IRC11:57
*** epic has joined #buildstream12:04
epicWant IRC ads? https://williampitcock.com/12:04
*** epic has quit IRC12:08
*** urdh has joined #buildstream12:09
urdhWant IRC ads? https://williampitcock.com/12:09
*** DJones has joined #buildstream12:10
DJonesWant IRC ads? https://williampitcock.com/12:10
*** urdh has quit IRC12:13
*** DJones has quit IRC12:14
tristanOh yeah... adds please ! \o/12:36
*** ernestask has joined #buildstream13:02
csorianojjardon: setting +s worked elsewhere15:45
csoriano /mode #buildstream +s15:45
*** leopi has quit IRC16:18
*** ernestask has quit IRC17:15
gitlab-br-botbuildstream: merge request (tristan/fix-spurious-errors-1.2->bst-1.2: git.py: Handle concurrent download completions properly) #584 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/58417:22
*** leopi has joined #buildstream17:23
gitlab-br-botbuildstream: merge request (tristan/backport-logline-dups-1.2->bst-1.2: buildelement.py: Only display one activity message (#507)) #586 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/58617:40
*** leopi has quit IRC18:10
*** bochecha has quit IRC18:26
*** infernix has joined #buildstream19:26
gitlab-br-botbuildstream: merge request (tristan/fix-spurious-errors-1.2->bst-1.2: git.py: Handle concurrent download completions properly) #584 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/58419:53
gitlab-br-botbuildstream: merge request (tristan/backport-logline-dups-1.2->bst-1.2: buildelement.py: Only display one activity message (#507)) #586 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/58619:55
*** finn has joined #buildstream20:18
gitlab-br-botbuildstream: merge request (tristan/backport-logline-dups-1.2->bst-1.2: buildelement.py: Only display one activity message (#507)) #586 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/58621:14

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