#3 Run tests considering the arches supporting wired tiger storage engine.
Opened 6 years ago by jaruga. Modified 3 years ago
rpms/ jaruga/rubygem-mongo hotfix/consider-wiredtiger-storage-engine  into  master

No commits found

Right now on the rawhide, the build was failed.
https://apps.fedoraproject.org/koschei/package/rubygem-mongo
https://koji.fedoraproject.org/koji/taskinfo?taskID=26893408

The reason is that the wired tiger storage engine of the mongodb is supported for only specified architectures, seeing mongodb.spec [1]
The above build was run on armv7hl arch that does not support tiger storage engine.
You can see error messages "Majority read concern requested, but it is not supported by the storage engine. (148)" in the build.log.

I did below tests.

Before the modification

$ koji build rawhide --scratch --arch-override=x86_64 *.src.rpm

https://koji.fedoraproject.org/koji/taskinfo?taskID=26981353
ok

$ koji build rawhide --scratch --arch-override=armv7hl *.src.rpm

https://koji.fedoraproject.org/koji/taskinfo?taskID=26981445
failed.

After this modification.

$ koji build rawhide --scratch --arch-override=x86_64 *.src.rpm

https://koji.fedoraproject.org/koji/taskinfo?taskID=26981909
ok

$ koji build rawhide --scratch --arch-override=armv7hl *.src.rpm

https://koji.fedoraproject.org/koji/taskinfo?taskID=26981924
ok

[1] https://src.fedoraproject.org/rpms/mongodb/blob/master/f/mongodb.spec#_16-18

Ping. someone, could you review this?
Thanks.

When I looked into this, I tried to use ExclusiveArch: x86_64 [1, 2] to force build on x86_64. I think that would be much better/simpler solution. Unfortunately, this does not appear to work. Would you mind to investigate this, possibly opening ticket with release engineering to fix this?

OK. let me check it later.

ExclusiveArch: x86_64 [1, 2] to force build on x86_64

Right? The tag name would confuse me.
ExclusiveArch: x86_64 is to build on the architectures except x86_64, isn't it?

ExclusiveArch: x86_64 is to build on the architectures except x86_64, isn't it?

It means that x86_64 builders will be used exclusively, i.e. no other arch will be used to build the package.

The ExclusiveArch should work and it is investigated why it does not work:

https://pagure.io/releng/issue/7671

What I think you want is ExcludeArch. Not sure this is relevant anymore.

What I think you want is ExcludeArch. Not sure this is relevant anymore.

This can be used as well. Nevertheless, I suggested ExclusiveArch because the build would then run always on the same architecture, providing more consistency. The downside is, that due to builds done always on single architecture, we could miss some arch specific issues on other platforms. But the noarch builds are distributed among platforms randomly, therefore the chances we catch anything are low anyway. Therefore I would prefer consistency.