*** mike has joined #baserock | 07:39 | |
*** mike is now known as Guest5251 | 07:40 | |
*** a1exhughe5 has joined #baserock | 08:10 | |
*** gfinney has joined #baserock | 08:15 | |
*** jonathanmaw has joined #baserock | 08:22 | |
*** mdizzle has joined #baserock | 08:36 | |
*** mdunford has joined #baserock | 09:01 | |
*** bashrc_ has joined #baserock | 09:01 | |
*** rdale has joined #baserock | 09:07 | |
*** rdale has quit IRC | 09:17 | |
*** rdale has joined #baserock | 09:19 | |
*** mdizzle has quit IRC | 09:29 | |
*** mdizzle has joined #baserock | 09:31 | |
*** mdizzle has quit IRC | 09:36 | |
*** mdizzle has joined #baserock | 09:37 | |
*** franred has joined #baserock | 09:47 | |
*** tiagogomes_ has joined #baserock | 09:49 | |
*** CTtpollard has joined #baserock | 09:51 | |
*** ssam2 has joined #baserock | 09:57 | |
*** ChanServ sets mode: +v ssam2 | 09:57 | |
*** gary_perkins has joined #baserock | 09:58 | |
*** paulwaters_ has quit IRC | 09:59 | |
*** paulw has joined #baserock | 10:03 | |
ssam2 | wow, lots of patches in Gerrit now | 10:23 |
---|---|---|
ssam2 | cool! | 10:23 |
*** wschaller has joined #baserock | 10:23 | |
*** flatmush1 is now known as flatmush | 10:28 | |
CTtpollard | is the stance still no to a bot that announces gerrit merges? | 10:29 |
richard_maw | kejiahu: I've worked out what's gone on with your gawk problem. Upstream's latest release build is broken | 10:29 |
Kinnison | So we need to roll backwards on gawk a bit, or is there a fix in their repo? | 10:30 |
richard_maw | gawk-4.1.0-367-gcd99e34 is the earliest point where it was fixed | 10:30 |
richard_maw | Kinnison: development head has a fix, but no release includes it yet | 10:30 |
kejiahu | richard_maw: thanks, I will try that one | 10:30 |
straycat | CTtpollard, i'd like one | 10:33 |
richard_maw | kejiahu: in the absence of a proper release, it may even be better to pick the head of the gawk-4.1-stable branch | 10:33 |
straycat | CTtpollard, i'd like one for submissions too | 10:34 |
radiofree | hello! | 10:37 |
straycat | hello! | 10:37 |
radiofree | building an armv7b build-system, get this error with libusb http://fpaste.org/201346/14271070/ | 10:37 |
CTtpollard | I think I brought it up before, but it was a mixed response | 10:37 |
radiofree | "Too many mounts (maximum of 50)" ? | 10:37 |
richard_maw | old version of linux-user-chroot | 10:37 |
radiofree | yeah i am building this on a baserock 8 system :\ | 10:38 |
straycat | CTtpollard, i would argue anyone who doesn't want to receive messages from a gerrit bot can put the bot on their ignore list | 10:38 |
radiofree | i have bootstrapped a new armv7b system, perhaps i should start again from there | 10:38 |
CTtpollard | straycat: my view exactly | 10:38 |
radiofree | richard_maw: is http://git.baserock.org/cgi-bin/cgit.cgi/delta/linux-user-chroot.git/log/?h=baserock/morph still the version we're using? | 10:39 |
richard_maw | radiofree: yes | 10:40 |
radiofree | ta | 10:40 |
ssam2 | tpollard,straycat: good point actually, I hadn't thought of that and no longer object | 10:48 |
*** jonathanmaw has quit IRC | 10:56 | |
*** Krin has joined #baserock | 10:57 | |
*** jonathanmaw has joined #baserock | 10:58 | |
* pedroalvarez fails to fetch a commit from a review in gerrit to test it | 11:00 | |
SotK | I think you need to use git-review to get the commits somehow | 11:02 |
SotK | or fetch it from a weird ref | 11:02 |
ssam2 | refs/changes/nn/nn | 11:14 |
ssam2 | but because 'git remote update' / 'git fetch' only pull refs/heads/* and refs/tags/* by default, you have to manually do `git fetch gerrit refs/changes/nn/nn; git checkout FETCH_HEAD -b change-nnn` | 11:14 |
ssam2 | or use git-review | 11:15 |
jjardon | mmm, seems some commit has not be applied? (I do not see the xserver upgrade in definitions master) but gerrit said it did: http://gerrit.baserock.org/#/c/46/ | 11:23 |
jjardon | neither http://gerrit.baserock.org/#/c/45/ | 11:27 |
pedroalvarez | odd and worrying | 11:28 |
* Kinnison doesn't like the sequence of reviews on that | 11:28 | |
Kinnison | is that how Gerrit works? | 11:28 |
Kinnison | i.e. that the author gets to +2 their patch? | 11:29 |
pedroalvarez | in this case, the author, which is also in the mergers group, acted as a merger and decided that the two +1's were valid, and then +2ed the patch and merged | 11:30 |
richard_maw | Kinnison: I don't think there's anything fundamentally wrong with that, since +2 is just the final "yes, please merge this bot!", and sometimes as a reviewee you want to review the reviews to see if you think they're appropriately rigorous | 11:30 |
richard_maw | Kinnison: but AIUI the intention is to add Zuul to do the +2 later anyway | 11:30 |
Kinnison | Aah I see | 11:31 |
Kinnison | so the two +1s, plus the absence of any -1s permitted the merger to push the "merge it" button which is recorded as a +2 ? | 11:31 |
*** edcragg has joined #baserock | 11:31 | |
Kinnison | Okay | 11:31 |
* straycat notices that large changes seem to be being submitted as single commits | 11:31 | |
Kinnison | I fear that's how gerrit works | 11:32 |
SotK | I think the problem was that the "merge it" button doesn't appear until there is an explicit +2 | 11:32 |
Kinnison | SotK: aah | 11:32 |
straycat | We do need to figure out how to submit series to it, otherwise I'd sooner use the ml personally | 11:32 |
*** mdunford has quit IRC | 11:33 | |
SotK | I don't think you can | 11:33 |
SotK | Gerrit's "patch series" support is the topic stuff | 11:33 |
pedroalvarez | I've already seen "patch series" in gerrit | 11:34 |
kejiahu | richard_maw: HEAD of 4.1 stable fixed the gawk issue, the build is carrying on to see if there is any more issue. thanks for your help | 11:35 |
richard_maw | no worries kejiahu | 11:35 |
* richard_maw just attempted to tab-complete the phrase "no worries", since he uses it so often | 11:35 | |
straycat | topic stuff? | 11:38 |
* richard_maw just got linked to http://dachary.org/?p=2917 | 11:39 | |
SotK | straycat: the name in brackets in the Branch column of the changes page | 11:39 |
richard_maw | the rough idea appears to be "submit your patch series with this command-line tool and it'll submit all your changes and put dependencies in to string them together" | 11:40 |
straycat | okay | 11:41 |
* Kinnison worries that the default behaviour of gerrit is not to support patch series | 11:42 | |
* Kinnison thought work had been done to allow them | 11:42 | |
bashrc_ | gerrit isn't ideal. I don't know what the rationale was for using it | 11:44 |
Kinnison | It's better than everything we had before :) | 11:44 |
Kinnison | and it's already there | 11:44 |
richard_maw | and OpenStack is using it | 11:44 |
Kinnison | and used by many projects, which means there's lots of engineers familiar with it | 11:44 |
* Kinnison is just a whingy git :) | 11:45 | |
richard_maw | you know what they say, there's two kinds of tools, those which everyone complains about, and those which nobody uses | 11:46 |
Kinnison | :) | 11:46 |
*** mdunford has joined #baserock | 11:48 | |
* straycat expected to be able to review a series from the cli with the git-review tool, and to view patches with the same topic in some sane way | 11:53 | |
persia | straycat: Have you looked at gertty? | 11:57 |
straycat | no i'll check it out thanks | 11:58 |
ssam2 | I think it's actually not too bad having to submit things as individual commits | 11:59 |
ssam2 | we have cases where someone submits a patch series to the mailing list and someone else goes "this is too big to review, please split it up into smaller parts" | 12:00 |
ssam2 | Gerrit kind of enforces splitting up big changes | 12:00 |
straycat | i think it's pretty terrible because it completely screws my ability to linearly explain what i'm trying to do | 12:01 |
ssam2 | it can makes things more awkward, yeah. Perhaps in that case, drop a cover letter to the mailing list listing all of the changes and explaining the order that they make sense | 12:03 |
bashrc_ | unfortunately the consequence of that could be people submitting large patches as a single commit | 12:03 |
straycat | that's basically every case, then | 12:03 |
persia | Indeed: for large things, sending mail to the list with explanations can be useful. | 12:03 |
straycat | and putting it in the cover letter means it's not in the git history | 12:03 |
persia | bashrc_: That ought be cause for -1 | 12:03 |
straycat | (the explanation of my changes) | 12:03 |
ssam2 | straycat: cover letters already aren't in the git history | 12:03 |
ssam2 | and we use them | 12:03 |
persia | straycat: Yes, but if you use a topic, they should generally land together, in order. | 12:03 |
straycat | ssam2, i put the explanation in the patch | 12:04 |
ssam2 | then I don't see a problem... | 12:04 |
straycat | that's what a series allows me to do, to build up a linear explanation that goes into the git history for anyone to review and digest later | 12:04 |
ssam2 | you can submit a change to Gerrit that depends on another change | 12:05 |
ssam2 | first you push change A, then you push a branch with both change A and change B | 12:05 |
straycat | sure, if a topic works and the gerrtty tool allows sane review of that then that's cool, but i don't agree with your initial statement that it's useful that we're being coerced into submitting things as individual commits | 12:05 |
straycat | if that were useful we'd be doing it already | 12:06 |
ssam2 | fair enough | 12:07 |
* SotK submitted his partial builds patch series by doing `git push gerrit HEAD:refs/for/master/baserock/adamcoldrick/partial-builds` whilst I had my baserock/adamcoldrick/partial-builds branch checked out and I'm pretty sure that came out in the right order with the dependencies right | 12:08 | |
ssam2 | 30 seconds of gerrit downtime coming up while I test backup automation again. sorry | 12:27 |
* pedroalvarez is sitll worried about why things are not in g.b.o after they have been merged in gerrit | 12:28 | |
pedroalvarez | e.g. http://gerrit.baserock.org/#/c/45/ | 12:28 |
jjardon | yeah, me too. ssam2 (or other) maybe you can take a look to the logs and see if there is something strange? | 12:29 |
ssam2 | good point, will do | 12:29 |
ssam2 | probably a merge conflict between gerrit's master and git.baserock.org's master | 12:29 |
*** wschaller has quit IRC | 12:53 | |
*** wschaller has joined #baserock | 13:10 | |
SotK | so, its impossible to deploy a minimal system at the moment | 13:27 |
richard_maw | SotK: what's broken? | 13:27 |
SotK | it doesn't use systemd, but it has simple-network.configure in its configure extensions | 13:28 |
SotK | which expects systemd to be used | 13:28 |
SotK | things like "ERROR: [Errno 2] No such file or directory: '/srv/distbuild/tmp/deployments/tmpIy3eIZ/tmpmfch7p/overlay-deploy-minimal-system-x86_64-generic-rootfs/etc/systemd/network/50-e*.network'" happen | 13:29 |
richard_maw | SotK: is it failing because there's no /etc/systemd/network directory, or because /etc/systemd/network/10-dhcp.network doesn't exist? | 13:29 |
richard_maw | jjardon: ^^ | 13:29 |
richard_maw | I don't care much about whether it drops networkd config in which won't be used, but we need to make it work even when the /etc/systemd/network directory doesn't exist | 13:30 |
*** petefoth has quit IRC | 13:31 | |
persia | I thought we were careful to complain about all the systemd-networkd patches and make sure that got tested with minimal. | 13:41 |
persia | Would adding minimal to the mason runs help avoid this? We really want to support the non-systemd case. | 13:41 |
ssam2 | adding the minimal systems to clusters/ci.morph might indeed make sense | 13:48 |
straycat | is anyone here using gertty? i think i need to generate a http password for it, but when i try to do this on gerrit.baserock.org it gives a 'working... | 13:49 |
straycat | ' notifaction, but no password gets generated | 13:49 |
ssam2 | the 'generate password' thing in gerrit seems really buggy | 13:49 |
straycat | *notification | 13:49 |
straycat | Oh | 13:49 |
ssam2 | try going to a different page, and going back to the settings page again, keep clicking the button | 13:49 |
straycat | it just worked | 13:49 |
ssam2 | it worked for me in the end | 13:49 |
pedroalvarez | and it just worked for me too | 13:49 |
ssam2 | i've not investigated reporting a bug upstream yet, but there's definitely something wrong with it | 13:50 |
* bashrc_ notices that in 14.x versions the morph definitions were all over the place | 13:51 | |
straycat | you mean chunk morphs in chunk repos? | 13:51 |
bashrc_ | no separate subdirectories | 13:52 |
*** petefoth has joined #baserock | 13:53 | |
pedroalvarez | it's much better now | 13:58 |
jjardon | SotK: I can not look at that at the moment; can you file a bug in the storyboard an assign it to me, so I do not forget? | 14:10 |
SotK | jjardon: sure | 14:10 |
jjardon | SotK: thanks | 14:10 |
straycat | gertty didn't seem too great so i'm trying gerrymander except i have an issue caused by the following: | 14:35 |
straycat | richardipsum salo ~ $ ssh review gerrit stream-events | 14:35 |
straycat | Capability streamEvents is required to access this resource | 14:35 |
* pedroalvarez is still trying to get gertty working :/ | 14:39 | |
straycat | given it ran for around 30seconds with no output while presumably populating its database i don't hold much hope for it | 14:39 |
Kinnison | straycat: admins are given streamevents automatically, everyone else has to be explicitly granted it | 14:40 |
straycat | ahh | 14:42 |
straycat | http://sprunge.us/QbdC huzzah! | 14:42 |
Kinnison | cool | 14:42 |
straycat | i guess someone will have to grant me streamevents if i want to use the 'watch' command | 14:43 |
ssam2 | cool | 14:47 |
ssam2 | I can look into streamevents if you want, presumably there's some reason gerrit doesn't allow it by default | 14:47 |
ssam2 | if I can't find a reason, i'll enable it for everyone | 14:47 |
* SotK notes it will probably need to be enabled for Zuul when we get to that | 14:48 | |
*** wschaller_ has joined #baserock | 14:57 | |
*** wschaller has quit IRC | 15:00 | |
straycat | cool | 15:01 |
*** gfinney has quit IRC | 15:03 | |
*** gfinney has joined #baserock | 15:03 | |
*** gfinney has quit IRC | 15:05 | |
*** gfinney has joined #baserock | 15:05 | |
*** gfinney_ has joined #baserock | 15:06 | |
*** jonathanmaw_ has joined #baserock | 15:36 | |
*** jonathanmaw has quit IRC | 15:36 | |
ssam2 | git.baserock.org seems unresponsible over SSH. not sure why yet | 15:44 |
* straycat manages to comment from cli with ` richardipsum salo ~ $ ssh review gerrit review --code-review 0 -m "'This is a test comment from a cli'" 6fe11cd320332f9c24ca17ba2f9c1bdb323cc213' | 15:45 | |
straycat | https://blogs.gnome.org/markmc/2011/09/25/gerrit-patch-review-from-the-command-line/ | 15:45 |
* Kinnison is confused as to what those characters are in straycat's prompt | 15:46 | |
straycat | mad unicode courtesy of powerline shell | 15:46 |
Kinnison | Whatever you're pasting my shell insists isn't valid utf8 | 15:47 |
straycat | oh? i thought it was | 15:47 |
Kinnison | perhaps screen is squiffing it | 15:48 |
kejiahu | is git.baserock.org down? | 15:54 |
ssam2 | there seems to be an issue at the hosting provider for some baserock.org instances. git.baserock.org and cache.baserock.org are both unresponsive for me. | 16:03 |
ssam2 | I've raised a support ticket | 16:03 |
*** jonathanmaw_ has quit IRC | 16:03 | |
ssam2 | I have an existing SSH session into the 'frontend' machine, and while it's responsive, I can't run any commands | 16:03 |
ssam2 | so seems like IO is broken | 16:03 |
kejiahu | it was quite unstable since this morning. and now it's completely unaccessible | 16:03 |
*** jonathanmaw has joined #baserock | 16:03 | |
*** brlogger` has quit IRC | 16:03 | |
*** brlogger has joined #baserock | 16:03 | |
Kinnison | 16:03 <+statusbot> Status update: We're investigating an issue that's affecting access to instances hosted on our compute and storage platforms. Further updates to | 16:05 |
Kinnison | follow. -- http://status.datacentred.io | 16:05 |
Kinnison | just appeared on the hosting company's channel | 16:05 |
DavePage | Kinnison: I was just about to paste that :) | 16:05 |
Kinnison | :) | 16:05 |
pedroalvarez | in the meantime I managed to ssh in git.baserock.org | 16:08 |
Kinnison | yay | 16:08 |
pedroalvarez | and looks like cgit is working again | 16:08 |
SotK | \o/ | 16:08 |
Kinnison | So minor hiccough | 16:09 |
pedroalvarez | I hope :0 | 16:09 |
pedroalvarez | :) | 16:09 |
* straycat doesn't see a way to do inline comments from a cli yet | 16:09 | |
straycat | SotK, send it to the ml? | 16:10 |
straycat | or point out that the previous is on the ml if you submit to gerrit | 16:10 |
SotK | I think I'll send it to the ml | 16:11 |
pedroalvarez | i know is not ideal for some users, but it's possible to do comments in the web UI of gerrit | 16:11 |
SotK | I worry that submitting it to Gerrit will cause at least one of (a) about 20 commits being sent to Gerrit, (b) merge conflicts | 16:11 |
straycat | pedroalvarez, yup but no way to do that from the cli | 16:13 |
pedroalvarez | hmm | 16:13 |
straycat | SotK, which would be 20 new changes, but at least on the same topic? >.> | 16:13 |
ssam2 | SotK: is there really no way to break it up into separate topics | 16:13 |
ssam2 | ? | 16:14 |
ssam2 | Gerrit is used by several big projects, there must be ways of doing this sensibly | 16:14 |
SotK | ssam2: my branch depends on my OSTree branch which is on the mailing list | 16:14 |
ssam2 | ah, so it depends on something outside of Gerrit | 16:14 |
SotK | if I push just the two commits for partial deployment they won't make any sense | 16:14 |
SotK | yes | 16:15 |
ssam2 | probably fair to send it to the list as well then | 16:15 |
SotK | hopefully its the last one I send to the list! :) | 16:15 |
jjardon | ssam2: any idea what happened with the "missing" commits? should I send the patches again? | 16:16 |
ssam2 | just going to investigate now that the infra is back up | 16:16 |
Kinnison | Apparently Gerrit 2.11 and later support submitting comments over ssh | 16:16 |
Kinnison | cf. http://code.google.com/p/gerrit/issues/detail?id=602 | 16:16 |
jjardon | ssam2: thanks, sorry for rushing :) | 16:17 |
ssam2 | Gerrit's REST API is also really good, wouldn't be too hard to write a wrapper tool if none of the existing ones suit you | 16:19 |
jjardon | Kinnison: nice, unfortunately there is not a stable 2.11 release yet (but a promising v2.11-rc1 tag is already in the "stable-2.11" branch) | 16:19 |
Kinnison | :) | 16:20 |
* Kinnison gets the impression 2.11 has been a long-time coming | 16:20 | |
Kinnison | Given it was last july that issue 602 was marked "fixed in 2.11" | 16:21 |
straycat | Kinnison, you can already submit comments over ssh, but not inline comments | 16:24 |
Kinnison | straycat: yes, 2.11 is supposed to extend that suppotr | 16:26 |
ssam2 | jjardon: i don't see any missing changes in master of morph or definitions | 16:26 |
ssam2 | http://gerrit.baserock.org/#/c/45/ is merged to master of morph.git in git.baserock.org and gerrit.baserock.org | 16:26 |
straycat | Kinnison, okay i see | 16:27 |
jjardon | ssam2: what about http://gerrit.baserock.org/#/c/46 ? | 16:29 |
jjardon | (sorry for the previous one) | 16:30 |
pedroalvarez | I failed to see that it was for morph.git :/ | 16:32 |
ssam2 | jjardon: hmm, that does seem to be missing | 16:33 |
tlsa | http://paste.baserock.org/bajawequyo <-- can anyone help me with pushing to gerrit? | 16:40 |
tlsa | My changes have change-ids | 16:40 |
straycat | why are we not using https on gerrit.baserock.org? | 16:42 |
Kinnison | Lack of SSL certificate right now I imagine | 16:43 |
straycat | right, so that's why i can't use gertty i think | 16:43 |
* straycat sighs | 16:44 | |
jjardon | tlsa: mmm, it should work. try yo remove tlsa from for/master/tlsa/certify-reproducibility ? | 16:45 |
ssam2 | I've requested Codethink get a certificate for us, it's being looked in to | 16:45 |
ssam2 | tlsa: could you paste the output of 'git log master..HEAD' somewhere? | 16:46 |
tlsa | ok | 16:47 |
tlsa | http://paste.baserock.org/tafeqayapi | 16:48 |
tlsa | jjardon: my branch is tlsa/certify-reproducibility | 16:49 |
ssam2 | tlsa: are you trying to push all of those 4 at once? | 16:49 |
tlsa | http://git.baserock.org/cgi-bin/cgit.cgi/baserock/baserock/morph.git/log/?h=tlsa/certify-reproducibility | 16:49 |
tlsa | ssam2: yes | 16:49 |
ssam2 | I think you need to push each new change to refs/for/master/tlsa/xx individually | 16:49 |
ssam2 | although if that's the problem, the error message given is a complete joke | 16:49 |
tlsa | I thought more than one worked from what SotK said earlier | 16:50 |
jjardon | Doesnt matter whats the name of tour branch, you are setting the "topic" of the group of commits there | 16:52 |
tlsa | http://paste.baserock.org/peqewemuyi | 16:52 |
ssam2 | tlsa: I think that you can push a branch which contains existing unmerged changes, but not a branch that contains more than one new change | 16:52 |
tlsa | jjardon: oh, ok | 16:52 |
ssam2 | jjardon: do you know when 'submit' was pressed for http://gerrit.baserock.org/#/c/46/ ? | 16:53 |
tlsa | jjardon: same rejection without the "tlsa/" | 16:53 |
ssam2 | jjardon: today about 10:28:39 ? | 16:53 |
ssam2 | if so, no errors in the log (except for 'failed to send email') | 16:54 |
pedroalvarez | :/ | 16:55 |
pedroalvarez | he pointed it out at 11:23 | 16:55 |
ssam2 | could be https://code.google.com/p/gerrit/issues/detail?id=2094 but that suggests there'd be an error in the log file | 16:55 |
ssam2 | and it purports to be fixed in 2.8 | 16:56 |
jjardon | ssam2: yeah, 10:28 sound rigth | 16:57 |
jjardon | sounds* | 16:57 |
jjardon | tlsa: Its definitely possible to send a branch with several commits: gerrit will order them correctly with the same "topic" | 16:58 |
* jjardon taking a look to the logs again | 16:58 | |
ssam2 | there seem to be intermittent errors in the Gerrit logs where it can't access the database | 17:02 |
rjek | related to the other data centre problems? | 17:06 |
*** jonathanmaw has quit IRC | 17:07 | |
*** a1exhughe5 has quit IRC | 17:10 | |
ssam2 | jjardon: I've manually fixed http://gerrit.baserock.org/#/c/46/ and made it actually get merged | 17:10 |
jjardon | ssam2: cheers | 17:10 |
ssam2 | had to click 'cherry-pick', then +2 it myself | 17:10 |
ssam2 | I've no idea why this happened, so please look out for it happening again | 17:11 |
richard_maw | ssam2: could it be a race between the fetch+merge and the push involved? If there was a change from another source to morph.git and the merger isn't capable of handling conflicts then it might just get dropped | 17:12 |
ssam2 | richard_maw: the merger should be capable of handling and reporting conflicts, but it's possible that there was a race | 17:13 |
jjardon | ssam2: I wonder if we can change the policy to rebase before merge? I feel that we will have a lot of usefulness merge commits if not (before makes sense because we put the review info there) | 17:13 |
ssam2 | changing policy might help indeed | 17:14 |
straycat | ssam2, we could have a self-signed for now? | 17:14 |
ssam2 | straycat: that would be extra work and would only result in people complaining about the self-signed cert. may as well do it properly | 17:14 |
radiofree | ooh, lovely coloured dmesg in baserock master | 17:15 |
* straycat shrugs | 17:15 | |
straycat | also a little surprised there's no comment on the RFC for branching morph, given that's a pretty big change | 17:15 |
ssam2 | at present rate I should have some time free to do code review in about 2016 | 17:15 |
straycat | fair enough | 17:16 |
* straycat goes home | 17:16 | |
*** gfinney_ has quit IRC | 17:28 | |
*** mdizzle has quit IRC | 17:37 | |
pedroalvarez | hm.. | 17:40 |
* pedroalvarez is sad because his comments in the ML regarding mox3 were ignored | 17:41 | |
pedroalvarez | the patch was also sent to gerrit | 17:41 |
tlsa | ooh, I've done something that has changed the reason why gerrit rejects my patchs | 17:43 |
tlsa | [remote rejected] HEAD -> refs/for/master/certify-reproducibility (n/a (unpacker error)) | 17:43 |
tlsa | was (no new changes) | 17:43 |
Kinnison | that's the git packer change | 17:44 |
Kinnison | there's a flag to pass | 17:44 |
Kinnison | rdale: had the same issue | 17:44 |
rdale | i needed a '--no-thin' option when doing a push | 17:49 |
tlsa | yep, just found that on stackoverdlow | 17:50 |
jjardon | maybe of the interest of the infrastructure team: http://gitenterprise.me/2015/03/22/zero-downtime-git-and-gerrit-code-review-googlesource-com/ | 17:50 |
tlsa | well, that finally tel me push the series, but I'm not sure how the original (no new changes) rejection went away :s | 17:51 |
ssam2 | jjardon: feel free to start writing a custom database backend for Gerrit :) | 17:52 |
* jjardon runs | 17:52 | |
ssam2 | tlsa: it does seem that Gerrit's error messages are pretty unhelpful. Perhaps you can report a bug | 17:52 |
tlsa | s/tel/let/ | 17:52 |
*** gary_perkins has quit IRC | 17:58 | |
*** bashrc_ has quit IRC | 18:01 | |
*** edcragg has quit IRC | 18:09 | |
*** Guest5251 has quit IRC | 18:10 | |
*** mdunford has quit IRC | 18:14 | |
*** ssam2 has quit IRC | 18:20 | |
*** tiagogomes_ has quit IRC | 18:21 | |
*** Krin has quit IRC | 18:25 | |
jjardon | mmm, getting the cache from cache.baserock.org feels very slow, anyone more with this problem? | 18:39 |
pedroalvarez | jjardon: save some logs to look at how long takes to fetch some artifacts tomorrow | 18:43 |
jjardon | also mason is red, same error as other times: | 18:43 |
pedroalvarez | Also, this can be a problem of your network | 18:43 |
jjardon | 2015-03-23 16:03:49 Progress: Transferring pulseaudio-doc to shared artifact cache | 18:43 |
jjardon | 2015-03-23 16:04:02 Build of pulseaudio-doc failed. | 18:43 |
pedroalvarez | Uh | 18:43 |
jjardon | maybe, will go home and try there | 18:44 |
pedroalvarez | Mason error might be related with fetching artifacts | 18:44 |
pedroalvarez | Cache server misbehaving.. | 18:44 |
pedroalvarez | 17G free, no space problems this time | 18:45 |
*** tlsa has quit IRC | 19:04 | |
*** tlsa has joined #baserock | 19:04 | |
*** wschaller_ has quit IRC | 19:06 | |
radiofree | pedroalvarez: could you not give it more HD space? | 22:18 |
radiofree | it seems like you're constantly fighting with lack of space | 22:18 |
rjek | Evening. | 22:46 |
pedroalvarez | it wasn't space this time, but yes, I've been thinking about that | 23:51 |
pedroalvarez | mason failed this time for the same reason that git.baserock.org had problems today: The hosting company had a minor hiccough. | 23:52 |
pedroalvarez | also, the new version of tar is causing problems when building lsof (which uncompresses a file in the configure commands): http://mason-x86-32.baserock.org/log/85f0c8e334c712054b1196e7d70efc2bdeac1dbe--2015-03-23%2023:20:53.log | 23:53 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!