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

[riscv64] not ok 1786 parallel/test-perf-hooks-histogram #42477

Closed
yuzibo opened this issue Mar 26, 2022 · 1 comment
Closed

[riscv64] not ok 1786 parallel/test-perf-hooks-histogram #42477

yuzibo opened this issue Mar 26, 2022 · 1 comment
Labels
wrong repo Issues that should be opened in another repository.

Comments

@yuzibo
Copy link

yuzibo commented Mar 26, 2022

Version

16.14

Platform

Linux dev 5.16.0-5-amd64 #1 SMP PREEMPT Debian 5.16.14-1 (2022-03-15) riscv64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

1.git clone git@salsa.debian.org:js-team/nodejs.git
2.apt build-dep nodejs
3.git checkout master-16.x
4.dpkg-buildpackage -b -rfakeroot -us -uc

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

No response

What do you see instead?

not ok 1786 parallel/test-perf-hooks-histogram

duration_ms: 3.251
severity: fail
exitcode: 1
stack: |-
node:internal/event_target:916
process.nextTick(() => { throw err; });
^

AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

  ok(data.count > 0)

    at MessagePort.<anonymous> (/home/vimer/git/new_nodejs/nodejs/test/parallel/test-perf-hooks-histogram.js:87:5)
    at MessagePort.<anonymous> (/home/vimer/git/new_nodejs/nodejs/test/common/index.js:385:15)
    at MessagePort.eventHandler (node:internal/event_target:926:12)
    at MessagePort.[nodejs.internal.kHybridDispatch] (node:internal/event_target:647:20)
    at MessagePort.exports.emitMessage (node:internal/per_context/messageport:23:28) {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: false,
  expected: true,
  operator: '=='
}

...

Additional information

No response

@aduh95
Copy link
Contributor

aduh95 commented Mar 26, 2022

1.git clone git@salsa.debian.org:js-team/nodejs.git

Should that be sent to their repo instead? We are not in control of salsa.debian.org/js-team/nodejs. Closing, feel free to reopen if you can reproduce with code on that repo and/or provided by an official source tarball (see https://nodejs.org/en/download/).

@aduh95 aduh95 closed this as completed Mar 26, 2022
@aduh95 aduh95 added the wrong repo Issues that should be opened in another repository. label Mar 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wrong repo Issues that should be opened in another repository.
Projects
None yet
Development

No branches or pull requests

2 participants