Apache Allura / Chat

Apache Allura / Chat is hosted on FreeNode IRC channel #allura

Log for 2013-04-23

  • 13:28:44
    allura-ci

    Project forgehg build #98: UNSTABLE in 6.2 sec: http://engr.geek.net/hudson/job/forgehg/98/

  • 13:28:44
    allura-ci
    • Cory Johns: [#6083] Improved empty repo checking
  • 13:28:45
    allura-ci
    • Tim Van Steenburgh: [#6083] Change empty repo msg text
  • 13:29:55
    cory_fu

    ImportError: No module named allura.tests.decorators

  • 13:30:10
    cory_fu

    Um, I think you'll find that there quite is such a module, my friend.

  • 13:31:18
    cory_fu

    However, allura is failing becuase testfixtures wasn't added to our local mirror

  • 13:35:21
    cory_fu

    And yet Dave claims otherwise. Hrm

  • 13:36:40
    tvansteenburgh

    i added it last night

  • 13:39:05
    tvansteenburgh

    i think those will both fix themselves

  • 13:40:18
    ctsai-sf

    via #sourceforge:

  • 13:40:20
    ctsai-sf

    there is a bug in in the projects git branch view if there's an / in the branch name

  • 13:40:33
    ctsai-sf

    Is that known? Do we have a ticket for that? --^

  • 13:41:08
    tvansteenburgh

    i'm reviewing the fix now

  • 13:41:19
    tvansteenburgh
  • 13:41:39
    ctsai-sf

    Ah, thanks.

  • 13:48:56
    wjp

    that ticket is an excellent example of where displaying comments and metadata changes need improving, by the way

  • 13:56:08
    tvansteenburgh

    wjp: can you elaborate?

  • 13:57:09
    wjp

    scanning through the comments/history of that ticket is very inefficient

  • 13:58:00
    wjp

    because metadata changes take up more vertical space than is really justified and there is only a limited number of comments on a single page

  • 13:59:08
    tvansteenburgh

    good point about the metadata waste

  • 14:00:13
    brondsem

    yep, definitely. I've even poked around at the CSS a little bit trying to do a quick fix, but didn't have the time/skills to make a fast fix

  • 14:00:40
    tvansteenburgh

    and i agree about the paged comments too. seems like we might have a ticket for that already but not sure

  • 14:01:03
    brondsem

    [#5709] for that

  • 14:01:09
    tvansteenburgh

    cool

  • 14:56:41
    allura-ci

    Project forgehg build #99: STILL UNSTABLE in 3.4 sec: http://engr.geek.net/hudson/job/forgehg/99/

  • 14:56:42
    allura-ci
    • Tim Van Steenburgh: [#5120] Fixed branches with / in them
  • 14:56:42
    allura-ci
    • Tim Van Steenburgh: [#5120] Bump version
  • 14:58:45
    brondsem

    do we know why that's failinlg?

  • 15:00:00
    tvansteenburgh

    b/c it can't import allura for some reason?

  • 15:53:56
    brondsem

    ah I figured out the forgehg problem

  • 15:54:03
    brondsem
  • 15:54:09
    brondsem

    it tried to pull down Allura from pypi

  • 15:54:24
    brondsem

    because the Allura build (upstream job) had failed

  • 15:54:27
    brondsem

    so it wasnt' available

  • 15:55:09
    tvansteenburgh

    yeah, and allura is failing b/c it can't install testfixtures

  • 15:55:18
    tvansteenburgh

    which doesn't make sense - it was working last night

  • 15:55:25
    brondsem

    Allura doesn't trigger the forgehg (downstream) if it fails, but there were new forgehg commits which made it run anyway

  • 15:55:38
    brondsem

    i kicked off a new Allura run, because I agree it seems like it should work

  • 15:56:28
    tvansteenburgh

    wonder if we could add a rule to not build forgehg if allura is red

  • 15:57:08
    tvansteenburgh

    although i guess that would usually be a little extreme

  • 15:57:33
    tvansteenburgh

    since it will still usually be importable, even if it's failing

  • 15:57:44
    brondsem

    yeah

  • 16:12:13
    allura-ci

    Project allura build #2,056: UNSTABLE in 24 min: http://engr.geek.net/hudson/job/allura/2056/

  • 16:32:26
    brondsem

    that looks like just a regular legit test failure

  • 16:32:40
    brondsem

    cory_fu: perhaps related to empty repo changes

  • 16:36:27
    tvansteenburgh

    hrm, i fixed that on my sandbox during testing

  • 16:36:30
    tvansteenburgh

    i'll take a look

  • 16:49:25
    tvansteenburgh

    i'm going to delete that test

  • 16:49:32
    tvansteenburgh

    it's useless

  • 16:49:59
    tvansteenburgh

    it's hitting a url for a tool that doesn't exist, and not even checking the response

  • 16:50:32
    tvansteenburgh

    it's failing now because we hit the disk if the metadata is missing, and there's no svn repo there

  • 17:24:34
    allura-ci

    Yippie, build fixed!

  • 17:24:35
    allura-ci

    Project allura build #2,057: FIXED in 20 min: http://engr.geek.net/hudson/job/allura/2057/

  • 17:25:43
    allura-ci

    Project forgehg build #100: STILL UNSTABLE in 1 min 4 sec: http://engr.geek.net/hudson/job/forgehg/100/

  • 17:28:59
    brondsem

    not sure what that test failure is about, lots of 404s in the functional tests

  • 17:37:10
    tvansteenburgh

    wtf, i ran all these tests repeatedly on my sandbox

  • 17:39:47
    tvansteenburgh

    and they still all pass for me on master

  • 17:51:15
    tvansteenburgh

    oh i know why

  • 17:51:35
    tvansteenburgh

    forgehg master is ahead of allura master, on which it depends

  • 17:51:55
    tvansteenburgh

    but i can't push allura master yet, b/c i'm waiting for the new forgehg lib to be installed in pythontree

  • 17:52:37
    brondsem

    k

  • 18:53:03
    ctsai-sf

    Getting a couple recent reports of git browser not showing up-to-date info. I thought that was fixed. :(

  • 18:55:56
    brondsem

    :(

  • 18:56:04
    brondsem
  • 18:56:30
    ctsai-sf

    Yeah, so, new ticket then?

  • 18:56:43
    ctsai-sf

    Or roll into that one?

  • 18:56:46
    brondsem

    seems about the same as 6101 to me

  • 18:56:55
    brondsem

    yeah

  • 18:57:03
    ctsai-sf

    It is git vs. hg.

  • 18:57:27
    brondsem

    cory_fu: you think that'd make it a different bug?

  • 19:00:47
    cory_fu

    It showing a commit as modifying a directory that it didn't modify is quite possibly a separate bug from it showing a correct but out-dated set of commits

  • 19:02:11
    ctsai-sf

    I'll make a new ticket and say "may be related to:" ;)

  • 19:05:44
    cory_fu

    Yeah, I think that's best

  • 19:05:53
    cory_fu

    I'm really sad that these types of issues are still cropping up

  • 19:09:25
    ctsai-sf

    User notes that it seems only the root that's affected.

  • 19:09:38
    ctsai-sf

    From openmsx

  • 19:13:04
    Quibus

    ctsai-sf: here, you mean? :P

  • 19:13:34
    ctsai-sf

    Yes, this is indeed what I meant when I said that we were talking about your problem in #allura

  • 19:13:51
    ctsai-sf

    Quibus is part of the openmsx project.

  • 19:13:53
    Quibus

    If you click the doc dir, you can see only recent stuff

  • 19:14:24
    Quibus

    while the message, user and date of the doc dir on root level is about 12 years old

  • 19:14:32
    Quibus

    (just as an example)

  • 19:20:40
    brondsem

    [#4826] is another open ticket we have on it

  • 19:21:30
    brondsem

    maybe the new 6152 should be closed in favor of that one

  • 19:24:07
    ctsai-sf

    Hrm, I thought that would have been closed when [#4691] was.

  • 19:24:08
    sfbot
  • 19:25:53
    brondsem

    those are older commits, we probably need to run the last commit updating script on it

  • 19:26:00
    brondsem

    we haven't run that much at all yet

  • 19:26:38
    brondsem

    so keeping them separate tickets is probably ok

  • 19:26:45
    cory_fu

    But these new tickets would presumably be using the newer LCD records so maybe there's still an issue with the new version

  • 19:26:50
    brondsem

    right

  • 19:32:46
    Quibus

    We had just had this repo pushed last night

  • 19:32:50
    Quibus

    Is that related?

  • 19:33:55
    ctsai-sf

    Yes, it shows that this issue is not entirely the same as similar issues we've seen in the past. Hence the decision to keep separate tickets for this rather than closing one in favor of the other.

  • 19:34:41
    Quibus

    OK

  • 19:35:01
    Quibus

    You could probably test by reproducing it by uploading it again on your test env.

  • 20:47:37
    Quibus

    good night

  • 21:37:17
    allura-ci

    Yippie, build fixed!

  • 21:37:17
    allura-ci

    Project forgehg build #101: FIXED in 1 min 9 sec: http://engr.geek.net/hudson/job/forgehg/101/