-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Java: convert remaining java-code-scanning.qls
query tests to .qlref
#19842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
3b874a0
to
4a835f9
Compare
Also, split off into separate directory from JndiInjectionTest because their $Alerts were interfering with each other.
Leaves ReDoS.ql unmodified since it's not a dataflow query; just moves it to its own directory.
It's a non-path query, so the InlineExpectationsTest postprocessor doesn't do anything.
This fixes the failing diff-informed consistency check.
This is because it was failing the diff-informed consistency check, and like other ReDoS queries (Python?) the query tries to be helpful by showing a substring of a regex, which has a `hasLocation(...)` (intensional) but no corresponding `getLocation()` (extensional). Until the location overrides get updated to support `hasLocation`-based locations, it's probably best to turn off diff-informed support.
4a835f9
to
a49999d
Compare
...ql/test/query-tests/security/CWE-312/CleartextStorageCookie/CleartextStorageCookieTest.qlref
Fixed
Show fixed
Hide fixed
Given that it's a non-path-problem dataflow query, the InlineExpectationsTest is not as useful.
d6f8ec3
to
6904461
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Woah, what about CI? |
There was a failing check, which I just retried, so that's still running? |
Yikes, sorry I missed that. Can I revert this somehow? |
It was the QLDoc Checks, so I think it's unlikely to break main, and possibly could have been a spurious failure (hence why I retried it), but we should keep an eye on it - if the retry succeeds then all is well, otherwise we need to understand the failure and whether it's something that affects main. |
Looks like the retry succeeded, so all looks well. |
Example prior work: #18848 #19817
utils/test/InlineExpectationsTestQuery.ql
-based ones, similar to the above PRs.--check-diff-informed
) runs on .qlref-based tests, the UnsafeDeserialization and PolynomialReDoS tests were newly failing that check.getASelectedSinkLocation
override.