Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[Bug][e2e] Several plugin e2e tests fail on a fresh database because they depend on tables created by other tests

Fermée
  • Quelque chose ne va pas ?
#9,223 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

@chenwei791129 y travaille déjà.

Depuis le 14/10/2026.

  • #9224 par @chenwei791129 — ouverte

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
go, mysql
Domaine
testing

Piste de recherche

Start with e2ehelper.DataFlowTester and the failing TestCalculateCLTimeDataFlow in plugins/dora/e2e/, then check scripts/e2e-test-go-plugins.sh to see the shared-database order. Reproduce on an empty database with go test -count=1 ./plugins/<plugin>/e2e/..., and make each test create the tables its subtasks read or write. Done means every listed package and test passes alone on a fresh database.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Search before asking
  • I had searched in the issues and found no similar issues.
What happened

Several Go plugin e2e tests fail when they run on a fresh, empty database, for example when you run one plugin's e2e package or one test on its own:

--- FAIL: TestCalculateCLTimeDataFlow
panic: failed to batch fetch first reviews (500)
	Wraps: (3) Error 1146 (42S02): Table 'lake_test.accounts' doesn't exist

e2ehelper.DataFlowTester runs no migrations. A test only has the tables it flushes or imports. Some tests run subtasks that read or write other tables, for example a converter that deletes old board_issues rows, or a query that joins accounts. Those tables exist in CI only because an earlier test created them: scripts/e2e-test-go-plugins.sh runs every plugin's e2e package in go list order on one shared database.

Packages that fail on their own (fresh database per package):

Package Missing table Test
dora/e2e accounts TestCalculateCLTimeDataFlow (the first review query joins accounts since #9000)
customize/e2e board_issues TestImportIssueChangelogDataFlow, TestImportIssueCommitDataFlow
gitlab/e2e issue_labels TestGitlabIssueDataFlow
opsgenie/e2e board_issues TestIncidentDataFlow
pagerduty/e2e board_issues TestIncidentDataFlow
teambition/e2e board_sprints TestTeambitionSprints

Tests that fail with go test -run <Test> (fresh database per test), because an earlier test in the same package created the tables:

  • customize: TestImportIssueWorklogDataFlow
  • gitlab: TestGitlabMrDataFlow, TestGitlabMrDetailDataFlow, TestGitlabMrNoteDataFlow
  • teambition: TestTeambitionTask
  • bitbucket: TestCommentDataFlow
  • github: TestMilestoneDataFlow, TestPrReviewDataFlow
  • jira: TestEpicDataflow, TestIssueRelationshipDataFlow, TestIssueSubtaskWithoutMapping
  • linear: TestLinearIssueHistoryDataFlow
  • tapd: TestTapdBugCustomizeDueDate, TestTapdStoryCustomizeDueDate, TestTapdTaskCustomizeDueDate

Some of these tests also read data that an earlier test left behind, not only the table:

  • The bitbucket issue comment converter joins _tool_bitbucket_issues, which account_test.go fills.
  • The tapd due date tests use the statuses and workitem types that the test before them imports.

Also, the DORA fixture has no bot account, so nothing in the e2e tests covers the bot exclusion added in #9000.

What do you expect to happen

Each e2e package and each e2e test passes on a fresh database. A test sets up every table its subtasks use and does not depend on the order tests run in.

How to reproduce
  1. Create an empty MySQL database.
  2. From backend/:
export E2E_DB_URL='mysql://merico:[email protected]:3306/lake_test?charset=utf8mb4&parseTime=True&loc=UTC'
TZ=UTC go test -count=1 ./plugins/dora/e2e/...

The other packages fail the same way. For the per-test failures, run e.g. go test -count=1 -run '^TestCommentDataFlow$' ./plugins/bitbucket/e2e/ on an empty database.

Anything else

CI passes today only because of the order the tests run in. It would break if the e2e tests ran in parallel or on a database per package.

Version

main (4ad2f66df)

Are you willing to submit PR?
  • Yes I am willing to submit a PR!
Code of Conduct
Langage dominant
Go
Étoiles
3.2k
Forks
830
Merge moyen
2 j 12 h
PR mergées (30 j)
61

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de apache/devlake

Toutes les issues de apache/devlake

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.