You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "amoeba (via GitHub)" <gi...@apache.org> on 2026/07/03 19:25:17 UTC
[I] [Release] 07-flightsqlodbc-upload.sh PHASE_BUILD_MSI doesn't correctly watch workflow run [arrow]
amoeba opened a new issue, #50363:
URL: https://github.com/apache/arrow/issues/50363
### Describe the bug, including details regarding any error messages, version, and platform.
It looks like the watching logic in the `PHASE_BUILD_MSI` doesn't quite work like we thought.
I ran the previous step successfully,
```
$ PHASE_DEFAULT=0 PHASE_SIGN_DLL=1 dev/release/07-flightsqlodbc-upload.sh 25.0.0 1
[1/8] Downloading arrow_flight_sql_odbc_unsigned.dll from release...
[2/8] Signing arrow_flight_sql_odbc_unsigned.dll...
NOTE: Running jsign. You may be prompted for your OTP PIN...
Adding Authenticode signature to /Users/bryce/src/apache/arrow/dev/release/tmp/arrow_flight_sql_odbc_unsigned.dll
[3/8] Uploading signed DLL to GitHub Release...
Successfully uploaded 1 asset to apache-arrow-25.0.0-rc1
```
Then ran the `PHASE_BUILD_MSI` step but it didn't wait for the workflow and instead reporting "...has complete already...":
```
$ PHASE_DEFAULT=0 PHASE_BUILD_MSI=1 dev/release/07-flightsqlodbc-upload.sh 25.0.0 1
[4/8] Triggering odbc_release_step in package_odbc.yml workflow...
✓ Created workflow_dispatch event for package_odbc.yml at apache-arrow-25.0.0-rc1
https://github.com/apache/arrow/actions/runs/28679576610
To see the created workflow run, try: gh run view 28679576610
To see runs for this workflow, try: gh run list --workflow="package_odbc.yml"
[5/8] Waiting for workflow to complete. This can take a very long time...
Looking for GitHub Actions workflow on apache/arrow:apache-arrow-25.0.0-rc1
Waiting for run to start...
Found GitHub Actions workflow with ID: 28646443202
Run Package Apache Arrow Flight SQL ODBC Driver (28646443202) has already completed with 'success'
```
The workflow run is still in progress:
```
$ gh run view 28679576610
* apache-arrow-25.0.0-rc1 Package Apache Arrow Flight SQL ODBC Driver · 28679576610
Triggered via workflow_dispatch less than a minute ago
JOBS
* ODBC Windows Build & Upload Unsigned MSI (ID 85060122105)
- ODBC Windows Upload Unsigned DLL in 0s (ID 85060122620)
- Upload Unsigned ODBC DLL to Release in 0s (ID 85060122628)
For more information about a job, try: gh run view --job=<job-id>
View this run on GitHub: https://github.com/apache/arrow/actions/runs/28679576610
```
### Component(s)
Release
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Release] 07-flightsqlodbc-upload.sh PHASE_BUILD_MSI doesn't correctly watch workflow run [arrow]
Posted by "amoeba (via GitHub)" <gi...@apache.org>.
amoeba commented on issue #50363:
URL: https://github.com/apache/arrow/issues/50363#issuecomment-4878962954
I think I can see the issue from the above output. The workflow we started has id `28679576610`, see:
```
✓ Created workflow_dispatch event for package_odbc.yml at apache-arrow-25.0.0-rc1
https://github.com/apache/arrow/actions/runs/28679576610
```
But the next step finds a workflow with another ID, `28646443202`:
```
Found GitHub Actions workflow with ID: 28646443202
```
This came up in the PR review (https://github.com/apache/arrow/pull/49788) and we opted to try the current approach instead of parsing the URL from the above output.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Release] 07-flightsqlodbc-upload.sh PHASE_BUILD_MSI doesn't correctly watch workflow run [arrow]
Posted by "yohimik (via GitHub)" <gi...@apache.org>.
yohimik commented on issue #50363:
URL: https://github.com/apache/arrow/issues/50363#issuecomment-5610501841
I reproduced the stale-run selection against [`utils-watch-gh-workflow.sh` at df40dd4](https://github.com/apache/arrow/blob/df40dd400bbaea59e621123ead6c41a51f0fc654/dev/release/utils-watch-gh-workflow.sh) with a stub `gh`: `run list` returns the previous successful ID while the newly dispatched run is not yet visible. The helper immediately watches the old ID and exits 0. No build, signing or publication was performed in this reproduction.
A useful regression set would cover:
- An old success remains visible before the new run appears.
- Two dispatches use the same tag and workflow.
- The selected run fails or is cancelled.
- No matching run appears before a bounded deadline.
The helper already uses `--exit-status`, so failure propagation is present; identifying the correct invocation is the gap. Capturing the dispatch's run ID, where the supported CLI/API provides it, avoids the discovery race. Otherwise a unique dispatch input exposed in the run name is stronger than tag, SHA or creation time alone. Retain that ID for recovery, then verify the MSI belongs to that invocation before signing it.
The final [25.0.0 release](https://github.com/apache/arrow/releases/tag/apache-arrow-25.0.0) currently contains the MSI and DLL assets. This is a remaining script regression, not a claim those artifacts are missing.
Disclosure: I maintain [dispat](https://github.com/yohimik/dispat), where dependency ordering and recorded completion are useful for multi-stage releases. An external workflow adapter still has to preserve this invocation identity; orchestration alone would not fix the wrong-run lookup.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org