i#1807 long failures: List 8 long suite tests as flaky

[derekbruening]

Adds the following tests to the ignore list in order to keep the long
suite on master merges greener:

• win64 'common.floatpc_xl8all' x64 common.floatpc_xl8all fails non-deterministically with a truncated pc #2267
• win64 'code_api|tool.drcachesim.simple-config-file' fix failing tests in debug build long suite #1807
• lin32 'code_api,opt_speed|common.fib' fix failing tests in debug build long suite #1807
• lin32 'prof_pcs|common.nativeexec_exe_opt' ASSERT signal.c:4224 in prof_pcs nativeexec test #2052
• lin64 'code_api,opt_speed|common.floatpc_xl8all' fix failing tests in debug build long suite #1807

Only ignored in the long suite since these are tests we don't want to
completely break:

• lin32 'code_api|api.startstop' 32-bit linux.thread-reset, linux.clone-reset, api.startstop failing with usage error about vdso sysenter raw syscalls #4604
• lin64 'code_api|api.detach_state' ASSERT api.detach_state vmareas.c:8308 !ok || !TEST(MEMPROT_WRITE, prot2) || TEST(FRAG_SELFMOD_SANDBOXED, *flags) || !INTERNAL_OPTION(hw_cache_consistency) #5123
• lin64 'code_api|client.cleancallsig' fix failing tests in debug build long suite #1807

Issue: #1807, #2267, #2052, #4604, #5123

[derekbruening]

Hmm, this PR ignores lin32 api.startstop failures in the long suite only: but here in the short suite we hit #4604 again. Should we put it on the ignore list for PR's too for lin32??

[abhinav92003]

Hmm, this PR ignores lin32 api.startstop failures in the long suite only: but here in the short suite we hit #4604 again. Should we put it on the ignore list for PR's too for lin32??

As the PR description says, this is one of the important ones. So if there's flakiness in the PR suite, let's not ignore that. Better to ignore only in the long suite.

[abhinav92003]

For now, I guess just a re-run might do.

Do you have any guesses on the root-cause? If this is high priority, I can try solving it this/next week.

[derekbruening]

For now, I guess just a re-run might do.

In progress.

Do you have any guesses on the root-cause? If this is high priority, I can try solving it this/next week.

Actually for this one I reproduced on my old laptop and meant to try to debug it but never had time:
#4604 (comment)
Have not yet tried on the new one.
Sure, if you can reproduce, that would be good. #5123 is the other one I'm worried about, but I can't repro that one.