Skip to content

Conversation

@dsherret
Copy link
Member

@dsherret dsherret commented Jan 8, 2026

Reasons:

  1. Uses the same test infrastructure as the rest of the integration tests.
    • Runs flaky test in isolation on the CI.
    • Gets rid of duplicate logic we already have.
  2. We get reporting on failed tests.

@dsherret dsherret force-pushed the feat_node_compat_tests_ci_report branch from ef9279e to 3abaedb Compare January 8, 2026 02:24
Copy link
Member Author

Choose a reason for hiding this comment

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

Bug fix for on failure it wouldn't clear properly sometimes.

Copy link
Member Author

@dsherret dsherret Jan 8, 2026

Choose a reason for hiding this comment

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

Changed to json so we don't have to add a toml parser dependency

Copy link
Member

Choose a reason for hiding this comment

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

Makes sense

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

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

Can you please fix tools/node_compat_tests.js?

@dsherret
Copy link
Member Author

dsherret commented Jan 8, 2026

Can you please fix tools/node_compat_tests.js?

Good catch. I removed this file because we don't need it anymore.

@dsherret dsherret requested a review from bartlomieju January 8, 2026 21:15
@dsherret dsherret merged commit 30d1a95 into denoland:main Jan 9, 2026
31 of 36 checks passed
@dsherret dsherret deleted the feat_node_compat_tests_ci_report branch January 9, 2026 00:23
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