On 12/04/2019 07:45, Jack Rosenthal wrote:
> On Thu, 11 Apr 2019 at 15:32 +0200, 'Paulo Matos' via Racket
> Developers wrote:
>> No, currently I have a central cache for the gitlab machines
>> locally. However, I have in place an S3 bucket (Google would also
>> be possible but would need to
On Thu, 11 Apr 2019 at 15:32 +0200, 'Paulo Matos' via Racket Developers wrote:
> No, currently I have a central cache for the gitlab machines locally.
> However, I have in place an S3 bucket (Google would also be possible
> but would need to check) I will sponsor to hold the cache between the
>
On 11/04/2019 15:32, 'Paulo Matos' via Racket Developers wrote:
>
> Thanks. I don't know much about kubernetes (still at the docker level...
> :)) but I saw the name thrown around in the gitlab docs so it should be
> fine integrating such a cluster with CI.
>
Now I know where I keep seeing
On 11/04/2019 11:56, Jack Firth wrote:
> So about 30-40 total cores for that second category?
That would be awesome! :)
> About how much
> total RAM is needed?
Someone might correct me here but from what I can see it would be great
to have something like 2G/core - but if not it shouldn't be
So about 30-40 total cores for that second category? About how much total
RAM is needed? I'm assuming Gitlab owns all persisted data so there's not
much need for these machines to have non-transient disk storage. How much
importance does resource density play, in terms of ideal
On Wednesday, April 10, 2019 at 12:15:02 AM UTC-7, Paulo Matos wrote:
>
> Currently I don't have enough machines or AWS time to dedicate to Racket
> builds
How much do you need?
--
You received this message because you are subscribed to the Google Groups
"Racket Developers" group.
To
I have finished pushing the changes I have mentioned below.
Hopefully things will improve. Again, I am sorry for leaving Racket in
such a red state for the past couple of weeks. :)
On 10/04/2019 09:14, 'Paulo Matos' via Racket Developers wrote:
>
>
> On 09/04/2019 19:44, Alexis King wrote:
>>
On 09/04/2019 19:44, Alexis King wrote:
> Hi Paulo,
>
Hi Alexis,
> The work you’re doing is really cool, though I admit most of it is over my
> head. Thank you for putting in the time to set it all up. One thing I have
> noticed, however, is that the GitLab pipeline seems to almost always
Hi Paulo,
The work you’re doing is really cool, though I admit most of it is over my
head. Thank you for putting in the time to set it all up. One thing I have
noticed, however, is that the GitLab pipeline seems to almost always fail or
timeout, which causes almost every commit on the commits
Hello,
Short Summary: I have added in 35d269c29 [1] cross architectural testing
using virtualized qemu machines. There are problems - we need to fix those.
Long Story:
For months now, I have been wishing I could get cross-arch testing done
on a regular basis on Racket. Initially I had something
10 matches
Mail list logo
