All integration tests on all architectures
- Dominant language
- C++
- Stars
- 8.6k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
Many integration tests are running only on some architectures - they would not pass on others. We should:
1. Identify disabled combinations.
2. Enable those that are passing out-of-the-box, without any RetDec modifications.
3. Gradually identify problems in those that do not pass, fix them, and enable tests.
We should try to do this even for binaries, that do not have debugging information, higher optimization levels, etc.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by identifying the disabled architecture combinations in the integration-test configuration and run the existing integration tests across those combinations. Done means combinations that pass without RetDec changes are enabled, while failing combinations have their problems identified, fixed, and enabled, including tests for binaries without debugging information and with higher optimization levels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100