casra-developers commented on PR #29935:
URL: https://github.com/apache/airflow/pull/29935#issuecomment-1469505442

   > > This is very weird since I followed the online resources provided by 
Github.
   > 
   > The indentation is wrong for those lines - they should be indented more - 
this is simply not valid yaml if it is not.
   
   I fixed the indentation in the .yml file but the plugin still complains 
about "jobs" and "on" not being allowed properties and "runs" missing.
   ```yml
   name: 'Running Tests on Windows'
   description: 'Verification that tests run on Windows.'
   on: [push]
   jobs:
     test:
       runs-on: windows-latest
       steps:
         - name: Check out repository code
           uses: actions/checkout@v2
   
         - name: Setup Python
           uses: actions/setup-python@v2
           with:
             python-version: "3.x"
   
         - name: Setup venv
           run: |
             python -m venv venv
             .\venv\Scripts\activate
   
         - name: Install dependencies
           run: |
             pip install ".[devel]"
   
         - name: Run tests
           run: |
             pytest --verbosity=0 --strict-markers --durations=100 --maxfail=50 
--color=yes --junitxml=/files/test_result-Always-sqlite.xml --timeouts-order 
moi --setup-timeout=60 --execution-timeout=60 --teardown-timeout=60 
--output=/files/warnings-Always-sqlite.txt --disable-warnings -rfEX 
--with-db-init --ignore tests/providers --ignore tests/charts tests
   ```
   I used this site among others to create the file: 
https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python
   I would guess that the documentation is more accurate than the plugin so can 
I just ignore it?


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