*** mthebeau has quit IRC | 00:09 | |
*** bengates has joined #starlingx | 07:05 | |
*** bengates has quit IRC | 07:05 | |
*** bengates has joined #starlingx | 07:06 | |
*** zbsarash1 has quit IRC | 07:59 | |
*** hyunsikyang has joined #starlingx | 12:47 | |
*** billzvonar has joined #starlingx | 12:48 | |
*** hyunsikyang__ has quit IRC | 12:50 | |
*** zbsarash1 has joined #starlingx | 13:54 | |
*** sgw has quit IRC | 13:57 | |
*** Samiam1999DTP has quit IRC | 14:11 | |
*** Samiam1999DTP has joined #starlingx | 14:11 | |
*** sgw has joined #starlingx | 14:14 | |
sgw | Morning all | 14:14 |
---|---|---|
*** dpanech has joined #starlingx | 14:25 | |
dpanech | hi all | 14:26 |
sgw | dpanech: you made it! | 14:27 |
dpanech | yes :) so are you having any specific problems with Jenkins? How can I help? Also: I meant I was port-forwarding the web port over SSH, not VNC... | 14:36 |
*** mthebeau has joined #starlingx | 14:48 | |
sgw | dpanech: that's what I tried to do also, but it's just really to slow an not usable for me. My idea is to create a local jenkins instance and then import (if that's possible) the cengn configuration | 15:07 |
sgw | that way I can do some testing on changes like removing "pike" simple stuff to start with | 15:07 |
sgw | dpanech: I know that slittle1 ties to keep a git repo of the jenkins configation | 15:08 |
*** dirk has quit IRC | 15:38 | |
*** bengates_ has joined #starlingx | 16:14 | |
*** bengates has quit IRC | 16:16 | |
*** bengates_ has quit IRC | 16:25 | |
*** bengates has joined #starlingx | 16:26 | |
slittle1 | hi all | 16:38 |
slittle1 | sgw: let me update the git repo for cengn | 16:43 |
sgw | Hi Scott! thanks, but it's more than that, I am not sure how I can create a development version of Jenkins that I can test with locally, I am barely a Jenkins user, let alone a jenkins admin/maintainer person. | 16:54 |
*** bengates has quit IRC | 16:58 | |
*** bwensley has joined #starlingx | 17:21 | |
sgw | slittle1: dpenney: I am just doing some tests with different initrd.img files 1 from layer'ed build and one from monolithic, but everything else from layer'ed. The initrd seems to be the problem, have not dug into it further yet. If I use the monolithic initrd.img file it works | 20:31 |
slittle1 | I've posted my prelim findings | 20:34 |
slittle1 | https://review.opendev.org/#/c/727908 failed to uprev kmods | 20:35 |
slittle1 | layered build uses build avoidance, so kmods did not rebuilds | 20:36 |
slittle1 | so the layered initrd contains kmods for an older kernel | 20:36 |
slittle1 | I'll generate a gerrit review to increment the kmod versions as the short term fix | 20:37 |
slittle1 | posted https://review.opendev.org/730122 | 20:47 |
slittle1 | I'll start looking into extending Don's work around enhanced GITREVCOUNTs | 20:54 |
sgw | slittle1: I was going to ask about that, but I am not sure it would work because it | 21:12 |
sgw | 'because it's based on the directory the packages are in. I wonder if you just use GITREVCOUNT itself? | 21:13 |
sgw | That might be too agressive for rebuilds? | 21:14 |
dpenney | starlingx-dashboard makes use of GITREVCOUNT on itself, so you could do that for these. Advantage of having a REPO_GITREVCOUNT would be that it wouldn't need SRC_DIR set | 21:24 |
dpenney | but I think if the stx/kernel pkgs used SRC_DIR=. (if they don't have a SRC_DIR already), they'd just need TIS_BASE_SRCREV set to an older SHA... (REPO_GITREVCOUNT could also make that SRCREV optional) | 21:25 |
*** billzvonar has quit IRC | 21:33 | |
slittle1 | I don't plan on using GITREVCOUNT on the full krenel repo | 22:59 |
slittle1 | Can we get https://review.opendev.org/#/c/730122/ approved before tonight's build ? | 23:00 |
sgw | Sure | 23:03 |
dpenney | W+1 | 23:08 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!