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

notice in phpunit (THE ERROR HANDLER HAS CHANGED!) #296

Closed
server-may-cry opened this issue May 27, 2016 · 6 comments
Closed

notice in phpunit (THE ERROR HANDLER HAS CHANGED!) #296

server-may-cry opened this issue May 27, 2016 · 6 comments

Comments

@server-may-cry
Copy link

PHPUnit 4.8.25 by Sebastian Bergmann and contributors.

................

Time: 2.58 seconds, Memory: 46.00Mb

OK (16 tests, 105 assertions)

THE ERROR HANDLER HAS CHANGED!

after upgrading from 0.18.1 to 0.19.0 - diff

@dcramer
Copy link
Member

dcramer commented May 27, 2016

Open to suggestions here, but the SDK now installs an error handler by default (which bubbles up). It shouldn't affect anything.

@server-may-cry
Copy link
Author

server-may-cry commented Dec 28, 2016

Solve by stop enable sentry in test environment (when run tests). That was wrong.

@GijsErenstein
Copy link

How i solved this problem:

in bundles.php:
Sentry\SentryBundle\SentryBundle::class => ['prod' => true],

and move the sentry.yaml from packages to packages/prod. you could probably tho the same for some more envs where you do want sentry to be active

Briones pushed a commit to Briones/sentry-php that referenced this issue Feb 20, 2020
@hugochinchilla
Copy link

Can we consider this not fixed?

I have many tests checking the sentry integration and I don't want to disable sentry in test. In test I have decorated the SentryHub with a custom implementation that allows testing sentry without sending events to the server.

@ste93cry
Copy link
Collaborator

Can we consider this not fixed?

Yes, but we're tracking the problem in getsentry/sentry-symfony#421 because it involves Symfony

@hugochinchilla
Copy link

Oh, thank you for pointing this out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants