Jenkins build failure: mono bindings monomaniacally breaking

Bug #931764 reported by Allan LeSage on 2012-02-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Charles Kerr

Bug Description

Apparently this issue is known to ted; this bug will serve as reminder, inspiration to get this Jenkins build going; apparently missing some files relating to mono bindings. Marking to high as we'd like to get this build up; if you suspect Jenkins' misconfiguration pls. ping alesage or follow-up on this ticket.

Related branches

Allan LeSage (allanlesage) wrote :
Ted Gould (ted) wrote :

Something funny has to be happening with the basename. Not sure what. I've attached a branch that should print it out in the build log. Can you run with that branch so we can get more data please?

Changed in libappindicator:
status: New → Incomplete
Ted Gould (ted) wrote :

Wrong bug, sorry.

Changed in libappindicator:
status: Incomplete → New
Ted Gould (ted) on 2012-02-17
Changed in libappindicator:
importance: High → Critical
Charles Kerr (charlesk) on 2012-02-17
Changed in libappindicator:
status: New → Triaged
Olli Ries (ories) on 2012-03-01
Changed in libappindicator:
assignee: nobody → charles (charlesk)
Allan LeSage (allanlesage) wrote :

Ted advanced a theory that we're using a -j2 compiler flag, which might cause mono bindings to fail. For the record Jenkins simply does a pdebuild--don't know if it's possible to affect his compiler options.

Charles Kerr (charlesk) on 2012-03-06
Changed in libappindicator:
status: Triaged → In Progress
Ted Gould (ted) on 2012-03-07
Changed in libappindicator:
status: In Progress → Fix Committed
milestone: none → 0.4.91
Ted Gould (ted) on 2012-03-09
Changed in libappindicator:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers