I think the failed test on logged error might actually be correct here.

The test in question that is failing is calling /derp on the idp, which makes no sense. At no point should we be making that call to that endpoint.

I wonder if the unit tests are reusing ports, and it used to be a coderd, but now it's a fake IDP on that port? In which case, tests are not cleaning up correctly?

Gotcha 👍 that's fair. I thought this might be a timing issue (or something similarly flaky), but if it's indicative of something actually incorrect then absolutely we shouldn't paper over it.

Gotcha 👍 that's fair. I thought this might be a timing issue (or something similarly flaky), but if it's indicative of something actually incorrect then absolutely we shouldn't paper over it.

I haven't looked deep yet, so maybe it is timing. But I cannot think of a reason that route should be called on the IDP. If it's a test teardown thing, that sounds like a pain to debug 😢