Merge pull request #16847 from smowton/smowton/admin/java-diagnostic-test-expectations

Java: Adjust test expectations for Java diagnostic severity changes

Author: smowton

java/ql/integration-tests/all-platforms/java/buildless-gradle-timeout/diagnostics.expected

@@ -1,6 +1,6 @@
 {
   "markdownMessage": "A Gradle process was aborted because it didn't write to the console for 5 seconds. Consider either lengthening the timeout if appropriate by setting CODEQL_EXTRACTOR_JAVA_BUILDLESS_CHILD_PROCESS_IDLE_TIMEOUT to a higher value or zero for no timeout, or else investigate why Gradle timed out. Java analysis will continue, but the analysis may be of reduced quality.",
-  "severity": "warning",
+  "severity": "note",
   "source": {
     "extractorName": "java",
     "id": "java/autobuilder/buildless/gradle-timed-out",
@@ -14,7 +14,7 @@
 }
 {
   "markdownMessage": "Build tool(s) should have been able to provide a recommended classpath but the attempt failed. Extraction will continue, but external dependencies will be inferred from the Java package names used. Consider troubleshooting the build tool error or using a build mode other than 'none'.",
-  "severity": "warning",
+  "severity": "note",
   "source": {
     "extractorName": "java",
     "id": "java/autobuilder/buildless/classpath-from-tool-failed",
@@ -84,7 +84,7 @@
 }
 {
   "markdownMessage": "Running the Gradle plugin `org.gradle:github-dependency-graph-gradle-plugin` failed. This means precise dependency information will be unavailable, and so dependencies will be guessed based on Java package names. Consider investigating why this plugin fails to run.",
-  "severity": "warning",
+  "severity": "note",
   "source": {
     "extractorName": "java",
     "id": "java/autobuilder/buildless/github-dependency-graph-gradle-plugin-failed",

java/ql/integration-tests/all-platforms/java/buildless-maven-timeout/diagnostics.expected

@@ -1,6 +1,6 @@
 {
   "markdownMessage": "A Maven process was aborted because it didn't write to the console for 5 seconds. Consider either lenghtening the timeout if appropriate by setting CODEQL_EXTRACTOR_JAVA_BUILDLESS_CHILD_PROCESS_IDLE_TIMEOUT to a higher value or zero for no timeout, or else investigate why Maven timed out. Java analysis will continue, but the analysis may be of reduced quality.",
-  "severity": "warning",
+  "severity": "note",
   "source": {
     "extractorName": "java",
     "id": "java/autobuilder/buildless/maven-timed-out",
@@ -14,7 +14,7 @@
 }
 {
   "markdownMessage": "Build tool(s) should have been able to provide a recommended classpath but the attempt failed. Extraction will continue, but external dependencies will be inferred from the Java package names used. Consider troubleshooting the build tool error or using a build mode other than 'none'.",
-  "severity": "warning",
+  "severity": "note",
   "source": {
     "extractorName": "java",
     "id": "java/autobuilder/buildless/classpath-from-tool-failed",
@@ -84,7 +84,7 @@
 }
 {
   "markdownMessage": "Running the Maven plugin `com.github.ferstl:depgraph-maven-plugin:4.0.2:graph` failed. This means precise dependency information will be unavailable, and so dependencies will be guessed based on Java package names. Consider investigating why this plugin fails to run.",
-  "severity": "warning",
+  "severity": "note",
   "source": {
     "extractorName": "java",
     "id": "java/autobuilder/buildless/depgraph-maven-plugin-failed",

java/ql/integration-tests/all-platforms/java/buildless-maven-tolerate-unavailable-dependency/diagnostics.expected

@@ -1,6 +1,6 @@
 {
   "markdownMessage": "At least one dependency JAR suggested by the build system could not be downloaded. This means the analysis will try to satisfy the dependency with its default choice for the required external package name, which may be the wrong version or the wrong package entirely. This may lead to partial analysis of code using this dependency. See the extraction log for full details. If the cause appears to be a temporary outage, consider retrying the analysis.",
-  "severity": "warning",
+  "severity": "note",
   "source": {
     "extractorName": "java",
     "id": "java/extractor/buildless/suggested-classpath-fetches-failed",
@@ -14,7 +14,7 @@
 }
 {
   "markdownMessage": "Buildless extraction tried and failed to fetch a jar (`https://repo1.maven.org/maven2, junit:junit:jar:9.9.9`). If a temporary network outage is likely, consider retrying the scan.",
-  "severity": "warning",
+  "severity": "note",
   "source": {
     "extractorName": "java",
     "id": "java/extractor/buildless/jar-fetch-failed",
@@ -98,7 +98,7 @@
 }
 {
   "markdownMessage": "Running the Maven plugin `com.github.ferstl:depgraph-maven-plugin:4.0.2:graph` yielded an artifact transfer exception. This means some dependency information will be unavailable, and so some dependencies will be guessed based on Java package names. Consider investigating why this plugin encountered errors retrieving dependencies.",
-  "severity": "warning",
+  "severity": "note",
   "source": {
     "extractorName": "java",
     "id": "java/autobuilder/buildless/depgraph-maven-plugin-transfer-exception",