@Ignore AtomicFileWriterPerfTest

[batmat]

No JIRA nor changelog, trivial change. Causing recent build flakiness for no obvious reason (this test was added 1+ year ago).

Proposed changelog entries

Submitter checklist

- [ ] JIRA issue is well described

• Changelog entry appropriate for the audience affected by the change (users or developer, depending on the change). Examples
  * Use the Internal: prefix if the change has no user-visible impact (API, test frameworks, etc.)
  - [ ] Appropriate autotests or explanation to why this change has no tests
  - [ ] For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

[Wadeck]

Not sure such approach is really good for the long run.

[batmat]

Not sure such approach is really good for the long run.

I tend to agree. I guess I could just delete the test. I wanted to avoid this, but given the perf of the storage, there's probably no good way out. Or at some point introduce a profile for such flakes/things that require some normal environment. (if you check the comment around the test, you'll see that these perfs are absolutely horrible, it's like 3 times slower than an old 5400 RPM hard-disk)....

[jglick]

Please just @Ignore this test so we are not bothered with it in CI.

[batmat]

Right, so given @Wadeck and @jglick feedback, I've finally gone the @Ignore path, though I generally prefer to just delete tests in such case, but well. This test could be useful in the future for testing if someone changes AtomicFileWriter or so I suppose.

[batmat]

Given the implicit approval of @jglick (because he added that @Ignore too himself in #3799), and approvals from Ramon and Wadeck, I will likely merge this later today once the PR build is successful and if nobody objects in the meantime.

[jglick]

obsolete comment

[batmat]

Superseded by #3799