Skip to content

Conversation

@dcoles
Copy link
Contributor

@dcoles dcoles commented Feb 25, 2024

This also preserves the gemma binary as a build artefact should folks want to grab a pre-built binary.

Dropped the use of the lukka/cmake actions due to conflicts with --preset. This isn't that bad as we were mostly overriding the default behaviour anyway.

It also shaves ~2 min off the build since the GitHub builders already have CMake pre-installed.

Important

Currently the resulting Windows binary is being detected as Trojan:Win32/Phonzy.B!ml by Windows Defender ...and only Windows Defender. This is almost certainly a false positive given that the binary is built on GitHub's official "windows_latest" image with the provided CMake and Clang compilers. I've submitted the file to Microsoft Security Intelligence (Submission ID: f2092a44-4b58-45bb-b6ed-071d43a9bc2a) to ask that they investigate.

Also opened actions/runner-images#9403 to report the issue.

@dcoles dcoles force-pushed the windows-build branch 2 times, most recently from 7bc5117 to c64b6fd Compare February 25, 2024 01:42
@dcoles
Copy link
Contributor Author

dcoles commented Feb 25, 2024

Latest build (8034688123) is no longer being detected as a threat. 🤞 spoke too soon. 🤦

@jan-wassenberg
Copy link
Member

Looks good to me, thanks. Would you mind rebasing?

@dcoles
Copy link
Contributor Author

dcoles commented Feb 25, 2024

Looks good to me, thanks. Would you mind rebasing?

Unfortunately I can't. Copybarra wiped away the Windows build again: 6965973

@jan-wassenberg
Copy link
Member

Bummer :/ We're working on it, seems caused by a copybara bug which we are told will be fixed soon.

@dan-zheng
Copy link
Collaborator

Unfortunately I can't. Copybarra wiped away the Windows build again: 6965973

Sorry about that! Changes should have been restored in 4c155bd, and we've aligned on our workflows so reversions shouldn't happen again.

Let me try to run CI for this pull request now.

@dan-zheng dan-zheng added the copybara-import Trigger Copybara for merging pull requests label Feb 26, 2024
copybara-service bot pushed a commit that referenced this pull request Feb 26, 2024
--
c64b6fd by David Coles <dcoles@dcoles.net>:

Include Windows in GitHub Actions build

This also preserves the `gemma` binary as a build artefact
should folks want to grab a pre-built binary.

Dropped the use of the lukka/cmake actions due to conflicts with `--preset`.
This isn't that bad as we were mostly overriding the default behaviour anyway.

It also shaves ~2 min off the build since the GitHub builders already
have CMake pre-installed.

COPYBARA_INTEGRATE_REVIEW=#38 from dcoles:windows-build c64b6fd
PiperOrigin-RevId: 610449220
@dcoles dcoles closed this Feb 26, 2024
@dan-zheng
Copy link
Collaborator

Our Copybara automation has effectively merged this pull request and imported it as a commit in dev branch: 7aeade5.

Unfortunately, the automation doesn't actually merge pull requests right now, so we have to manually close it – we're looking into fixing this asap. Thanks for your contribution!

@dcoles
Copy link
Contributor Author

dcoles commented Feb 26, 2024

Hi @dan-zheng,

Sorry about that! Changes should have been restored in 4c155bd, and we've aligned on our workflows so reversions shouldn't happen again.

No worries. I know how much a pain syncing internal/external repositories can be.

Unfortunately, the automation doesn't actually merge pull requests right now, so we have to manually close it – we're looking into fixing this asap. Thanks for your contribution!

I rebased my branch onto the current dev branch which seems to have been enough for GitHub to realize the changes have been merged and automatically close the branch. Thanks for checking. 😄

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

Labels

copybara-import Trigger Copybara for merging pull requests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants