Skip to content

Fix evergreen-validate failures in CI#966

Merged
autarch merged 1 commit intomasterfrom
03-27-fix_evergreen-validate_failures_in_ci
Mar 27, 2026
Merged

Fix evergreen-validate failures in CI#966
autarch merged 1 commit intomasterfrom
03-27-fix_evergreen-validate_failures_in_ci

Conversation

@autarch
Copy link
Copy Markdown
Collaborator

@autarch autarch commented Mar 27, 2026

This also rewrites the code that ignores certain warnings to be a bit clearer.

@autarch autarch requested a review from a team as a code owner March 27, 2026 18:42
@autarch autarch requested review from mankawal and mmcclimon and removed request for a team March 27, 2026 18:42
Copy link
Copy Markdown
Collaborator Author

autarch commented Mar 27, 2026

This stack of pull requests is managed by Graphite. Learn more about stacking.

This was referenced Mar 27, 2026
Comment on lines +411 to +414
strings.HasSuffix(line, "but allowed_requesters is always higher precedence") ||
strings.HasSuffix(
line,
"defined but not used by any variants; consider using or disabling",
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The real change is adding these two things to the ignore list and removing the "already set in map" check, because that is no longer a warning we see.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[narrator] But he did not, in fact, remove the "already set in map" check.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now I did. I also removed most of the other checks, because we're no longer getting them. It's just the unused variants one.

Copy link
Copy Markdown
Contributor

@mmcclimon mmcclimon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would tweak a couple things here but trust you to make these changes; I don't need to review this again unless you just really want me to, thanks!

if strings.HasPrefix(line, "WARNING: ") {
if strings.HasSuffix(line, "unmarshal errors:") ||
strings.HasSuffix(line, "already set in map") ||
strings.HasSuffix(line, "but allowed_requesters is always higher precedence") ||
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a better fix here would just be to fix the task definition (I meant to do this the other day and then got sidetracked and forgot). The fix is just in the run_manual_generated_tasks task:

diff --git a/mongodump_passthrough/tasks.yml b/mongodump_passthrough/tasks.yml
index e6ea4fde..722f258a 100644
--- a/mongodump_passthrough/tasks.yml
+++ b/mongodump_passthrough/tasks.yml
@@ -70,7 +70,7 @@ tasks:
         params:
           files:
             - src/github.com/mongodb/mongo-tools/manual-tasks.json
-    patch_only: true
+    allowed_requesters: ["patch"]

   # Task dependencies have been changed slightly here, to allow this
   # task to execute concurrently with "compile_coverage".

(And then with that, we don't need this suffix check.)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

Comment on lines +411 to +414
strings.HasSuffix(line, "but allowed_requesters is always higher precedence") ||
strings.HasSuffix(
line,
"defined but not used by any variants; consider using or disabling",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[narrator] But he did not, in fact, remove the "already set in map" check.

This also rewrites the code that ignores certain warnings to be a bit clearer.
@autarch autarch force-pushed the 03-27-fix_evergreen-validate_failures_in_ci branch from 377221a to f911d77 Compare March 27, 2026 20:36
Copy link
Copy Markdown
Collaborator Author

autarch commented Mar 27, 2026

Merge activity

  • Mar 27, 9:14 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Mar 27, 9:15 PM UTC: @autarch merged this pull request with Graphite.

@autarch autarch merged commit 0bbfb8f into master Mar 27, 2026
38 of 39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants