flaky integration tests
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
Research direction
The failure is in the integration test job of a CI run linked from the issue, at step 28. The reporter suspects the llm2 service was not ready when the tests started, but has not confirmed this. Start by reading that log, then check how the integration tests wait for llm2 before running. Done means the tests pass reliably, which likely requires a readiness wait or a fix in the setup, confirmed by repeated CI runs.
Written by the indexing model from the issue text.
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
spotted in https://github.com/nextcloud/context_agent/actions/runs/38265295274/job/114865819511?pr=257#step:28:24
seems like llm2 was not ready in time, didn't investigate much.
- Dominant language
- Python
- Stars
- 26
- Forks
- 20
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the 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 nextcloud/context_agent
-
enhancement priority normal
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
nextcloud/context_agent#270 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
nextcloud/context_agent#242 · 1 comment ·
Maintainers usually reply within 1 day
-
Add endpoint to create new CollectivesPossibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nextcloud/context_agent#240 · 1 comment ·
Maintainers usually reply within 1 day
-
find_person_in_contacts fails with Niquests content argument and cannot serialize vCard AddressOpenbug
Difficulty 2/5 Half a day Newbie friendliness 76/100
nextcloud/context_agent#217 · 3 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 22/100
nextcloud/context_agent#271 ·
Maintainers usually reply within 1 day
All issues in nextcloud/context_agent
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/policyengine-us#10262 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
kellyjonbrazil/jc#788 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
`/search.json` ignores the documented `editions.sort` parameterPossibly taken @PranavD2905 claimed this today. OpenAffects: Server Good First Issue Module: Solr Needs: Triage Theme: Public APIs Theme: Search
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
internetarchive/openlibrary#13989 · 1 comment ·
Maintainers usually reply within 1 day
-
bug P2: misleading query
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
jeffknupp/association#478 ·