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

Linux build occassionally fails in CI #4350

Open
z64555 opened this issue Jun 4, 2022 · 3 comments
Open

Linux build occassionally fails in CI #4350

z64555 opened this issue Jun 4, 2022 · 3 comments
Assignees
@z64555
Labels
bug An issue from unintended consequences build An issue related to the build systems ci A feature or issue related to the continous integration tools

Comments

@z64555
Copy link
Member

z64555 commented Jun 4, 2022 •
edited
Loading

We've been seeing this more recently. Essentially, one or multiple builds on the Linux target fails.

My investigation led me to a failure by cp, a copy command for bash, stating that it could not copy a .so file because it already exists in the destination, which appears to be nonsense.

The line that this call to cp happens in is rather long, making commandline length limit highly probable. The linux length limit of 4096 characters coincidentally has it run this as its last command on the line: cp -a /__w/fs2open.github.com/fs2open.github.com/build/lib

Further investigation revealed that cp is being called by ninja, and the build.ninja file its running on is from cmake, but that's about as far as I got. I suspect there's a configuration not quite right in cmake that's leading to the symptom.
@z64555 z64555 added bug An issue from unintended consequences build An issue related to the build systems ci A feature or issue related to the continous integration tools labels Jun 4, 2022
@z64555 z64555 added this to the Release 22.2 milestone Jun 4, 2022
@z64555
Copy link
Member Author

z64555 commented Jun 4, 2022

IIRC I had stumbled across this issue very recently when messing around with the pi-pico. The solution with it was to update cmake, so this is a possible solution for this situation as well.

@z64555 z64555 self-assigned this Jun 5, 2022
@z64555 z64555 mentioned this issue Jun 15, 2022
Merged
@z64555
Copy link
Member Author

z64555 commented Jul 20, 2022

The CMake versions in the linux runners should be the latest release, so that makes it unlikely that upgrading the cmake version will resolve this.

@z64555
Copy link
Member Author

z64555 commented Jul 22, 2022

It's possible that there's a configuration with cmake that can limit the commandline options that it generates, but since I'm not familiar with cmake nor how to navigate its documentation I cannot make a reasonable time limit.

Since this issue is mostly an nuisance rather than a progress stopper, I'm demoting the priority and removing it from the 22.2 milestone.

@z64555 z64555 removed this from the Release 22.2 milestone Jul 22, 2022
@JohnAFernandez JohnAFernandez moved this from To Sort to Low Impact in Issue Management Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@z64555 z64555

Labels
bug An issue from unintended consequences build An issue related to the build systems ci A feature or issue related to the continous integration tools
Projects
Issue Management
Status: Low Impact
Milestone
No milestone
Development

No branches or pull requests
1 participant
@z64555