Skip to content

test: add a place for reproducing known bugs

Rodrigo Muino Tomonari requested to merge github/fork/cjihrig/bugs into master

Pull Request check-list

Please make sure to review and check all of these items:

  • Does make -j8 test (UNIX) or vcbuild test nosign (Windows) pass with this change (including linting)?
  • Is the commit message formatted according to [CONTRIBUTING.md][0]?
  • If this change fixes a bug (or a performance problem), is a regression test (or a benchmark) included?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.

Affected core subsystem(s)

test

Description of change

This PR is a proof of concept related to https://github.com/nodejs/testing/issues/18. The point is to create a place to track the state of current known bugs, with a single command to verify that they still exist (the issue tracker has proven to be a difficult way to manage this).

There are currently a few hundred open issues, so I only bothered to port one bug reproduction. I also need to add make test-bugs to vcbuild for Windows. If this can get in, I'll work to create more reproductions.

Merge request reports