-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
NET6 - Wrong DateTime.ToString() formating when using monoVM and linux-arm #61598
Milestone
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
dotnet-issue-labeler
bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Nov 15, 2021
michaldobrodenka
changed the title
NET6 - Wrong millisecond time formating when using monoVM
NET6 - Wrong DateTime.ToString() formating when using monoVM
Nov 15, 2021
lewing
added
area-CoreLib-mono
and removed
untriaged
New issue has not been triaged by the area owner
labels
Nov 15, 2021
michaldobrodenka
changed the title
NET6 - Wrong DateTime.ToString() formating when using monoVM
NET6 - Wrong DateTime.ToString() formating when using monoVM and linux-arm
Nov 15, 2021
.... the formatting code is unlikely to be in a runtime-dependent section. If you completely clean your build directories, does the issue persist? |
Yes, I've retested it, deleted all the bin/obj and publish folders. |
so
|
monoVM linux-x64 tested on WSL - also ok |
ghost
added
the
in-pr
There is an active PR which will close this issue when it is merged
label
Dec 2, 2021
ghost
removed
the
in-pr
There is an active PR which will close this issue when it is merged
label
Dec 9, 2021
directhex
added a commit
to directhex/runtime
that referenced
this issue
Dec 9, 2021
So... there's no case where we don't want to assume hard float Fixes: dotnet#61598 Fixes: dotnet#61599
ghost
added
the
in-pr
There is an active PR which will close this issue when it is merged
label
Dec 9, 2021
ghost
removed
the
in-pr
There is an active PR which will close this issue when it is merged
label
Jan 24, 2022
ghost
locked as resolved and limited conversation to collaborators
Feb 24, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
DateTime.Now.ToString("yyyy-MM-dd HH:mm:ss.fff") - returns
2021-11-15 14:54:33.3378046
-when app is published with-p:UseMonoRuntime=true
.When using default runtime (without
-p:UseMonoRuntime=true
) it returns2021-11-15 15:58:30.675
Reproduction Steps
I was testing minimum possible delay with following program:
compiled with
dotnet publish -r linux-arm -p:PublishTrimmed=True -p:TrimMode=Link --self-contained true -c Release -f net6.0 -o bin\dotnet\mono -p:UseMonoRuntime=true
for mono VMand
dotnet publish -r linux-arm -p:PublishTrimmed=True -p:TrimMode=Link --self-contained true -c Release -f net6.0 -o bin\dotnet
for default runtime
Expected behavior
fff
in DateTime.ToString() should return 1/1000ths of secondActual behavior
fff
in DateTime.ToString() return 1/10 000 000 of secondin screenshot - first with mono, then with dotnet default
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
Tested on 32bit linux-arm on Yocto linux
The text was updated successfully, but these errors were encountered: