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

[Flaky test] telemetry stats #6898

Closed
fabriziomello opened this issue May 8, 2024 · 0 comments · Fixed by #6907
Closed

[Flaky test] telemetry stats #6898

fabriziomello opened this issue May 8, 2024 · 0 comments · Fixed by #6907
Labels
flaky-test Issue about a flaky test

Comments

@fabriziomello
Copy link
Contributor

fabriziomello commented May 8, 2024 •
edited

Which test is flaky?

telemetry_stats-${PG_VERSION}

Since when has the test been flaky?

May 6th, 2024

Link to the failed test run

https://github.com/timescale/timescaledb/actions/runs/8994009665/job/24707134414?pr=6894
https://github.com/timescale/timescaledb/actions/runs/8990693698/job/24696598336?pr=6890
https://github.com/timescale/timescaledb/actions/runs/8973620139/job/24650353471?pr=6889

Log output

not ok 16    - telemetry_stats-16                        575 ms
diff -u /Users/runner/work/timescaledb/timescaledb/tsl/test/expected/telemetry_stats-16.out /Users/runner/work/timescaledb/timescaledb/build/tsl/test/results/telemetry_stats-16.out
--- /Users/runner/work/timescaledb/timescaledb/tsl/test/expected/telemetry_stats-16.out	2024-05-06 20:46:33
+++ /Users/runner/work/timescaledb/timescaledb/build/tsl/test/results/telemetry_stats-16.out	2024-05-06 20:50:44
@@ -527,11 +527,11 @@
      },                                        +
      "user_defined_action": {                  +
          "total_runs": 3,                      +
-         "total_crashes": 1,                   +
-         "total_duration": "@ 0",              +
+         "total_crashes": 0,                   +
+         "total_duration": "@ 0.009673 secs",  +
          "total_failures": 2,                  +
-         "total_successes": 0,                 +
-         "max_consecutive_crashes": 1,         +
+         "total_successes": 1,                 +
+         "max_consecutive_crashes": 0,         +
          "total_duration_failures": "@ 4 secs",+
          "max_consecutive_failures": 1         +
      },                                        +

Reason for flakiness

No response
@fabriziomello fabriziomello added the flaky-test Issue about a flaky test label May 8, 2024
@fabriziomello fabriziomello changed the title [Flaky test] <Title> [Flaky test] telemetry stats May 8, 2024
fabriziomello added a commit to fabriziomello/timescaledb that referenced this issue May 10, 2024
@fabriziomello
Fix telemetry stats flaky regression test
d478198 
In timescale#6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes timescale#6898
@fabriziomello fabriziomello mentioned this issue May 10, 2024
Merged
fabriziomello added a commit to fabriziomello/timescaledb that referenced this issue May 13, 2024
@fabriziomello
Fix telemetry stats flaky regression test
0a549ee 
In timescale#6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes timescale#6898
fabriziomello added a commit to fabriziomello/timescaledb that referenced this issue May 13, 2024
@fabriziomello
Fix telemetry stats flaky regression test
13de751 
In timescale#6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes timescale#6898
fabriziomello added a commit to fabriziomello/timescaledb that referenced this issue May 13, 2024
@fabriziomello
Fix telemetry stats regression test
64e822b 
In timescale#6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes timescale#6898
fabriziomello added a commit to fabriziomello/timescaledb that referenced this issue May 14, 2024
@fabriziomello
Fix telemetry stats regression test
875377f 
In timescale#6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes timescale#6898
fabriziomello added a commit to fabriziomello/timescaledb that referenced this issue May 14, 2024
@fabriziomello
Fix telemetry stats regression test
8861c6c 
In timescale#6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes timescale#6898
fabriziomello added a commit to fabriziomello/timescaledb that referenced this issue May 15, 2024
@fabriziomello
Fix telemetry stats regression test
c0f68d1 
In timescale#6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes timescale#6898
fabriziomello added a commit to fabriziomello/timescaledb that referenced this issue May 15, 2024
@fabriziomello
Fix telemetry stats regression test
a35f139 
In timescale#6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes timescale#6898
fabriziomello added a commit that referenced this issue May 15, 2024
@fabriziomello
Fix telemetry stats regression test
791dcc4 
In #6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes #6898
github-actions bot pushed a commit that referenced this issue May 15, 2024
@fabriziomello @timescale-automation
Fix telemetry stats regression test
5c347cb 
In #6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes #6898

(cherry picked from commit 791dcc4)
Merged
fabriziomello added a commit that referenced this issue May 16, 2024
@fabriziomello
Fix telemetry stats regression test
331e9b9 
In #6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes #6898

(cherry picked from commit 791dcc4)
fabriziomello added a commit that referenced this issue May 16, 2024
@fabriziomello
Fix telemetry stats regression test
e088f17 
In #6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes #6898

(cherry picked from commit 791dcc4)
timescale-automation pushed a commit that referenced this issue May 16, 2024
@fabriziomello @timescale-automation
Fix telemetry stats regression test
a452e6c 
In #6767 we introduced the track job execution history and renamed the
`policy_job_error_retention` to `policy_job_stat_history_retention` but
we forgot to adapt the telemetry to identify this change.

Fixes #6898

(cherry picked from commit 791dcc4)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
flaky-test Issue about a flaky test
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix telemetry stats regression test fabriziomello/timescaledb
1 participant
@fabriziomello