mixing of i686 and i386 archs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
It seems that a common practice in rpms is to mix i386 things into i686 rpms. This messes up with our tests, as the tests expect i686 folder but for example in java-1.8.0-openjdk-devel-1.8.0.292.b10-3.fc33.i686.rpm there is /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.292.b10-3.fc33.i386/bin/ bin folder..
this results in rather large amount of tests failing as those are unable to locate relevant binaries in expected folders.. question is whether its something that should be fixed in the rpms or should be expected in the test.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failures against java-1.8.0-openjdk-devel-1.8.0.292.b10-3.fc33.i686.rpm and inspect the tests that expect i686 paths. Compare the package's i386 and i686 locations, then determine whether the RPM or test expectations are responsible. Done means the relevant tests reliably locate the binaries and pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, python
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100