| *** tristan has quit IRC | 04:18 | |
| *** tristan has joined #buildstream | 04:27 | |
| gitlab-br-bot | push on buildstream@sam/fix-docs (by Tristan Van Berkom): 4 commits (last: Fix keyboardinterrupts caused by subprocesses) https://gitlab.com/BuildStream/buildstream/commit/23c1e284ea748942e7067454aae2b279a1ab0e68 | 05:07 |
|---|---|---|
| gitlab-br-bot | buildstream: merge request (sam/fix-docs->master: .gitlab-ci.yml: Fix documentation build) #116 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/116 | 05:07 |
| gitlab-br-bot | buildstream: merge request (102-run-ci-as-non-root-user->master: Resolve "Run CI as non-root user") #104 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/104 | 05:10 |
| gitlab-br-bot | push on buildstream@102-run-ci-as-non-root-user (by Tristan Van Berkom): 2 commits (last: Add warnings when staging to /buildstream/build) https://gitlab.com/BuildStream/buildstream/commit/10847a66dc0748696829d5fd18ad17043c2c6878 | 05:10 |
| gitlab-br-bot | push on buildstream@master (by Tristan Van Berkom): 1 commit (last: .gitlab-ci.yml: Fix documentation build) https://gitlab.com/BuildStream/buildstream/commit/8cdacab742d0749da45ba2b807f13c59f0bfd18f | 05:11 |
| gitlab-br-bot | buildstream: merge request (sam/fix-docs->master: .gitlab-ci.yml: Fix documentation build) #116 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/116 | 05:11 |
| gitlab-br-bot | buildstream: merge request (102-run-ci-as-non-root-user->master: Resolve "Run CI as non-root user") #104 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/104 | 05:12 |
| gitlab-br-bot | push on buildstream@102-run-ci-as-non-root-user (by Tristan Van Berkom): 2 commits (last: .gitlab-ci.yml: Fix documentation build) https://gitlab.com/BuildStream/buildstream/commit/8cdacab742d0749da45ba2b807f13c59f0bfd18f | 05:12 |
| *** adds68 has quit IRC | 07:57 | |
| *** adds68 has joined #buildstream | 07:57 | |
| *** jonathanmaw has joined #buildstream | 08:37 | |
| gitlab-br-bot | push on buildstream@master (by Tristan Van Berkom): 1 commit (last: .gitlab-ci.yml: Drop root privileges for some tests) https://gitlab.com/BuildStream/buildstream/commit/324a3cbd69026fa565bbeb174a308456f1ef8fa6 | 08:54 |
| gitlab-br-bot | buildstream: issue #102 ("Run CI as non-root user") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/102 | 08:54 |
| gitlab-br-bot | buildstream: merge request (102-run-ci-as-non-root-user->master: Resolve "Run CI as non-root user") #104 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/104 | 08:54 |
| tristan | juergbi, any thoughts on https://gitlab.com/BuildStream/buildstream/issues/105#note_44039467 ? | 08:58 |
| tristan | I'm tempted to immediately set SOURCE_DATE_EPOCH=0 across the board, but reproducible builds says "... MUST not", which is confusing and obnoxious | 08:59 |
| juergbi | taking a look | 09:01 |
| tristan | https://reproducible-builds.org/specs/source-date-epoch/ | 09:02 |
| * tristan wonders if they have a mailing list, where do things get contested ? | 09:02 | |
| * tristan subscribes to https://lists.reproducible-builds.org/listinfo/rb-general | 09:03 | |
| tristan | might be interesting ML for others in this channel btw | 09:03 |
| juergbi | tristan: i assume the 'MUST NOT' refers to build systems of individual modules | 09:04 |
| tristan | It says exporting to subprocesses, if it is not present | 09:04 |
| juergbi | i.e., they should allow top-level build systems to set it and the module-level build systems should use the set value | 09:04 |
| tristan | Ah that could make more sense | 09:05 |
| juergbi | https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal#Setting_the_variable | 09:05 |
| tristan | only set if not already in the env | 09:05 |
| juergbi | Debian sets the variable | 09:05 |
| juergbi | i'm not a big fan of timestamp 0, not sure whether we can come up with something better, though | 09:06 |
| tristan | baserock was using november 11, 2011 for some things | 09:06 |
| tristan | I suppose all it does is avoid weirdos (like ninja) making freaking weird assumptions about timestamps | 09:06 |
| tristan | juergbi, it would be more *correct* to dynamically set it to last mtime of Source implementation, so that... meh, not such a big bonus ? | 09:07 |
| juergbi | debian uses the timestamp of the last entry in debian/changelog, which is much nicer | 09:07 |
| tristan | maybe something like `cat --version` is going to say "Built on Jan 1, 1970" ? | 09:08 |
| tristan | nicer but... like what gain do you get from it ? | 09:08 |
| *** givascu has joined #buildstream | 09:08 | |
| tristan | We'd have to have all sources find the last mtime, which eh, seems mostly pointless | 09:08 |
| juergbi | git doesn't store mtimes, so for git it would also be the commit timestamp | 09:09 |
| tristan | that's what an mtime would be for a git source, yeah | 09:09 |
| tristan | I mean, last commit is last modification time isnt it ? | 09:09 |
| tristan | an every source would need to provide one | 09:09 |
| tristan | in some way | 09:09 |
| tristan | all so that... modules can know when they were built ? | 09:10 |
| juergbi | i thought you meant filesystem mtime with mtime | 09:10 |
| tristan | yeah I gather :) | 09:10 |
| tristan | I mean abstract Source.mtime() return value | 09:11 |
| juergbi | i'm not sure whether there would be sufficient real benefits | 09:11 |
| juergbi | i just really dislike completely fake timestamps | 09:11 |
| tristan | Ok, and adding SOURCE_DATE_EPOCH=0 means cache key breakage if we ever change that | 09:11 |
| tristan | not bad, but persia doesnt like those :) | 09:12 |
| juergbi | avoiding timestamp 0 to avoid breaking some odd software may be sensible, though | 09:12 |
| juergbi | i.e., like baserock | 09:12 |
| tristan | juergbi, lets set it to something fake, november 11th 2011 lets say... and if one day we want to do better, we will | 09:12 |
| tristan | makes sense I think ? | 09:13 |
| juergbi | ok | 09:13 |
| * tristan struggles to ask `date` to tell him the real value of human readable "Nov 11 2011 UTC" | 09:13 | |
| tristan | or UTC doesnt matter here I guess | 09:13 |
| *** ssam2 has joined #buildstream | 09:14 | |
| tristan | 1320937200 | 09:14 |
| tristan | 2011-11-11 = 1320937200 | 09:14 |
| gitlab-br-bot | push on buildstream@master (by Tristan Van Berkom): 1 commit (last: data/projectconfig.yaml: Fixes #105 - Set SOURCE_DATE_EPOCH to constant value) https://gitlab.com/BuildStream/buildstream/commit/ea3c76b1b272f7699c6ef32b164881fc7cf591a6 | 09:17 |
| gitlab-br-bot | buildstream: issue #105 ("Consider SOURCE_DATE_EPOCH effort") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/105 | 09:17 |
| *** tlater has joined #buildstream | 09:27 | |
| tristan | tlater, fyi, I'm a bit nervous about having landed the running CI as regular user thing | 09:32 |
| tristan | tlater, the pytest job failed, and then passed on a retry, and... I'm not exactly sure why | 09:32 |
| tristan | :-/ | 09:32 |
| * tlater will have a look | 09:33 | |
| tristan | Perhaps it relied on the chown thing having run once, or not, in the cache ? | 09:33 |
| tlater | tristan: I don't think so, considering I ran it on a fresh instance of the project before pushing to origin | 09:33 |
| tristan | yeah I really dont know | 09:35 |
| tristan | tlater, we might get some failing pipelines, and it might be related to that | 09:35 |
| tristan | it certainly was not a network timeout, failed somewhere in the push/pull frontend tests | 09:36 |
| * tristan gotta run though :-/ | 09:36 | |
| *** tristan has quit IRC | 09:40 | |
| *** ssam2 has quit IRC | 10:25 | |
| *** ssam2 has joined #buildstream | 10:41 | |
| gitlab-br-bot | push on buildstream@tracking-changes (by Tristan Maat): 1 commit (last: Issue #113: Split tracking and saving in `bst build`) https://gitlab.com/BuildStream/buildstream/commit/c54ec0bc9140c7955e54b137a1678f35faa8c5bd | 11:54 |
| *** givascu has quit IRC | 13:06 | |
| gitlab-br-bot | push on buildstream@tracking-changes (by Tristan Maat): 1 commit (last: Issue #113: Split tracking and saving in `bst build`) https://gitlab.com/BuildStream/buildstream/commit/ae7374b3a41531aca0c91da3b144e4d39cefdeda | 13:22 |
| gitlab-br-bot | push on buildstream@tracking-changes (by Tristan Maat): 1 commit (last: Issue #113: Split tracking and saving in `bst build`) https://gitlab.com/BuildStream/buildstream/commit/2b42f782f8589be70fa46a6d9219a15f9e7d074b | 14:07 |
| *** gitlab-br-bot has quit IRC | 15:05 | |
| ssam2 | bot is being migrated to a new host | 15:05 |
| *** gitlab-br-bot has joined #buildstream | 15:08 | |
| *** brlogger has joined #buildstream | 15:35 | |
| *** brlogger` has joined #buildstream | 15:38 | |
| ssam2 | two loggers! oh dear | 15:39 |
| *** brlogger has joined #buildstream | 15:41 | |
| *** brlogger has joined #buildstream | 15:46 | |
| ssam2 | go away brlogger! | 15:47 |
| *** brlogger has joined #buildstream | 16:09 | |
| *** brlogger has quit IRC | 16:17 | |
| *** jonathanmaw has quit IRC | 16:26 | |
| *** jude has quit IRC | 16:28 | |
| *** jude has joined #buildstream | 16:45 | |
| *** xjuan has joined #buildstream | 16:56 | |
| *** tristan has joined #buildstream | 17:03 | |
| tristan | sorry I broke tests :) | 17:04 |
| *** tiagogomes has quit IRC | 17:11 | |
| tristan | fixed | 17:17 |
| ssam2 | the gitlab bot isn't working, i'll try and fix that early next week | 17:19 |
| tlater | Aww, poor gitlab-br-bot | 17:21 |
| ssam2 | i didn't realise it needs to be able to receive http requests for the webhooks to work | 17:21 |
| tlater | tristan: Awesome, now my CI won't fail anymore ;) | 17:22 |
| *** gitlab-br-bot has quit IRC | 17:22 | |
| *** tlater has quit IRC | 17:25 | |
| *** ssam2 has quit IRC | 17:25 | |
| *** bochecha has quit IRC | 21:49 | |
| *** xjuan has quit IRC | 22:43 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!