(superset) branch double_pylint updated (7410deafef -> 3b07cc9049)

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

maximebeauchemin pushed a change to branch double_pylint
in repository https://gitbox.apache.org/repos/asf/superset.git


 discard 7410deafef chore: testing that running tests twice fails
     new 3b07cc9049 chore: testing that running tests twice fails

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (7410deafef)
            \
             N -- N -- N   refs/heads/double_pylint (3b07cc9049)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:

(superset) 01/01: chore: testing that running tests twice fails

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

maximebeauchemin pushed a commit to branch double_pylint
in repository https://gitbox.apache.org/repos/asf/superset.git

commit 3b07cc90497d2738874652761e3e2e53dfcba526
Author: Maxime Beauchemin <ma...@gmail.com>
AuthorDate: Mon Jun 10 15:23:28 2024 -0700

    chore: testing that running tests twice fails
    
    Recently I noted that some tests fail if they run twice, and wanted to
    confirm that this is the case in CI too with a quick DRAFT PR.
    
    Once I prove that's the case, I'll be able to prove that my fix for it
    also fixes the issue with double runs.
---
 .github/workflows/superset-python-integrationtest.yml | 1 +
 .github/workflows/superset-python-unittest.yml        | 3 ++-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/superset-python-integrationtest.yml b/.github/workflows/superset-python-integrationtest.yml
index fec35ef9db..a0a0f2defc 100644
--- a/.github/workflows/superset-python-integrationtest.yml
+++ b/.github/workflows/superset-python-integrationtest.yml
@@ -124,6 +124,7 @@ jobs:
         if: steps.check.outputs.python
         run: |
           ./scripts/python_tests.sh
+          ./scripts/python_tests.sh
       - name: Upload code coverage
         uses: codecov/codecov-action@v4
         with:
diff --git a/.github/workflows/superset-python-unittest.yml b/.github/workflows/superset-python-unittest.yml
index d26f0435ed..c88a30c0c0 100644
--- a/.github/workflows/superset-python-unittest.yml
+++ b/.github/workflows/superset-python-unittest.yml
@@ -44,7 +44,8 @@ jobs:
           SUPERSET_TESTENV: true
           SUPERSET_SECRET_KEY: not-a-secret
         run: |
-          pytest --durations-min=0.5 --cov-report= --cov=superset ./tests/common ./tests/unit_tests --cache-clear
+          pytest --durations-min=0.5  --cov-report= --cov=superset ./tests/common ./tests/unit_tests
+          pytest --durations-min=0.5  ./tests/common ./tests/unit_tests
       - name: Upload code coverage
         uses: codecov/codecov-action@v4
         with: