Quarantined test: BundlesScopedCssFiles_UpdatesBundleWhenContentsChange

[SteveSandersonMS]

It's failing on Helix even though it passes locally and in other CI environments:

https://dev.azure.com/dnceng/public/_build/results?buildId=802210&view=ms.vss-test-web.build-test-results-tab&runId=25400452&resultId=107994&paneView=debug

[BrennanConroy]

Why isn't it marked quarantined then?

[SteveSandersonMS]

The PR that quarantines it isn’t yet merged.

[javiercn]

@BrennanConroy Is there anything wrong here?

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[captainsafia]

@javiercn I think we can improve the way the test is written here. The issue happens when we check to see that the last-modified timestamp of the compiled CSS does not change if the file contents haven't (ref). The way we determine the timestamps results in a millisecond variance in the test environment which causes the check to fail. We should either (1) read the timestamp from the file directly or (2) update the test to account for millisecond variance in last modified datetime.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.