We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.42.1
open report of skipped test
There could be either 0s or nothing
0s
0 which scares a bit
0
No response
System: OS: macOS 14.3.1 CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Memory: 6.49 GB / 32.00 GB Binaries: Node: 20.9.0 - /usr/local/bin/node npm: 10.1.0 - /usr/local/bin/npm pnpm: 8.9.0 - /usr/local/bin/pnpm Languages: Bash: 3.2.57 - /bin/bash
The text was updated successfully, but these errors were encountered:
Hi! I'll work on this Can you please assign it to me?
Sorry, something went wrong.
fix: time in ms for skip test (#30078)
82804cc
Fixes #29861
Successfully merging a pull request may close this issue.
Version
1.42.1
Steps to reproduce
open report of skipped test
![Screenshot 2024-03-08 at 19 03 54](https://private-user-images.githubusercontent.com/7899764/311307592-d9724d26-9fdf-45f4-acb5-e8bca941513e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYwODYyNDUsIm5iZiI6MTcyNjA4NTk0NSwicGF0aCI6Ii83ODk5NzY0LzMxMTMwNzU5Mi1kOTcyNGQyNi05ZmRmLTQ1ZjQtYWNiNS1lOGJjYTk0MTUxM2UucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MTFUMjAxOTA1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MzYwNGFmMjcyY2Y5NDc5YWQxNjU1NjJjMTgwY2U0NGQwOTM1OGVlY2Y3MjE5MjFiOWRhNmYxMDc1Y2NjMTRlMiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.-scmpCNnbha1DhAUHK3Fy2eTnY4D8N9K1tMAx3pjLl8)
Expected behavior
There could be either
0s
or nothingActual behavior
0
which scares a bitAdditional context
No response
Environment
The text was updated successfully, but these errors were encountered: