Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Continuous integration setup #239

Closed
azonenberg opened this issue Oct 20, 2020 · 4 comments
Closed

Continuous integration setup #239

azonenberg opened this issue Oct 20, 2020 · 4 comments
Assignees
@kench
Labels
build Build system and infrastructure

Comments

@azonenberg
Copy link
Collaborator

We should have nightly Windows and Linux builds logging to a CI server.
@azonenberg azonenberg added the build Build system and infrastructure label Oct 20, 2020
@azonenberg
Copy link
Collaborator Author

@bvernoux @nshcat can one of you investigate these Windows build failures?

https://github.com/kench/scopehal-apps/actions/runs/319193878

@azonenberg
Copy link
Collaborator Author

@kench looks like your OOM issue is the result of building with "make -j" and no cap on the number of jobs. If you have 192GB of RAM on your workstation like I do this is fine, but GitHub's build system clearly has less :)

@kench
Copy link
Collaborator

kench commented Oct 22, 2020

@azonenberg Can fix. While we're on the topic of make -j, can you update the glscopeclient manual?

It's going to be frustrating for new users when their Windows builds fail because the instructions assume that they have 192GB of RAM installed.

@azonenberg
Copy link
Collaborator Author

Updated in ngscopeclient/scopehal-docs@549cf1e

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

@kench kench

Labels
build Build system and infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kench @azonenberg and others