Aneesh Bhave
Aneesh Bhave
can I work on this, once a final decision has been made?
@rustbot claim I would love to take this up. It would help to know where I should begin.
Sorry for dropping this, my exams are around the corner.
Attached the message from `cargo test`, used ``` cargo test > out.txt ``` [out.txt](https://github.com/uutils/coreutils/files/12249044/out.txt)
Note that stderr only reports compiles, module runs and test rerun message ; hence not included in the text file. 
I'm in India, which has the IST time zone. It is `UTC + 5:30` Here is a screenshot from windows settings - 
The problem may be with `chrono` getting the incorrect time for whatever reason. Would you like me to run some code that would allow us to rule `chrono` out?
I'm not familiar with the crate but I ran this code - ```rs use chrono::prelude::*; fn main() { let local = Local::now(); println!("{:?}", local); } ``` Using `chrono v0.4.26`. Output...
A little reading later, I think I understand how to test if `chrono` to `filetime` is an issue. Here is the code - ```rs use chrono::prelude::*; use filetime::FileTime; use std::time::{SystemTime,...
Executing command - ``` coreutils pr --pages=3:5 --column=3 -a -n ".\tests\fixtures\pr\column.log" > pr.txt ``` Test - `test_pr::test_with_column_across_option` Times seem to be wrong. [pr.txt](https://github.com/uutils/coreutils/files/12249575/pr.txt)