Closed rauldpm closed 1 year ago
A ppc64le rpm
package has been successfully created in build https://ci.wazuh.info/view/Packages/job/Packages_builder/123457/. This build had a stop before creating the S3 machine and was paused for 5 minutes.
After trying it manually in a machine, an error appeared for some problem with the versions:
Building target platforms: ppc64le
Building for target ppc64le
error: File /build_wazuh/rpmbuild/SOURCES/wazuh-agent-4.5.0.tar.gz: No such file or directory
This was solved by calling the builder script using argument --packages-version
, and a package was created successfully:
There is probably some difference in how is it called from Jenkins which creates the problem, as the machine where the tests have been done is the same as the one used by Jenkins. As a matter of fact, on the same machine the manual test was done, Jenkins had managed to build successfully a package: https://ci.wazuh.info/view/Packages/job/Packages_builder/123462/console
After reviewing the console output in the failed and successful builds in Jenkins and the first error that appears in all failed ones is always:
11:43:24 c++: fatal error: Killed signal terminated program cc1plus
and in a similar problem it seems it may have to do with memory usage, which could explain why it does work sometimes. Two possible solutions:
ppc64le
is selected, no more than 4 cores can be used for the compilationThe second option mentioned in the last commentary has been seen by @alberpilot as not possible due to infrastructure problems, so this issue is going to be manually transferred to https://github.com/wazuh/wazuh-jenkins so that the first solution may be implemented.
Description
The build of the PowerPC package for RPM systems has failed due to an error with
g++
:In addition, the following errors are observed:
It is necessary to review and fix the generation of this package to be able to carry out tests on it.
Related: https://ci.wazuh.info/view/Packages/job/Packages_builder/123439/
Tasks
Validation