Skip to content

question: can I tree-factor test/parallel #706

Closed

Description

@refack

I'm asking here before opening a PR in core...
Is there some build voodoo around test/parallel? This directory currently hold 1323 files, which causes my IDE to stutter and even GitHub borks.
image

Can I tree-factor it to subdirectories by subsystem so that we'll have:

test/parallel/
|
-> arm/
|
-> assert/
|
-> async-wrap/
...

Activity

  1. gibfahn commented on Apr 30, 2017

    @gibfahn
    Member

    It's listed here: https://github.com/nodejs/node/blob/master/tools/test.py#L1559, any special casing will be done in tools/test.py.

    All our tests are currently in test/* (i.e. only one directory deep). Not sure what you mean by tree-factor, are you talking about having test/sequential/buffer/ and test/sequential/fs? If so why? There are only 40 tests in sequential, there doesn't seem to be much point to moving tests around and adding complexity. Moving things has been done in the past, but it generates a load of churn, so is normally done sparingly.

    In any case, I don't think there's anything build specific that requires that layout, but I suspect test.py probably does.

  2. changed the title [-]question: can I tree-factor `test/sequential`[/-] [+]question: can I tree-factor `test/parallel`[/+] on Apr 30, 2017
  3. refack commented on Apr 30, 2017

    @refack
    ContributorAuthor

    @gibfahn I ment test/parallel.
    Thank. I'll try a little bit and adjust test.py to make sure it works.

  4. gibfahn commented on Apr 30, 2017

    @gibfahn
    Member

    parallel will be special-cased, as tools/test.py -j4 will only run 4 at a time for the parallel test suite.

    I think breaking it up was proposed before and didn't happen, it might be having a look for previous discussions before going down that road again.

  5. refack commented on Apr 30, 2017

    @refack
    ContributorAuthor

    I can tell test.py that it's a single suite, just a two dirs deep.
    Anyway I'll try too look up the previous discussions.

  6. joaocgreis commented on May 1, 2017

    @joaocgreis
    Member
  7. maclover7 commented on Feb 13, 2018

    @maclover7
    Contributor

    I think this is an issue for nodejs/node, going to close in favor of discussion there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions