
@samth given one of your last commits, shouldn’t have CS snapshots here already: https://snapshot.racket-lang.org/ci-snapshots/ ?

Also just noticed we started (maybe we have done so for awhile) distributing snapshots for OpenIndiana, although we don’t really test it, do we? we should think about running CI on OpenIndiana and OpenBSD given we officially provide snapshots for it.

… and who’s using OpenIndiana?

Unless I misunderstood, I think create-installer3m
should be renamed to create-installers
.

It looks like https://snapshot.racket-lang.org/ci-snapshots/current/log/Racket%20CS%20(Ubuntu%2018.04,%20x86_64) gets cut off.

Oh - so the snapshot is there but for some reason the page doesn’t show it?

I think the build failed.

But somehow is not reported as a failure

Really? Wow - why do you think it failed?

I fixed the job name. Opened a PR to move the snapshot creation to its own workflow.

Just my wild guess: failed in a sense that it didn’t finish the job. Perhap parallel
in https://github.com/racket/racket/blob/master/.github/workflows/site-small.rkt#L23 is buggy and terminates whenever the first job finishes first? Idk,

ah - i know what you mean. Well, I can try that locally.


if all you want is to checkout the branch that triggered the workflow you don’t need to do anything besides using actions/checkout@v2


Only a single commit is fetched by default, for the ref/SHA that triggered the workflow.

no, it checks out the commit, not the branch

is what I did not going to work, then?

I think we are using v1
, maybe update to v2
?

nope… because you cannot checkout a reference name.

I think v2
does what you want: Creates a local branch • No longer detached HEAD when checking out a branch

oh, I see in the docs — great!

try removing the step and just using checkout@v2

it should work… i think

at least according to the docs.

Ok, done

Finally installed act
— should have done this a long time ago

is there an emoji for mind blown?

:exploding_head:

that’s right…

I didn’t know about act
.

lol


I have been sometimes commiting stuff to branch just to trigger actions. :slightly_smiling_face:

need to give it a go.

I like it already - take a look at this beauty of a diagram!

yeah i was impressed

OK, so what actually happens with Racket CS builds?

The last line is always raco setup: moving: <pkgs>/data-doc/data/doc/data