9 Commits

Author SHA1 Message Date
Reinaldy Rafli
a9a914840f
test: integration test for user feedback (#3880)
* test: integration test for user feedback

* fix(test): try to set shell to True to use environment variables

* chore: debug nodejs sdk output

* test: run user feedback test only on feature-complete

* test: make javascript file relative

* Update _integration-test/nodejs/package.json

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Update _integration-test/test_01_basics.py

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
2025-12-07 12:06:58 +07:00
Reinaldy Rafli
e3e7789853
fix(tests): skip logs event test for errors-only (#3915) 2025-09-03 13:25:21 +01:00
Reinaldy Rafli
af32d373b2
test: run errors-only integration tests (#3910) 2025-09-03 06:05:57 +07:00
Reinaldy Rafli
f5773e8ed5
feat: enable Logs feature (#3912)
* feat: enable Logs feature

* feat: enable swap on all runners

See ce819b8d99
2025-09-02 10:21:03 -07:00
Pierre Massat
8bf5663c0a
fix(eap): Fix dataset parameter to target spans (#3866) 2025-08-12 12:48:43 -07:00
Tobias Wilfert
bf660f3302
fix: Increase timeout for flakey test (#3781) 2025-06-27 06:12:13 +07:00
Anton Pirker
4276f44a07
Make usage of Python SDK future proof (#3714)
Fixes problems that appear when Python SDK 3.0 will be released.
2025-05-27 13:07:44 +02:00
Emmanuel Ferdman
84094424e8
Resolve datetime deprecation warnings (#3686)
# PR Summary
This small PR fixes the `datetime` deprecation warnings which you can find in the CI logs:
```python
 /home/runner/work/_actions/getsentry/self-hosted/master/_integration-test/test_01_basics.py:303: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
```
2025-05-02 12:19:34 +01:00
Burak Yigit Kaya
63b6c0afa7
test: Reorganize backup/restore tests for speed and reliability (#3537)
We should do the backup/restore tests _after_ we do the basic tests. This is both more efficient as we avoid an extra up/down cycle and more meaningful as we will back up and restore an actually used system.

A bit hard to measure directly as this also moves the initial `docker compose up -w` into the test suite but a random run without this patch took about 10m 49s to finish for the testing part whereas with the patch it came down to 9m 10s so **almost 2 minutes faster**!
2025-01-16 09:59:38 -08:00