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.

Sign up for GitHub

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

Jump to bottom

Flake in store_test #9506

Closed
lahabana opened this issue Mar 6, 2024 · 5 comments
Closed

Flake in store_test #9506

lahabana opened this issue Mar 6, 2024 · 5 comments
Labels
area/ci-cd kind/ci-flake Used to track flakes in CI triage/accepted The issue was reviewed and is complete enough to start working on it triage/stale Inactive for some time. It will be triaged again

Comments

@lahabana
Copy link
Contributor

lahabana commented Mar 6, 2024

What happened?

------------------------------
• [FAILED] [3.981 seconds]
PostgresStore template Store: pq Update() [It] should update an existing resource
github.com/kumahq/kuma/pkg/test/store/store_test_template.go:131

  Timeline >>
  2024-03-05T18:03:12Z	INFO	config	skipping reading config from file
  "level"=0 "msg"="Connecting and creating database to container id: 4bb43e0e0e62dd38d28ead51a6329d3edcb75410b89ae348b0a067a177579192, port 5432 mapped to host port: 32771; db name kuma_dd1f9fd37ebd4c91987a2b0a557b0b7b"
  "level"=0 "msg"="Database successfully created and started" "name"="kuma_dd1f9fd37ebd4c91987a2b0a557b0b7b"
  2024-03-05T18:03:12Z	INFO	config	skipping reading config from file
  "level"=0 "msg"="Connecting and creating database to container id: 4bb43e0e0e62dd38d28ead51a6329d3edcb75410b89ae348b0a067a177579192, port 5432 mapped to host port: 32771; db name kuma_754db260833f4db49515ec3fa357aecf"
  "level"=0 "msg"="Database successfully created and started" "name"="kuma_754db260833f4db49515ec3fa357aecf"
  2024-03-05T18:03:13Z	INFO	config	skipping reading config from file
  "level"=0 "msg"="Connecting and creating database to container id: 4bb43e0e0e62dd38d28ead51a6329d3edcb75410b89ae348b0a067a177579192, port 5432 mapped to host port: 32771; db name kuma_0d1f3fd1d24e4635a193aff576cee7cb"
  "level"=0 "msg"="Database successfully created and started" "name"="kuma_0d1f3fd1d24e4635a193aff576cee7cb"
  2024-03-05T18:03:13Z	INFO	config	skipping reading config from file
  "level"=0 "msg"="Connecting and creating database to container id: 4bb43e0e0e62dd38d28ead51a6329d3edcb75410b89ae348b0a067a177579192, port 5432 mapped to host port: 32771; db name kuma_c829aa51a6ad4128a561a96f23dedb01"
  "level"=0 "msg"="Database successfully created and started" "name"="kuma_c829aa51a6ad4128a561a96f23dedb01"
  2024-03-05T18:03:13Z	INFO	config	skipping reading config from file
  "level"=0 "msg"="Connecting and creating database to container id: 4bb43e0e0e62dd38d28ead51a6329d3edcb75410b89ae348b0a067a177579192, port 5432 mapped to host port: 32771; db name kuma_514734ef3eb9490f97bb2ffd48424478"
  "level"=0 "msg"="Database successfully created and started" "name"="kuma_514734ef3eb9490f97bb2ffd48424478"
  2024-03-05T18:03:14Z	INFO	config	skipping reading config from file
  "level"=0 "msg"="Connecting and creating database to container id: 4bb43e0e0e62dd38d28ead51a6329d3edcb75410b89ae348b0a067a177579192, port 5432 mapped to host port: 32771; db name kuma_7fbdebf0e69d454cbc346d656287148c"
  2024-03-05T18:03:14Z	INFO	postgres-event-listener-pgx	started
  2024-03-05T18:03:14Z	INFO	postgres-event-listener	start monitoring
  2024-03-05T18:03:14Z	ERROR	postgres-event-listener	failed to listen on events	{"error": "error getting connection: failed to connect to `host=localhost user=kuma database=kuma_c9391220c55[540](https://github.com/kumahq/kuma/actions/runs/8160591183/job/22307689546#step:6:541)ce9d88fa83027aed54`: dial error (dial tcp [::1]:32770: connect: connection refused)", "errorVerbose": "failed to connect to `host=localhost user=kuma database=kuma_c9391220c55540ce9d88fa83027aed54`: dial error (dial tcp [::1]:32770: connect: connection refused)\nerror getting connection\ngithub.com/kumahq/kuma/pkg/plugins/common/postgres.(*PgxListener).handleNotifications\n\tgithub.com/kumahq/kuma/pkg/plugins/common/postgres/pgx_listener.go:79\ngithub.com/kumahq/kuma/pkg/plugins/common/postgres.(*PgxListener).run\n\tgithub.com/kumahq/kuma/pkg/plugins/common/postgres/pgx_listener.go:67\nruntime.goexit\n\truntime/asm_amd64.s:1650"}
  github.com/kumahq/kuma/pkg/plugins/resources/postgres/events.(*listener).Start
  	github.com/kumahq/kuma/pkg/plugins/resources/postgres/events/listener.go:55
  github.com/kumahq/kuma/pkg/core/runtime/component.(*resilientComponent).Start.func1
  	github.com/kumahq/kuma/pkg/core/runtime/component/resilient.go:43
  2024-03-05T18:03:14Z	INFO	postgres-event-listener-pgx	stopped
  2024-03-05T18:03:14Z	ERROR	postgres-event-listener-component	component terminated with an error	{"generationID": 20, "error": "error getting connection: failed to connect to `host=localhost user=kuma database=kuma_c9391220c55540ce9d88fa83027aed54`: dial error (dial tcp [::1]:32770: connect: connection refused)", "errorVerbose": "failed to connect to `host=localhost user=kuma database=kuma_c9391220c55540ce9d88fa83027aed54`: dial error (dial tcp [::1]:32770: connect: connection refused)\nerror getting connection\ngithub.com/kumahq/kuma/pkg/plugins/common/postgres.(*PgxListener).handleNotifications\n\tgithub.com/kumahq/kuma/pkg/plugins/common/postgres/pgx_listener.go:79\ngithub.com/kumahq/kuma/pkg/plugins/common/postgres.(*PgxListener).run\n\tgithub.com/kumahq/kuma/pkg/plugins/common/postgres/pgx_listener.go:67\nruntime.goexit\n\truntime/asm_amd64.s:1650"}
  github.com/kumahq/kuma/pkg/core/runtime/component.(*resilientComponent).Start
  	github.com/kumahq/kuma/pkg/core/runtime/component/resilient.go:51
  github.com/kumahq/kuma/pkg/plugins/resources/postgres_test.setupListeners.func1
  	github.com/kumahq/kuma/pkg/plugins/resources/postgres/listener_test.go:133
  "level"=0 "msg"="Database successfully created and started" "name"="kuma_7fbdebf0e69d454cbc346d656287148c"
  2024-03-05T18:03:14Z	INFO	config	skipping reading config from file
  "level"=0 "msg"="Connecting and creating database to container id: 4bb43e0e0e62dd38d28ead51a6329d3edcb7[541](https://github.com/kumahq/kuma/actions/runs/8160591183/job/22307689546#step:6:542)0b89ae348b0a067a177579192, port [543](https://github.com/kumahq/kuma/actions/runs/8160591183/job/22307689546#step:6:544)2 mapped to host port: 32771; db name kuma_7b7364dd652742d3a0d422a1264ba784"
  "level"=0 "msg"="Database successfully created and started" "name"="kuma_7b7364dd652742d3a0d422a1264ba784"
  2024-03-05T18:03:15Z	INFO	config	skipping reading config from file
  "level"=0 "msg"="Connecting and creating database to container id: 4bb43e0e0e62dd38d28ead51a6329d3edcb75410b89ae348b0a067a177579192, port 5432 mapped to host port: 32771; db name kuma_511aa4f2dc7d4940a0dc50b948d0[544](https://github.com/kumahq/kuma/actions/runs/8160591183/job/22307689546#step:6:545)9"
  "level"=0 "msg"="Database successfully created and started" "name"="kuma_511aa4f2dc7d4940a0dc50b948d05449"
  [FAILED] in [It] - github.com/kumahq/kuma/pkg/test/store/store_test_template.go:173 @ 03/05/24 18:03:16.064
  << Timeline

  [FAILED] Expected
      <int>: 859
  to equal
      <int>: 858
  In [It] at: github.com/kumahq/kuma/pkg/test/store/store_test_template.go:173 @ 03/05/24 18:03:16.064

https://github.com/kumahq/kuma/actions/runs/8160591183/job/22307689546

I don't remember seeing unit tests flake anytime.
@lahabana lahabana added area/ci-cd triage/pending This issue will be looked at on the next triage meeting kind/bug A bug labels Mar 6, 2024
@lukidzi lukidzi added kind/ci-flake Used to track flakes in CI and removed kind/bug A bug labels Mar 7, 2024
@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Mar 12, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jun 11, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lobkovilya lobkovilya removed the triage/stale Inactive for some time. It will be triaged again label Jun 17, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Sep 16, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Sep 16, 2024
@slonka
Copy link
Contributor

slonka commented Sep 16, 2024

Has anyone seen this recently? 🤔

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 16, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi
Copy link
Contributor

lukidzi commented Dec 16, 2024

Haven't seen, closing

@lukidzi lukidzi closed this as not planned Won't fix, can't repro, duplicate, stale Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ci-cd kind/ci-flake Used to track flakes in CI triage/accepted The issue was reviewed and is complete enough to start working on it triage/stale Inactive for some time. It will be triaged again
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lahabana @slonka @jakubdyszkiewicz @lobkovilya @lukidzi