Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

`serialport` fails in `win11-vs2022_clang-arm64`

Aperta Adatta ai principianti
  • Qualcosa non va?
#1,220 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@MikeMcC399 ci sta già lavorando.

Dal 28/10/2026.

  • #1221 di @MikeMcC399 — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
62/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, node.js
Ambito
ci-cd, testing

Direzione di ricerca

Inizia leggendo la voce serialport in lookup.json e il codice che applica skip a platform/arch, per vedere come verrebbe espresso uno skip per Windows arm64. Conferma che la build che fallisce è il passo node-gyp di @parcel/watcher che invoca llvm-lib.exe, che lo skip serve a evitare anziché correggere. Fatto significa che citgm non esegue più serialport su win11 arm64 mentre continua a eseguirlo altrove, verificato rispetto alla corrispondenza della piattaforma dello smoker.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Situation

serialport fails in citgm-smoker running under win11-vs2022_clang-arm64 in Jenkins. Logs under https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3805/nodes=win11-vs2022_clang-arm64/testReport/junit/(root)/citgm/serialport_v13_0_0/ (collaborator access only).

This is also reproducible in the GitHub Actions runner windows-11-vs2026-arm runner for Node.js versions 22, 24 & 26.

windows-11-vs2026-arm includes Visual Studio Enterprise 2026 with Clang.

Item Status
npm package https://www.npmjs.com/package/serialport
npm status not deprecated
last published 13.0.0 Dec 24, 2024
weekly downloads 220,500
repo location https://github.com/serialport/node-serialport
repo last update to default branch Jan 2, 2026
repo status quiet
repo CI status runs in Node.js 18 - 22 (macos- ubuntu- windows-latest)
lookup version / HEAD HEAD
lookup - skip ppc 390x
lookup maintainer 1 reconbot

lookup.json settings are:

  "serialport": {
    "skip": ["ppc", "s390x"],
    "head": true,
    "tags": "native",
    "maintainers": "reconbot"
  },

Logs

 npm error code 1
 npm error path C:\Users\lhymbtjceacp\AppData\Local\Temp\3454ddb9\serialport\node_modules\@parcel\watcher
 npm error command failed
 npm error command C:\Windows\system32\cmd.exe /d /s /c node-gyp-build
 npm error /LTCG:INCREMENTAL: no such file or directory
 npm error C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(1647,5): error MSB6006: "llvm-lib.exe" exited with code 1. [C:\Users\lhymbtjceacp\AppData\Local\Temp\3454ddb9\serialport\node_modules\@parcel\watcher\build\node_modules\node-addon-api\nothing.vcxproj]
 npm error (node:8452) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
 npm error (Use `node --trace-deprecation ...` to show where the warning was created)
 npm error (node:8452) [DEP0190] DeprecationWarning: Passing args to a child process with shell option true can lead to security vulnerabilities, as the arguments are not escaped, only concatenated.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard_C while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard_C while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard_C while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard while converting to MSBuild.
 npm error Warning: unrecognized setting VCCLCompilerTool/LanguageStandard_C while converting to MSBuild.
 npm error gyp ERR! build error
 npm error gyp ERR! stack Error: `C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\arm64\MSBuild.exe` failed with exit code: 1
 npm error gyp ERR! stack     at ChildProcess.onExit (C:\Users\lhymbtjceacp\AppData\Local\Temp\3454ddb9\serialport\node_modules\node-gyp\lib\build.js:203:23)
 npm error gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
 npm error gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:324:12)
 npm error gyp ERR! System Windows_NT 10.0.22621
 npm error gyp ERR! command "d:\\workspace\\citgm-smoker\\node\\Release\\node.exe" "C:\\Users\\lhymbtjceacp\\AppData\\Local\\Temp\\3454ddb9\\serialport\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
 npm error gyp ERR! cwd C:\Users\lhymbtjceacp\AppData\Local\Temp\3454ddb9\serialport\node_modules\@parcel\watcher
 npm error gyp ERR! node -v v24.22.2
 npm error gyp ERR! node-gyp -v v9.4.1
 npm error gyp ERR! not ok
 npm error A complete log of this run can be found in: d:\workspace\citgm-smoker\node\Release\npm-cache\_logs\2026-10-27T02_26_58_372Z-debug-0.log

Suggestion

  • Check with @reconbot if there are plans to extend support in serialport to Windows arm64. GitHub Actions now supports a full set of arm64 runner images for Ubuntu & Windows (macOS was already arm64), so a test / CI environment would be available.
  • Encourage also GitHub Actions CI update in serialport > test.yml to test against currently supported Node.js versions 24 & 26.
  • In the meantime, skip serialport testing in citgm on Windows arm64

Related

https://serialport.io/docs/next/guide-platform-support

https://github.com/nodejs/citgm/issues/991#issuecomment-1742192125

i only officially support max Linux and windows on x64, arm is a very popular usecase but I don't have an easy way to test it.

https://github.com/serialport/node-serialport/issues/3149

Lingua principale
JavaScript
Stelle
608
Fork
163
Merge medio
2g 19h
PR unite (30g)
20

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nodejs/citgm

Tutte le issue di nodejs/citgm

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.