{"action":"created","issue":{"url":"https://api.github.com/repos/eddelbuettel/anytime/issues/84","repository_url":"https://api.github.com/repos/eddelbuettel/anytime","labels_url":"https://api.github.com/repos/eddelbuettel/anytime/issues/84/labels{/name}","comments_url":"https://api.github.com/repos/eddelbuettel/anytime/issues/84/comments","events_url":"https://api.github.com/repos/eddelbuettel/anytime/issues/84/events","html_url":"https://github.com/eddelbuettel/anytime/issues/84","id":385557949,"node_id":"MDU6SXNzdWUzODU1NTc5NDk=","number":84,"title":"anytime() behaves differently on Fedora","user":{"login":"earowang","id":2456216,"node_id":"MDQ6VXNlcjI0NTYyMTY=","avatar_url":"https://avatars0.githubusercontent.com/u/2456216?v=4","gravatar_id":"","url":"https://api.github.com/users/earowang","html_url":"https://github.com/earowang","followers_url":"https://api.github.com/users/earowang/followers","following_url":"https://api.github.com/users/earowang/following{/other_user}","gists_url":"https://api.github.com/users/earowang/gists{/gist_id}","starred_url":"https://api.github.com/users/earowang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/earowang/subscriptions","organizations_url":"https://api.github.com/users/earowang/orgs","repos_url":"https://api.github.com/users/earowang/repos","events_url":"https://api.github.com/users/earowang/events{/privacy}","received_events_url":"https://api.github.com/users/earowang/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-29T03:48:11Z","updated_at":"2018-11-29T03:55:03Z","closed_at":null,"author_association":"NONE","body":"Hi Dirk,\r\n\r\nI've been notified that [some unit tests in the **tsibble** package failed on platform `fedora-clang-devel`](https://cran.r-project.org/web/checks/check_results_tsibble.html). It seems to be related to `anytime()`.\r\n\r\nThe following lines return `\"2018-10-01 UTC\"` on macOS and ubuntu (systems that I have tested locally), which is as expected. But they all give `2018-10-01 01:00:00 UTC` on fedora instead. \r\n\r\n```r\r\nanytime::utctime(\"2018-10\", tz = \"UTC\")\r\nanytime::utctime(\"2018-10-01\", tz = \"UTC\")\r\nanytime::utctime(\"2018-10-01 00\", tz = \"UTC\")\r\nanytime::utctime(\"2018-10-01 00:00\", tz = \"UTC\")\r\nanytime::utctime(\"2018-10-01 00:00:00\", tz = \"UTC\")\r\n```\r\n\r\nI don't have access to fedora, so it's hard to reproduce and backtrace the error. I've created a tiny repo/package [here](https://github.com/earowang/anytimetest) and tested it using `rhub::check_on_fedora()`. All the lines above failed.\r\n\r\n```\r\n* checking tests ...\r\n  Running ‘testthat.R’\r\n ERROR\r\nRunning the tests in ‘tests/testthat.R’ failed.\r\nLast 13 lines of output:\r\n  ── 5. Failure: utctime2 (@test-utctime.R#10)  ──────────────────────────────────\r\n  anytime::utctime(\"2018-10-01 00:00:00\", tz = \"UTC\") not identical to `y`.\r\n  1/1 mismatches\r\n  [1] 2018-10-01 01:00:00 - 2018-10-01 == 1 hours\r\n  \r\n  ══ testthat results  ═══════════════════════════════════════════════════════════\r\n  OK: 0 SKIPPED: 0 FAILED: 5\r\n  1. Failure: utctime2 (@test-utctime.R#6) \r\n  2. Failure: utctime2 (@test-utctime.R#7) \r\n  3. Failure: utctime2 (@test-utctime.R#8) \r\n  4. Failure: utctime2 (@test-utctime.R#9) \r\n  5. Failure: utctime2 (@test-utctime.R#10) \r\n  \r\n  Error: testthat unit tests failed\r\n  Execution halted\r\n```\r\n\r\nThanks."},"comment":{"url":"https://api.github.com/repos/eddelbuettel/anytime/issues/comments/442697508","html_url":"https://github.com/eddelbuettel/anytime/issues/84#issuecomment-442697508","issue_url":"https://api.github.com/repos/eddelbuettel/anytime/issues/84","id":442697508,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MjY5NzUwOA==","user":{"login":"eddelbuettel","id":673121,"node_id":"MDQ6VXNlcjY3MzEyMQ==","avatar_url":"https://avatars1.githubusercontent.com/u/673121?v=4","gravatar_id":"","url":"https://api.github.com/users/eddelbuettel","html_url":"https://github.com/eddelbuettel","followers_url":"https://api.github.com/users/eddelbuettel/followers","following_url":"https://api.github.com/users/eddelbuettel/following{/other_user}","gists_url":"https://api.github.com/users/eddelbuettel/gists{/gist_id}","starred_url":"https://api.github.com/users/eddelbuettel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eddelbuettel/subscriptions","organizations_url":"https://api.github.com/users/eddelbuettel/orgs","repos_url":"https://api.github.com/users/eddelbuettel/repos","events_url":"https://api.github.com/users/eddelbuettel/events{/privacy}","received_events_url":"https://api.github.com/users/eddelbuettel/received_events","type":"User","site_admin":false},"created_at":"2018-11-29T03:55:03Z","updated_at":"2018-11-29T03:55:03Z","author_association":"OWNER","body":"Ewwww. That looks bad ... for Boost.\r\n\r\nI would, in the narrow sense, try to avoid the test to avoid the error at CRAN.  That is _clearly_ a parser bug hence an issue with the Boost version.  Do we know / can we know i) what the Fedora version is and ii) what the Boost version is?  We may be able to coax your test package to tell us.  \r\n\r\nTry adding `useR=TRUE` just to \"prove\" it's Boost.  By setting that flag we use the R parser (which I export via package `RApiDatetime`)."}}
{"actor":{"display_login":"eddelbuettel"}}