[VL] ANSI workflow checks out main instead of the PR
Maintainers usually reply within 2 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
The suspected cause is the empty ref in the checkout step of the unit testing jobs in .github/workflows/velox_backend_ansi.yml, near line 229. Compare that step with the checkout configuration in other Velox workflows in .github/workflows/ to see how the PR head ref is normally passed. Done means the ANSI job checks out the PR head when triggered by a PR comment, which you can confirm by re-running the job on a test PR and checking the logged commit SHA.
Written by the indexing model from the issue text.
Description
The ANSI CI job doesn't look to be able to run on the PR code correctly.
E.g., This ANSI test job, triggered by a comment on PR #13035, checked out origin/main at cc011f37 instead of the PR head.
Perhaps caused by the accident empty content of the ref to checkout of the unit testing jobs.
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 665
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 109
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a 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 apache/gluten
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
[VL] madvise(WILLNEED) call fails in MmapFileStream because of wrong calculation of fetching lengthPossibly taken @jiangjiangtian claimed this 32 days ago. Openbug triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/gluten#12711 · 2 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
apache/gluten#12316 · 5 comments ·
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
scylladb/scylla-migrator#417 ·
-
arch build failsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
digital-asset/participant-query-store#177 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
containerbase/base#7891 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 91/100
com-vitthalmirji/toon4s#117 ·
Maintainers usually reply within 1 day