> We should put the buildername/buildnumber/URL of the failing build into
> the failcache to be reported back on a match. The current output would
> not be helpful to find the reason why it failed. I added this
> information to the build environment [1].
Just curious. Given that you already implem
On 2016-9-14 18:07 , Mojca Miklavec wrote:
On 14 September 2016 at 06:25, Ryan Schmidt wrote:
Now that we have the failcache (thanks!) what would be involved in getting a
successcache?
- Before listing or installing any dependencies, ask MacPorts for the
name (full path) of the resulting bina
On 14 September 2016 at 06:25, Ryan Schmidt wrote:
> Now that we have the failcache (thanks!) what would be involved in getting a
> successcache?
- Before listing or installing any dependencies, ask MacPorts for the
name (full path) of the resulting binary tarball like
/opt/local/var/macports/so
Now that we have the failcache (thanks!) what would be involved in getting a
successcache? If I want to do a build of "all" ports, I don't want to spend
time just activating and deactivating files of ports that already successfully
built.
___
macports
On 2016-09-12 14:41, Clemens Lang wrote:
> here's a patch against mp-buildbot that would add a fail cache for use
> on the buildbots. Unfortunately I don't have a test setup yet, so I'm
> hesitating to commit this immediately. I'd welcome feedback, a code
> review, or testing by somebody with a wor
Hi,
here's a patch against mp-buildbot that would add a fail cache for use
on the buildbots. Unfortunately I don't have a test setup yet, so I'm
hesitating to commit this immediately. I'd welcome feedback, a code
review, or testing by somebody with a working builbot setup.
Basically, I'm keeping
