freenode/#abcl - IRC Chatlog
Search
12:40:21
easye
ACTION wonders idly how much the "carbon footprint" the Bear's current dual GitHub/travis CI builds are stepping in.
12:41:21
easye
alandipert: fix for <https://github.com/armedbear/abcl/pull/373> "abcl-aio not finding ABCL-CONTRIB" is working. Thanks for the bug report; sorry about the tardiness.
12:44:09
no-defun-allowed
The gnarliest "normal" program CI I could think of only used about 2.5kWh of power over a few years. And about 0.94 kg of CO2 is emitted per kWh generated from coal.
12:52:11
easye
I really don't want to encourage MSFT github monoculture for abcl, as one day we will have to leave. But Travis already stopped building for months 'cuz they didn't have the money...
12:52:46
no-defun-allowed
More off topic: I heard that crypto miners pushed CI providers to limit what they provide these days. How's that going? My tests only run for a few minutes, so they have to be going really badly to drop those.
12:55:36
no-defun-allowed
Right, you probably could shuttle around data between temporary nodes forever. Though I had meant if you had felt any new restrictions, in any sense of "feeling" them.
12:56:23
easye
Re: feeling restrictions: no, but I have been using private CI for the past six months from $WORK
12:58:25
no-defun-allowed
Okay, just wondering. It sounded like a serious pain if one has a large test suite and/or less than moderately fast compiler.
12:59:33
easye
When stegoing processes, one should best model the failures of an existing well, established tool, fuzz a bit to escape detection.
13:38:26
alandipert
easye thank you so much! i started working on it myself and arrived at that same section of abcl-contrib.lisp. next time i'll try to report *and* fix :-)
14:31:13
easye
alandipert: no problem. There isn't enough documentation/stabilty in abcl-contrib.lisp to fix easily. But patches are always welcome...
14:32:37
easye
Nor are there tests. I had to diagnose the problem by starting the `java -jar abcl-aio.jar` in a directory not related to abcl builds. Otherwise, it was introspecting the abcl-contrib.jar as a sibling, and therefore "working for me".