keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

ci: request 2G of RAM for compilation

Browse Source 
I think the `fork` errors CI is hitting might be due to more stringent
memory limit enforcements in OCP4. Let's be more explicit and actually
request 2G of RAM. We can adjust from there.

(One related thing is CPU requests; it's possible we might need to also
make that explicit and in turn adjust the `_smp_mflags` RPM macro, since
the default is unlikely to be k8s/cgroups-aware.)
This commit is contained in:
Jonathan Lebon 2020-07-12 19:35:42 -04:00 committed by OpenShift Merge Robot
parent 2235fb6c5b
commit 89d79f3505
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.cci.jenkinsfile
View File

@ -2,7 +2,7 @@
stage("Build") {
parallel rpms: {
cosaPod(buildroot: true, runAsUser: 0) {
cosaPod(buildroot: true, runAsUser: 0, memory: "2Gi") {
checkout scm
shwrap("""
# fetch tags so `git describe` gives a nice NEVRA when building the RPM
@ -40,7 +40,7 @@ codestyle: {
}
},
rust: {
cosaPod(buildroot: true, runAsUser: 0) {
cosaPod(buildroot: true, runAsUser: 0, memory: "2Gi") {
checkout scm
shwrap("ci/msrv.sh")
}