Bug 175522 – Only create directory and sandbox extension handle for storage directories if they are set

• Component: New Bugs
• Status: RESOLVED FIXED

[Tim Horton]

Only create directory and sandbox extension handle for storage directories if they are set

[Tim Horton]

Created attachment 318008 [details]
Patch

[Brady Eidson]

Comment on attachment 318008 [details]
Patch

The IDB change was causing tests to fail due to that noisy logging.

Are these others causing tests to fail with noisy logging?

If not, can we add some tests that will fail with the noisy logging?

(Because we should test this kind of thing)

[Tim Horton]

Most tests don’t care about logging; seems like it would be pretty weird to add a perf test to test this.

Maybe we can make a API test that temporarily slurps stdout?

[Brady Eidson]

(In reply to Tim Horton from comment #3)
> Most tests don’t care about logging; seems like it would be pretty weird to
> add a perf test to test this.
> 
> Maybe we can make a API test that temporarily slurps stdout?

My goal wasn't necessarily to make tests care about logging so much as make tests track this behavior.

[Tim Horton]

Created attachment 318027 [details]
With a weird test

[Tim Horton]

(In reply to Brady Eidson from comment #4)
> (In reply to Tim Horton from comment #3)
> > Most tests don’t care about logging; seems like it would be pretty weird to
> > add a perf test to test this.
> > 
> > Maybe we can make a API test that temporarily slurps stdout?
> 
> My goal wasn't necessarily to make tests care about logging so much as make
> tests track this behavior.

But, like you yourself said in https://bugs.webkit.org/show_bug.cgi?id=171522, there's not a great way to test this except for the side-effect of the logging. So I wrote a very strange test that makes sure we don't log during initialization. Which might be valuable and interesting, and might just be bizarre. But it does fail before and pass after...

[Brady Eidson]

(In reply to Tim Horton from comment #6)
> (In reply to Brady Eidson from comment #4)
> > (In reply to Tim Horton from comment #3)
> > > Most tests don’t care about logging; seems like it would be pretty weird to
> > > add a perf test to test this.
> > > 
> > > Maybe we can make a API test that temporarily slurps stdout?
> > 
> > My goal wasn't necessarily to make tests care about logging so much as make
> > tests track this behavior.
> 
> But, like you yourself said in
> https://bugs.webkit.org/show_bug.cgi?id=171522, there's not a great way to
> test this except for the side-effect of the logging. So I wrote a very
> strange test that makes sure we don't log during initialization. Which might
> be valuable and interesting, and might just be bizarre. But it does fail
> before and pass after...

Let me rephrase.

My goal was "Can we make a regression test of this that fails before and passes after?"
My observation was "In the other case, for example, the logging fulfilled this goal"
The unspoken part was "The logging is clearly a bizarre way to test, but if it's the only way, so be it"

Really, just want a test. And if your test is bizarre... but works... so be it.

[WebKit Commit Bot]

Comment on attachment 318027 [details]
With a weird test

Clearing flags on attachment: 318027

Committed r220709: <http://trac.webkit.org/changeset/220709>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Radar WebKit Bug Importer]

<rdar://problem/33878647>