> On Nov 2, 2016, at 06:52, Lawrence Velázquez <lar...@macports.org> wrote: > > Can you open a ticket for this and assign it to me? You can just > copypaste your original email as the description or something.
Thanks: https://trac.macports.org/ticket/52810#ticket > > vq > >> On Nov 2, 2016, at 3:56 AM, Jeremy Huddleston Sequoia >> <jerem...@macports.org> wrote: >> >> >>> On Nov 2, 2016, at 00:20, Mojca Miklavec <mo...@macports.org> wrote: >>> >>> On 2 November 2016 at 06:17, Jeremy Huddleston Sequoia wrote: >>>> I've been having a bit of difficulty dealing with the new buildbot emails. >>>> I would really like links to the individual failing jobs. Instead, we're >>>> given links to each job and a list of failed ports, but there is no >>>> indication as to which port corresponds to which job. One must look >>>> thorough each link to find the relevant one. >>>> >>>> Could we get those links added to the 'Broken ports' section? >>> >>> Sure. We gladly accept patches :) :) :) >>> >>> OK, joke aside. I wrote the part of the code that generates the >>> emails, but I did not manage to figure out how to map the build >>> number/url to a port. Buildbot nine is apparently more clever about >>> that and there it should apparently be more straightforward to do it, >>> but many are reluctant to switch just yet. >>> >>> There are several ways to fix this: >>> >>> - hack into Python code (most elegant, but I did not have any success >>> with that yet) >>> >>> - I once tried to fetch the contents of json files for individual >>> builds and parse it, but that crashed/froze the buildbot (it might be >>> that I wrote buggy code, but that approach is super ugly anyway) >>> >>> - probably the easiest workaround would be to print the URL or the >>> build number to >>> https://build.macports.org/builders/ports-10.8_x86_64_legacy-watcher/builds/2764/steps/summary/logs/stdio >>> which would make it easier to map the URLs to ports. >>> >>> Somewhat related tickets: >>> https://trac.macports.org/ticket/52766 >>> https://trac.macports.org/ticket/51995 >> >> FYI, My current hack method is to open the 'Full logs:' link, check out the >> summary, and then figure out from that list which of the job's to check (if >> the third job failed, pick the link with the third number in the series). >> >> --Jeremy >> >> _______________________________________________ >> macports-dev mailing list >> email@example.com >> https://lists.macosforge.org/mailman/listinfo/macports-dev >
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list firstname.lastname@example.org https://lists.macosforge.org/mailman/listinfo/macports-dev