Skip to content

Conversation

@danieleades
Copy link
Contributor

the installer currently fails on windows. This PR adds a job which tests the installer against different targets.
This doesn't fix the breakage, but should catch it next time.

Copy link
Collaborator

@alixander alixander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry about the delay in getting to this. I think it's a good addition. Probably in daily though. If you'd like to make the changes, including signing your commit, please update this PR. Otherwise I can make them in another.

@danieleades danieleades requested a review from alixander August 6, 2025 10:51
@danieleades danieleades force-pushed the installer-test branch 2 times, most recently from 07dc38f to 50937be Compare August 6, 2025 10:54
@danieleades
Copy link
Contributor Author

danieleades commented Aug 6, 2025

Sorry about the delay in getting to this. I think it's a good addition. Probably in daily though. If you'd like to make the changes, including signing your commit, please update this PR. Otherwise I can make them in another.

that should be done now.

now there's just the remaining issue of the fact the install script fails on mac-os and windows.

i guess the instructions are somewhat linux flavoured

name: Installer Test

on:
push:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's still on push rather than as a daily job

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the rationale for not wanting this on push?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

slows down ci for rare changes. i suppose if you want to add a gate that says only run this if the install script changed, it can be on push, but even then it'd have to be grouped under "ci" workflow to avoid the extra noise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants