Troubleshoot failing `loopback-connector-postgresql` CI pipelines
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 2
Description
With https://github.com/loopbackio/loopback-connector-postgresql/pull/492, it was discovered that the CI pipeline had started failing. The [last run](https://github.com/loopbackio/loopback-connector-postgresql/actions/runs/1270094767) was successful, though [this repo doesn't have weekly CI runs](https://github.com/loopbackio/loopback-connector-postgresql/blob/ecf91b5ac16e65f4355d192ce414ab9fa4857a32/.github/workflows/continuous-integration.yaml#L3-L7), so the time between the PR run and the previous run was a while back (about 2 months apart).
This issue is to track resolving the failing CI pipeline.
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 with pull request #492, the recorded Actions run, and .github/workflows/continuous-integration.yaml, especially the schedule noted around lines 3-7. Compare the failing pipeline information from that pull request with the last successful run and determine what remains reproducibly broken. Done means the affected CI pipeline runs successfully with the relevant PostgreSQL connector checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, postgresql, shell
- Domain
- ci-cd, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100