adamreeve commented on issue #49998:
URL: https://github.com/apache/arrow/issues/49998#issuecomment-4493910890

   Running this locally (`PYTHON=3.10 PANDAS=1.3.4 NUMPY=1.21.2 archery docker 
run conda-python-panda`) and removing the `-q` argument to `mamba install`, it 
looks like mamba is taking a very long time to resolve packages:
   ```
   STEP 5/10: RUN mamba install -y --file arrow/ci/conda_env_sphinx.txt
   Fetch Shard Index for conda-forge/linux-64                                   
                   ⧖ Starting
   Fetch Shard Index for conda-forge/linux-64                                   
             ✔ Done (0.1 sec)
   Fetch Shard Index for conda-forge/noarch                                     
                   ⧖ Starting
   Fetch Shard Index for conda-forge/noarch                                     
             ✔ Done (0.1 sec)
   Fetching and Parsing Packages' Shards                                        
                   ⧖ Starting
   Fetching and Parsing Packages' Shards                                        
             ✔ Done (8.0 sec)
   Using Cached Shard Index for conda-forge/linux-64                            
                       ✔ Done
   Using Cached Shard Index for conda-forge/noarch                              
                       ✔ Done
   Fetching and Parsing Packages' Shards                                        
                   ⧖ Starting
   Fetching and Parsing Packages' Shards                                        
             ✔ Done (0.7 sec)
   
   Pinned packages:
   
     - python=3.10
   
   Resolving Environment                                                        
                   ⧖ Starting
   ```
   
   It has been running for a while and is using 100% of 1 CPU core, I'll wait 
and see if it ever finishes.


-- 
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