Concerning CI testing
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Probably I'm missing out on something, but I could not find any information concerning testing the packages for the ARM mvebu-cortexa9 target.
I took a look on the CI result, where I noted the absence of testing for that particular architecture after @neheb commited a change, that was about to solve an issue I cared about.
I would just like to ask, how the packages for that platform (probably the mvebu-cortexa9 target is just one representative for lots of different ARM architectures?) get tested. In case there is no automated testing, that might be nice to have.
Doing so, issues with broken installation of packages could be detected automatically in advance.
Some information about how you are handling things right now would be nice, since I have no insights and I just took a brief look on the CI and could not find docs on why there is testing for some archs and not for others.
Contributor guide
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
Review the existing CI configuration and package-testing workflow for the mvebu-cortexa9 target; the issue names no specific file or test entry point. Done means documenting the current architecture-testing policy or establishing automated package installation coverage where it is absent.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100