ref_int - update test workflow according to DR8
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- build-system, ci-cd, testing
Research direction
Start by reading DR-008-int.html, especially Option 4, then locate the test_and_docs workflow and its current dependency-resolution, module-patching, test, coverage, and upstream-collection steps. The work is done when that workflow follows the Option 4 process and the resulting testing workflow matches the acceptance criterion.
Written by the indexing model from the issue text.
Description
What
According to https://eclipse-score.github.io/score/main/design_decisions/DR-008-int.html test_and_docs workflow needs to be updated to reflect described process in option 4.
Rough overview:
- resolve deps by bazel
- in each module (inside bazel directories or checkout?) patch deps to match resolved list
- execute UTs, coverage etc.
- collect in upstream as before
Acceptance Criteria (DoD)
Testing workflow matches Option 4
How
No response
- Dominant language
- Python
- Stars
- 6
- Forks
- 42
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 32
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from eclipse-score/reference_integration
-
Coverage calculation for C++ and RustMay be free again @dcalavrezo-qorix claimed this 73 days ago, and no pull request is open. Openbug
eclipse-score/reference_integration#259 · 6 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
v0.8
Difficulty 3/5 1-2 days Newbie friendliness 55/100
eclipse-score/reference_integration#245 ·
Maintainers usually reply within 1 day
-
v0.8
Difficulty 4/5 3-5 days Newbie friendliness 38/100
eclipse-score/reference_integration#244 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
eclipse-score/reference_integration#234 ·
Maintainers usually reply within 1 day
-
FIT baselibsOpenv0.8
Difficulty 3/5 1-2 days Newbie friendliness 42/100
eclipse-score/reference_integration#232 ·
Maintainers usually reply within 1 day
All issues in eclipse-score/reference_integration
Similar issues
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#13737 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
zhuima/awesome-cloudflare#237 ·
-
Zero-token evaluations are treated as missing cost in selectionPossibly taken @sylvesterkaczmarek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-research/rrsi#6 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
aws-samples/sample-aws-genai-db-modernizer#294 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#4174 ·
Maintainers usually reply within 1 day