libera/#clasp - IRC Chatlog
Search
2:35:55
mns
yitzi: if I use --jobs=2 with koga, will it automatically use that with ninja as well ? or do I have to explicitly tell ninja to use -j 2 ?
2:40:49
drmeister
yitzi: I didn't know about the `./koga --jobs=2`- that's to limit the number of processes that clasp forks?
2:42:59
drmeister
mns: I'm not clear on the effect of `./koga --jobs=2`. I know that `ninja -j 2 -C build` will limit the number of C++ compilation processes. I'm guessing `./koga --jobs=2` controls the lisp compiler and `ninja -j 2 -C build` controls the C++ compilation.
2:43:46
drmeister
::notify yitzi Have you looked into if `ninja -j 2` can somehow communicate the number of jobs to child processes?
2:48:46
drmeister
::notify yitzi What was that Common Lisp programming course thing you told me about? experienceio?
2:51:26
mns
my kid is going be studying for pharmacology starting september, hence the connection to molecular chemistry and clasp. though I came to the video via lisp. and then saw that it was for molecular chemistry, a nice way to bond with the kid.
2:52:58
drmeister
Down the road I'd like to. Not yet. We are just building clasp and running tests right now.
2:53:53
mns
alright it failed for bclasp. I'll update the github issue with the information that I can see. Are there log files that are generated somewhere ?
4:22:32
drmeister
::notify yitsi I got a cando build to work https://github.com/cando-developers/cando/actions. The macos builds failed - I need to figure out why.
9:38:39
Colleen
yitzi: drmeister said 6 hours, 54 minutes ago: Have you looked into if `ninja -j 2` can somehow communicate the number of jobs to child processes?
9:38:39
Colleen
yitzi: drmeister said 6 hours, 49 minutes ago: What was that Common Lisp programming course thing you told me about? experienceio?
9:38:39
Colleen
yitzi: drmeister said 6 hours, 46 minutes ago: Do I need to enable macos building outside of the yaml file?
9:39:47
yitzi
drmeister: ninja doesn't have a way to communicate the job count to clasp. That is the reason behind this. https://github.com/ninja-build/ninja/issues/2125
9:40:33
yitzi
drmeister: I'll look at your cando workflow and see I can figure out what is going on with macos.
10:42:02
yitzi
drmeister: Looks like I got the mac build into aclasp. There was a typo in the yaml file.
11:49:20
drmeister
I see - thank you. I didn't see what was wrong with the macos yaml line and assumed it was some outside configuration that I hadn't set.
11:50:39
yitzi
Look down at the bottom under "Annotation" https://github.com/cando-developers/cando/actions/runs/2335804433
11:51:57
yitzi
I am starting to come up with a more complete idea how all the workflows will connect together.
11:52:42
yitzi
For that packaging workflow I was thinking of making it run nightly if there are changes and build clasp, cando, etc
11:56:53
yitzi
That is as much detail as you will get. It was an indentation issue. One too many spaces on that line.
11:59:59
yitzi
I also added `skip-sync=cando` ... this is important because otherwise koga will overwrite the specific commit that GitHub is trying to checkout and test.
12:02:29
drmeister
This all makes sense to me. It helps to understand that yaml files are just double baked JSON format,
12:05:59
yitzi
cando has a testing workflow that is triggered by cando/main, clasp/main and cando PRs.
12:07:04
yitzi
clasp has a packaging workflow that runs on a schedule like nightly. It builds debian packages (or arch etc) for clasp and cando.
12:07:45
yitzi
If I can figure out logic to test for changes to clasp/cando there I can make it punt the nightly run if there are no changes.
12:10:04
yitzi
And then we have a release packaging workflow that builds and posts binary builds to the GitHub release tags.