eitsupi commented on PR #3695:
URL: https://github.com/apache/arrow-adbc/pull/3695#issuecomment-3516719594

   > I pushed up a new step but it still passes. The exact same command that's 
used in the step fails locally. Looking at the raw logs, I see the clippy step 
pulls down the windows crates so I wonder if that's doing something unexpected?
   
   IIUC, isn't CI running on the post-merge state (`pull/3695/merge` here, 
where the Windows bug has already been fixed)?
   
   ```
      "C:\Program Files\Git\bin\git.exe" checkout --progress --force 
refs/remotes/pull/3695/merge
     Note: switching to 'refs/remotes/pull/3695/merge'.
     
     You are in 'detached HEAD' state. You can look around, make experimental
     changes and commit them, and you can discard any commits you make in this
     state without impacting any branches by switching back to a branch.
     
     If you want to create a new branch to retain commits you create, you may
     do so (now or later) by using -c with the switch command. Example:
     
       git switch -c <new-branch-name>
     
     Or undo this operation with:
     
       git switch -
     
     Turn off this advice by setting config variable advice.detachedHead to 
false
     
     HEAD is now at 1cc084125 Merge 62f63e316cfe648dc39355bcfedc6f748a28db34 
into 34985ff324dbe923369d9585a2d68186e573a0e1
   ```
   
   
https://github.com/apache/arrow-adbc/actions/runs/19253604196/job/55043462638?pr=3695#step:2:179


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to