Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dm on dataflow engine e2e test failed #5535

Closed
amyangfei opened this issue May 23, 2022 · 0 comments · Fixed by #5550
Closed

dm on dataflow engine e2e test failed #5535

amyangfei opened this issue May 23, 2022 · 0 comments · Fixed by #5550
Assignees
Labels
area/engine Issues or PRs related to Dataflow Engine. component/test Unit tests and integration tests component. severity/minor type/bug The issue is confirmed as a bug.

Comments

@amyangfei
Copy link
Contributor

Which jobs are flaking?

DM-workflow

Which test(s) are flaking?

TestDMJob

Jenkins logs or GitHub Actions link

https://github.com/pingcap/tiflow/runs/6553393749?check_suite_focus=true

[2022/05/23 10:33:56.486 +00:00] [INFO] [sync_worker.go:51] ["init sync worker"]
[2022/05/23 10:33:56.486 +00:00] [INFO] [broker.go:176] ["Using local storage with path"] [path=039a887e-2223-4e4a-98c6-7f623ab212ac/test/mysql-replica-01]
[2022/05/23 10:33:56.488 +00:00] [WARN] [task_runner.go:256] ["Task init returned error"] [id=93f7b638-d373-4c31-960d-ab1bb465ed11] [error="panic: empty flavor with empty gtid is invalid"] [errorVerbose="panic: empty flavor with empty gtid is invalid\ngithub.com/pingcap/tiflow/engine/executor/worker.(*TaskRunner).onNewTask.func2.1\n\tgithub.com/pingcap/tiflow/engine/executor/worker/task_runner.go:225\nruntime.gopanic\n\truntime/panic.go:838\ngithub.com/pingcap/tiflow/dm/pkg/gtid.MustZeroGTIDSet\n\tgithub.com/pingcap/tiflow/dm/pkg/gtid/gtid.go:70\ngithub.com/pingcap/tiflow/dm/pkg/binlog.MustZeroLocation\n\tgithub.com/pingcap/tiflow/dm/pkg/binlog/position.go:256\ngithub.com/pingcap/tiflow/dm/syncer.NewRemoteCheckPoint\n\tgithub.com/pingcap/tiflow/dm/syncer/checkpoint.go:385\ngithub.com/pingcap/tiflow/dm/syncer.NewSyncer\n\tgithub.com/pingcap/tiflow/dm/syncer/syncer.go:274\ngithub.com/pingcap/tiflow/engine/dm.(*syncWorker).InitImpl\n\tgithub.com/pingcap/tiflow/engine/dm/sync_worker.go:67\ngithub.com/pingcap/tiflow/engine/lib.(*DefaultBaseWorker).Init\n\tgithub.com/pingcap/tiflow/engine/lib/worker.go:212\ngithub.com/pingcap/tiflow/engine/executor/worker.(*TaskRunner).onNewTask.func2\n\tgithub.com/pingcap/tiflow/engine/executor/worker/task_runner.go:230\ngithub.com/pingcap/tiflow/engine/executor/worker.(*TaskRunner).onNewTask.func3\n\tgithub.com/pingcap/tiflow/engine/executor/worker/task_runner.go:255\nruntime.goexit\n\truntime/asm_amd64.s:1571"]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x2a755b9]

goroutine 1220 [running]:
github.com/pingcap/tiflow/engine/dm.(*unitHolder).close(0x0)
        github.com/pingcap/tiflow/engine/dm/unit.go:210 +0x19
github.com/pingcap/tiflow/engine/dm.(*syncWorker).CloseImpl(0xc000d7d068?, {0x3110e20?, 0xc001a6a920?})
        github.com/pingcap/tiflow/engine/dm/sync_worker.go:92 +0x1d
github.com/pingcap/tiflow/engine/lib.(*DefaultBaseWorker).Close(0xc0006e5a40, {0x39cad20?, 0xc001a5b2d8?})
        github.com/pingcap/tiflow/engine/lib/worker.go:349 +0x4e
github.com/pingcap/tiflow/engine/executor/worker.(*TaskRunner).onNewTask.func3.1()
        github.com/pingcap/tiflow/engine/executor/worker/task_runner.go:243 +0x58
github.com/pingcap/tiflow/engine/executor/worker.(*TaskRunner).onNewTask.func3()
        github.com/pingcap/tiflow/engine/executor/worker/task_runner.go:257 +0x36b
created by github.com/pingcap/tiflow/engine/executor/worker.(*TaskRunner).onNewTask
        github.com/pingcap/tiflow/engine/executor/worker/task_runner.go:238 +0x5db

Anything else we need to know

  • Does this test exist for other branches as well?

  • Has there been a high frequency of failure lately?

@amyangfei amyangfei added component/test Unit tests and integration tests component. area/engine Issues or PRs related to Dataflow Engine. labels May 23, 2022
@lance6716 lance6716 self-assigned this May 23, 2022
@lance6716 lance6716 added type/bug The issue is confirmed as a bug. severity/minor labels May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/engine Issues or PRs related to Dataflow Engine. component/test Unit tests and integration tests component. severity/minor type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants