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

[Flaky test] job_errors_permissions #6751

Open
jnidzwetzki opened this issue Mar 8, 2024 · 0 comments
Open

[Flaky test] job_errors_permissions #6751

jnidzwetzki opened this issue Mar 8, 2024 · 0 comments
Labels
flaky-test Issue about a flaky test

Comments

@jnidzwetzki
Copy link
Contributor

Which test is flaky?

job_errors_permissions

Since when has the test been flaky?

08.03.2024

Link to the failed test run

https://github.com/timescale/timescaledb/actions/runs/8196660597/job/22417341187

Log output

diff -u /mnt/d/a/timescaledb/timescaledb/tsl/test/expected/job_errors_permissions.out /mnt/d/a/timescaledb/timescaledb/build_wsl/tsl/test/results/job_errors_permissions.out
--- /mnt/d/a/timescaledb/timescaledb/tsl/test/expected/job_errors_permissions.out	2024-03-08 00:21:07.368910000 +0000
+++ /mnt/d/a/timescaledb/timescaledb/build_wsl/tsl/test/results/job_errors_permissions.out	2024-03-08 00:31:36.882799000 +0000
@@ -90,21 +90,19 @@
 SET ROLE :ROLE_DEFAULT_PERM_USER_2;
 SELECT job_id, proc_schema, proc_name, sqlerrcode, err_message
 FROM timescaledb_information.job_errors WHERE job_id >= 1000;
- job_id | proc_schema |  proc_name   | sqlerrcode |                     err_message                     
---------+-------------+--------------+------------+-----------------------------------------------------
-   1002 | public      | custom_proc2 | 40001      | could not serialize access due to concurrent update
-(1 row)
+ job_id | proc_schema | proc_name | sqlerrcode | err_message 
+--------+-------------+-----------+------------+-------------
+(0 rows)
 
 SET ROLE :ROLE_SUPERUSER;
 SELECT job_id, proc_schema, proc_name, sqlerrcode, err_message
 FROM timescaledb_information.job_errors WHERE job_id >= 1000;
- job_id | proc_schema |  proc_name   | sqlerrcode |                     err_message                     
---------+-------------+--------------+------------+-----------------------------------------------------
-   1000 | public      | job_fail     | P0001      | raising an exception
-   1002 | public      | custom_proc2 | 40001      | could not serialize access due to concurrent update
-  11111 |             |              |            | not an error
-  22222 |             |              |            | job crash detected, see server logs
-(4 rows)
+ job_id | proc_schema | proc_name | sqlerrcode |             err_message             
+--------+-------------+-----------+------------+-------------------------------------
+   1000 | public      | job_fail  | P0001      | raising an exception
+  11111 |             |           |            | not an error
+  22222 |             |           |            | job crash detected, see server logs
+(3 rows)

Reason for flakiness

No response

@jnidzwetzki jnidzwetzki added the flaky-test Issue about a flaky test label Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test Issue about a flaky test
Projects
None yet
Development

No branches or pull requests

1 participant