DO NOT MERGE: fail tests on purpose

[guidopetri]

What type of PR is this?

• Refactor
• Feature
• Bug Fix
• New Query Runner (Data Source)
• New Alert Destination
• Other

Description

Test PR, do not merge.

How is this tested?

• Unit tests (pytest, jest)
• E2E Tests (Cypress)
• Manually
• N/A

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

[guidopetri]

As expected, the unit tests that should have failed passed. @AndrewChubatiuk @justinclift this is a problem, since it essentially means our CI is broken.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (320fddf) 63.41% compared to head (42e93ad) 63.41%.

❗ Current head 42e93ad differs from pull request most recent head c2cbd47. Consider uploading reports for the commit c2cbd47 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #6746   +/-   ##
=======================================
  Coverage   63.41%   63.41%           
=======================================
  Files         162      162           
  Lines       13169    13169           
  Branches     1819     1819           
=======================================
  Hits         8351     8351           
  Misses       4522     4522           
  Partials      296      296           

[justinclift]

Uh uh, that's not good. Any idea when it started?

[guidopetri]

I'm pretty sure it was the pull request target PR.

[AndrewChubatiuk]

@guidopetri updated checkout ref here

[guidopetri]

Closing as the tests (correctly) fail now.