Description:
------------
error_log emitted log entry timezone appears to be using the "Default Timezone" first and before falling back to date.timezone rather than just using date.timezone as the overriding variable.

So this maybe the expected behavior now, but the last error_log bugfix notes that I read the goal was to use date.timezone only, but there maybe superseding requirements that I missed or this is a feature request or documentation update.


After reading tracing the PHP source it appears error_log uses the user function:  php_format_date

Source: https://github.com/php/php-src/blob/3c2f433b2b0a4334b4f96358660ead92abdbb2cb/main/main.c#L888

Which uses guess timezone, which follows the fallback logic of 
* "Default Timezone"
* date.timezone
* UTC
(I maybe wrong) 

The concern is in a web application where users may specify their default Timezone (e.g. Drupal) then error_log entries can have different timezones. 

Personally opinion date.timezone should be the timezone for error_log as it is an ini value rather than a mutable value that may change between session, request or execution. So the error log timezone can remain consistent across multiple servers, executions. just my $.02