Projet

Général

Profil

Bug #56263

jenkins, builds avec tests rbac cassés

Ajouté par Frédéric Péters il y a plus de 2 ans. Mis à jour il y a plus de 2 ans.

Statut:
Fermé
Priorité:
Normal
Assigné à:
Benjamin Dauvergne
Catégorie:
-
Version cible:
-
Début:
19 août 2021
Echéance:
% réalisé:

0%

Temps estimé:
Patch proposed:
Non
Planning:
Non

Description

Les builds nocturnes "full" qui ont l'étape "Unit Tests (rbac)" échouent, depuis le 7 août https://jenkins.entrouvert.org/job/authentic/2167/

Révisions associées

Révision 85c5324e (diff)
Ajouté par Benjamin Dauvergne il y a plus de 2 ans

Jenkinsfile: keep using the existing venv (#56263)

As calling virtualenv two times on the same directory failed.

Révision f0d3227f (diff)
Ajouté par Benjamin Dauvergne il y a plus de 2 ans

Jenkinsfile: run slow authentic tests at night (#56263)

Those test were not run by `tox -e rbac-py3-dj22`.

Also to prevent running again the tests of the main step
pytest_runtest_setup() is modified to skip fast tests when slow tests
are run.

Révision 10e39e0c (diff)
Ajouté par Benjamin Dauvergne il y a plus de 2 ans

Jenkinsfile: factorize reporting as a final step (#56263)

It resolves two problems :
  • pylint reporting failed if called a second time,
  • mergeJunitResults delete junit files on each run and produce a
    junit.xml file, so the second call to it would lose the result of the
    first test run.

There is no problem with coverage as the coverage file is incrementally
updated by each pytest run, I moved it to the end of the Jenkinsfile
anyway for coherency.

Historique

#1

Mis à jour par Benjamin Dauvergne il y a plus de 2 ans

  • Assigné à mis à Benjamin Dauvergne
#2

Mis à jour par Benjamin Dauvergne il y a plus de 2 ans

  • Statut changé de Nouveau à Résolu (à déployer)
commit 128404f09297120710ae28c5ddbd3e37dd507387
Author: Benjamin Dauvergne <bdauvergne@entrouvert.com>
Date:   Fri Aug 20 09:25:05 2021 +0200

    Jenkinsfile: factorize reporting as a final step (#56263)

    It resolves two problems :
    * pylint reporting failed if called a second time,
    * mergeJunitResults delete junit files on each run and produce a
      junit.xml file, so the second call to it would lose the result of the
      first test run.

    There is no problem with coverage as the coverage file is incrementally
    updated by each pytest run, I moved it to the end of the Jenkinsfile
    anyway for coherency.

commit 00f597342ea98e6526956a8cf6b776ba98fb2f91
Author: Benjamin Dauvergne <bdauvergne@entrouvert.com>
Date:   Fri Aug 20 09:24:14 2021 +0200

    Jenkinsfile: run slow authentic tests at night (#56263)

    Those test were not run by `tox -e rbac-py3-dj22`.

    Also to prevent running again the tests of the main step
    pytest_runtest_setup() is modified to skip fast tests when slow tests
    are run.

commit 38a3c67b5b3c9b1968494d5ca888abbf289a7f16
Author: Benjamin Dauvergne <bdauvergne@entrouvert.com>
Date:   Fri Aug 20 09:23:24 2021 +0200

    Jenkinsfile: keep using the existing venv (#56263)

    As calling virtualenv two times on the same directory failed.
#3

Mis à jour par Frédéric Péters il y a plus de 2 ans

  • Statut changé de Résolu (à déployer) à Solution déployée

Formats disponibles : Atom PDF