ashb commented on issue #14228:
URL: https://github.com/apache/airflow/issues/14228#issuecomment-779196607


   @potiuk It's possible this is the cause (and I am doing much cleaning 
already, just not total nuke and refresh) but in this case I think it is very 
unlikely to be the problem.
   
   > Similar error here: 
https://github.com/apache/airflow/pull/14227/checks?check_run_id=1898772208#step:4:16551
   
   In this particular case, the runner two jobs in total:
   
   **CloudWatch Logs Insights**  
   region: eu-central-1  
   log-group-names: GitHubRunners  
   start-time: -86400s  
   end-time: 0s  
   query-string:
   ```
   fields @timestamp, message
   | filter @logStream = 'ip-172-31-25-117'
   | filter message like 'Running job'
   | sort @timestamp desc
   ```
   
-----------------------------------------------------------------------------------------------
   |       @timestamp        |                              message             
                 |
   
|-------------------------|-------------------------------------------------------------------|
   | 2021-02-14 19:05:39.617 | 2021-02-14 19:05:39Z: Running job: Build docs    
                 |
   | 2021-02-14 19:05:39.000 | WRITE LINE: 2021-02-14 19:05:39Z: Running job: 
Build docs         |
   | 2021-02-14 18:53:07.845 | 2021-02-14 18:53:07Z: Running job: Wait for CI 
images             |
   | 2021-02-14 18:53:07.000 | WRITE LINE: 2021-02-14 18:53:07Z: Running job: 
Wait for CI images |
   
-----------------------------------------------------------------------------------------------
   
   Since the only previous job was Wait for CI images" I find it hard to 
believe it would cause 
   
   
   
https://github.com/apache/airflow/commit/79ed11f9147483c4b2f6cc99d5a3e41e89d92968
   
   
   https://github.com/sphinx-doc/sphinx/issues/8880
   
   Not a problem with the runner.
   
   
   


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

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


Reply via email to