Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Win32] Test Suite Failing on Windows CI #151

Closed
FredKSchott opened this issue Jan 14, 2020 · 8 comments
Closed

[Win32] Test Suite Failing on Windows CI #151

FredKSchott opened this issue Jan 14, 2020 · 8 comments
Labels
bug Something isn't working contributors welcome! contributors welcome! good first issue Good for newcomers

Comments

@FredKSchott
Copy link
Owner

Original Discussion: https://www.pika.dev/npm/snowpack/discuss/43
/cc @crra

@crra found an interesting bug on Windows, where --optimize (it looks like tree-shaking, specifically) throws an error due to a badly formatted import URL.

I do all my development on a mac, so we need to add Windows to our CI via GitHub Actions in some way. If anyone knows GitHub Actions well, I would love some help on this one.

(Okay to add the Windows CI tests even if they are failing, as long as it doesn't block merging PRs.)

@FredKSchott FredKSchott added the contributors welcome! contributors welcome! label Jan 14, 2020
@FredKSchott FredKSchott changed the title Add Windows to Test Suite Add Windows CI to GitHub Actions Jan 14, 2020
@theashraf
Copy link
Contributor

I'd like to help with this one

@FredKSchott
Copy link
Owner Author

@theashraf that would be great! I believe GH supports this out of the box. Let me know if you need contributor access to the repo to work on it.

@FredKSchott
Copy link
Owner Author

Update: We merged #156 into win-support branch, and are now seeing failing tests (due to bugs in code). Would love any help debugging these issues, and creating PRs with fixes against that branch!

Example: https://github.com/pikapkg/snowpack/runs/392311458

@FredKSchott FredKSchott changed the title Add Windows CI to GitHub Actions Win32: Test Suite Failing on Windows CI Jan 17, 2020
@FredKSchott FredKSchott added bug Something isn't working good first issue Good for newcomers contributors welcome! contributors welcome! labels Jan 17, 2020
@FredKSchott FredKSchott changed the title Win32: Test Suite Failing on Windows CI [Win32] Test Suite Failing on Windows CI Jan 17, 2020
@yukukotani
Copy link
Contributor

yukukotani commented Jan 20, 2020

Failing tests seems to be a bug of npm cli. npm ci ignores os field so it trys to build fsevents on Windows.

Related issues: fsevents/fsevents#301, npm/cli#558

I'll keep watching this issue.

@FredKSchott
Copy link
Owner Author

I see this error in the CI logs:

jest-haste-map: Haste module naming collision: snowpack
  The following files share their name; please adjust your hasteImpl:
    * <rootDir>\package.json
    * <rootDir>\pkg\package.json

Maybe there's something there that we can track down? That doesn't seem fsevents related, but idk for sure

@yukukotani
Copy link
Contributor

yukukotani commented Jan 22, 2020

@FredKSchott
That warn occurred when running test after build. But it's not the cause of build failing.
In my local machine, it occurred but test succeed.

~/g/g/p/snowpack ❯❯❯ npm test                                                                                             win-support

> snowpack@1.0.5 test /Users/yukukotani/ghq/github.com/pikapkg/snowpack
> jest __tests__/runner.js

jest-haste-map: Haste module naming collision: snowpack
  The following files share their name; please adjust your hasteImpl:
    * <rootDir>/package.json
    * <rootDir>/pkg/package.json

 PASS  __tests__/runner.js (9.192s)
  ✓ dep-list-complex (1022ms)
  ✓ dep-list-simple (823ms)
  ✓ error-empty-dep-list (647ms)
  ✓ error-missing-dep (643ms)
  ✓ error-missing-nodemodules (645ms)
  ✓ error-no-dep-list (646ms)
  ✓ exclude (1282ms)
  ✓ include (1423ms)
  ✓ include-with-import-map (1428ms)

Test Suites: 1 passed, 1 total
Tests:       9 passed, 9 total
Snapshots:   0 total
Time:        9.926s
Ran all test suites matching /__tests__\/runner.js/i.

This warning would be fixed in #171.

@FredKSchott
Copy link
Owner Author

FredKSchott commented Jan 23, 2020

Oh interesting, that's so weird that it's failing but not giving us any output. I don't know what could be causing that (my comment in #171 may not be right, then)

@FredKSchott
Copy link
Owner Author

Fixed in #164

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working contributors welcome! contributors welcome! good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants