| *** paulw has joined #trustable | 08:51 | |
| *** ecclescake has joined #trustable | 09:05 | |
| *** Shaun has joined #trustable | 10:19 | |
| *** shaunmooney has joined #trustable | 10:51 | |
| *** Shaun has quit IRC | 10:54 | |
| ikerperez | Someone understands which is the reason of this error in the CI? | 10:57 |
|---|---|---|
| ikerperez | https://gitlab.com/trustable/distros/minimal-distro/-/jobs/115717184 | 10:57 |
| ikerperez | It is happening in an old commit which previously hadn't any error and was successful in al the CI steps | 10:58 |
| ikerperez | But the same is going on in other commits and branches | 10:58 |
| paulw | flatmush, ^^ ? | 10:59 |
| flatmush | ikerperez: Yes, the private key was deleted from gitlab CI's variables | 11:00 |
| flatmush | so I had to upload a new set of keys | 11:00 |
| flatmush | which means old branches without the new key will fail | 11:00 |
| flatmush | it was not me who deleted the key, I don't know how that happened | 11:00 |
| ikerperez | ok, so I need to apply the new key for the old branches? | 11:00 |
| flatmush | if you need them to build on CI, you should rebase them against master | 11:01 |
| flatmush | or at least the commit that adds the new key | 11:01 |
| ikerperez | ok, thanks | 11:01 |
| ikerperez | flatmush afte rebasing I am having the same error | 11:08 |
| ikerperez | https://gitlab.com/trustable/distros/minimal-distro/-/jobs/115719253 | 11:08 |
| *** traveltissues has joined #trustable | 11:09 | |
| flatmush | ikerperez: That's not rebased against master | 11:12 |
| flatmush | https://gitlab.com/trustable/distros/minimal-distro/commit/b58954a70df76c53b6188c1d4d8959f781664d64 | 11:13 |
| flatmush | needs to have that commit in it | 11:13 |
| *** shaunmooney has quit IRC | 11:50 | |
| *** shaunmooney has joined #trustable | 11:50 | |
| ikerperez | o yes, sorry | 11:55 |
| ikerperez | I thought I had master updated | 11:55 |
| ikerperez | thanks! | 11:55 |
| ikerperez | #trustable FRIDAY standup | 12:02 |
| ikerperez | order: ikerperez -> jorgesanjuan | 12:02 |
| ikerperez | # Sentences | 12:02 |
| ikerperez | ## Iker Perez | 12:02 |
| ikerperez | * Done | 12:02 |
| ikerperez | - Ping Javier Jardon for help, meeting on Monday | 12:02 |
| ikerperez | * Doing | 12:02 |
| ikerperez | - Create fossology docker for trustable | 12:02 |
| ikerperez | - Understand fossology's docker container | 12:02 |
| ikerperez | - Try to run fossology in the CI from a Docker image | 12:02 |
| ikerperez | - Try to build and run fossology in the CI from source | 12:02 |
| ikerperez | - Work in the merge requests related to issues #9 and #5 | 12:02 |
| ikerperez | * Next | 12:02 |
| ikerperez | - Discover how to apply spdx to fossology | 12:02 |
| ikerperez | - Have a look to the openchain self-certify process | 12:02 |
| ikerperez | ## Jorge Sanjuan (jorgesandman) | 12:02 |
| jorgesanjuan | sorry, _o_ | 12:02 |
| ikerperez | haha | 12:03 |
| ikerperez | STANDUP ENDS | 12:03 |
| ikerperez | flatmush the key is applied but the problem persists | 12:14 |
| flatmush | it's an issue with the key, and the pipeline is working on master right? | 12:14 |
| flatmush | ikerperez: This pipeline? https://gitlab.com/trustable/distros/minimal-distro/-/jobs/115742262 | 12:16 |
| flatmush | that's not the same problem | 12:16 |
| ikerperez | No, this one: https://gitlab.com/trustable/distros/minimal-distro/-/jobs/115742132 | 12:17 |
| flatmush | ikerperez: Don't know why it failed, but re-ran the pipeline and it works | 12:23 |
| flatmush | I guess it was caching something it shouldn't | 12:24 |
| *** brlogger` has joined #trustable | 12:49 | |
| *** brlogger has quit IRC | 12:51 | |
| *** brlogger has joined #trustable | 12:55 | |
| ikerperez | Anyone knows which is the IRC nick of Mathieu Bridon? | 13:12 |
| laurence- | bochecha | 13:14 |
| laurence- | ikerperez ^ | 13:14 |
| ikerperez | thanks laurence- | 13:20 |
| *** shaunmooney has quit IRC | 13:33 | |
| laurence- | yw | 13:35 |
| ikerperez | can be deleted the projects buildstream remote cache? | 15:48 |
| ikerperez | I am having this erros in a different branch: https://gitlab.com/trustable/distros/minimal-distro/-/jobs/115859761 | 15:53 |
| ikerperez | In orde to fix it I think I could try this: https://unix.stackexchange.com/questions/251211/why-doesnt-my-systemd-user-unit-start-at-boot | 15:54 |
| ikerperez | How can I do that before building the distro? Should I patch some of the elements that are built in buildstream? | 15:55 |
| ikerperez | flatmush, ctgriffiths,tiagogomes ^^ | 16:07 |
| ctgriffiths | why are you trying to start docker? | 16:10 |
| flatmush | ikerperez: I can delete the cache, but that's kinda the nuclear option | 16:11 |
| ctgriffiths | unless I've misunderstood you're trying to run the docker systemd service inside a docker container | 16:12 |
| ikerperez | I am trying to start docker because fossology runs in docker | 16:15 |
| ikerperez | flatmush I have been talking with bochecha and he thinks that something may be wrong with the server cache ssl configuration | 16:16 |
| flatmush | ikerperez: It was setup according to the documentation | 16:16 |
| flatmush | the only hiccup was that a key was deleted so it's running with new keys now | 16:17 |
| ikerperez | I don't say it is has been wrongly set, but maybe because of the key change now it is complaining | 16:17 |
| flatmush | I don't really know what to do about that | 16:18 |
| ctgriffiths | I think the prefered solution is to expose the docker socket to the CI container, this would be configured on the gitlab runner: https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/ | 16:18 |
| ikerperez | the ABU check keeps complaining although I have changed, so it might be that it is trying to check some resources that were generated with the previous key | 16:18 |
| ctgriffiths | rather than a fresh install inside a docker container | 16:19 |
| ikerperez | ctgriffiths I will have a look to that now | 16:19 |
| ikerperez | thanks | 16:19 |
| flatmush | the ssh key issue should only affect the building of previous branches, the artifacts themselves should be identical | 16:21 |
| ikerperez | I don't know which is the issue, but in the logs can be read "Invalid private key." so it is probably something related to it | 16:37 |
| tiagogomes | where does it show that? | 16:44 |
| ikerperez | https://gitlab.com/trustable/distros/minimal-distro/-/jobs/115758367 | 16:45 |
| ikerperez | Could be the reason be that in the project.conf in line 131 says " url: https://cache.trustable.io:11001" and in the Ci says " url: https://cache.trustable.io:11002" | 16:46 |
| ikerperez | https://gitlab.com/trustable/distros/minimal-distro/blob/master/project.conf | 16:46 |
| ikerperez | https://gitlab.com/trustable/distros/minimal-distro/blob/master/.gitlab-ci.yml | 16:46 |
| ikerperez | flatmush^^ | 16:46 |
| tiagogomes | aah | 16:51 |
| *** ecclescake has quit IRC | 16:57 | |
| flatmush | ikerperez: No, that's correct | 17:03 |
| flatmush | 11001 is the public cache | 17:03 |
| flatmush | the CI uses the private cache because it pushes | 17:03 |
| flatmush | the private cache is 11002 | 17:03 |
| flatmush | so it's deliberate that the CI uses that cache | 17:03 |
| *** jorgesanjuan has quit IRC | 17:22 | |
| *** tiagogomes has quit IRC | 18:01 | |
| *** traveltissues has quit IRC | 20:26 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!