Update log tests

[sadym-chromium]

• Remove implementation-defined tests. log.entryAdded handler in step 5.2 says:

If arg is a primitive ECMAScript value, append ToString(arg) to text. Otherwise append an implementation-defined string to text.

• Switch from classic current_time to BiDi current_time_bidi.

[juliandescottes]

Thanks! Would be great to still test objects against any_string, and for the fixture we can simply migrate the current one to bidi.

[sadym-chromium]

Thanks! Would be great to still test objects against any_string, and for the fixture we can simply migrate the current one to bidi.

@juliandescottes done, PTAL

[whimboo]

@sadym-chromium as it looks like some tests are failing with Chrome. Even it may be unrelated to your changes maybe you could have a look? Thanks.

[juliandescottes]

This looks good to me, as @whimboo said it would be good to know why there were chrome failures, but looking at the tests that failed I can't really see any relation with this patch?

[sadym-chromium]

The logging in Chromium was not implemented correctly. The PR GoogleChromeLabs/chromium-bidi#243 should address it. The problem is the BiDi implementation in ChromeDriver is updated only with ChromeDriver itself, which happens once a month.

[juliandescottes]

I imagine @whimboo was referring to the CI failures on /webdriver/tests/bidi/browsing_context/navigate/error.py and /webdriver/tests/get_active_element/get.py ?

[whimboo]

Maybe there were some CI issues. Lets retrigger the tests again.

[sadym-chromium]

I guess we can push the change, and fix the navigation tests in ChromeDriverBiDi separately.

[whimboo]

That's fine with me. Thanks.

[foolip]

Admin merging to ignore wpt-chrome-dev-stability failure, as requested.