-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
GH-37950: [R] tests fail on R < 4.0 due to test calling data.frame() without specifying stringsAsFactors=FALSE #37951
Conversation
@github-actions crossbow submit test-r-versions |
Revision: 84582a7 Submitted crossbow builds: ursacomputing/crossbow @ actions-75059b6651
|
After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit 1415598. There were 9 benchmark results indicating a performance regression:
The full Conbench report has more details. It also includes information about possible false positives for unstable benchmarks that are known to sometimes produce them. |
…ame() without specifying stringsAsFactors=FALSE (apache#37951) ### Rationale for this change Tests failing on R < 4.0 builds due to the default value of the the `data.frame()` parameter `stringsAsFactors` between older and newer versions of R ### What changes are included in this PR? Update a test using `data.frame()` to manually specify the value of `stringsAsFactors` as `FALSE`. ### Are these changes tested? No ### Are there any user-facing changes? No * Closes: apache#37950 Authored-by: Nic Crane <thisisnic@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>
…ame() without specifying stringsAsFactors=FALSE (apache#37951) ### Rationale for this change Tests failing on R < 4.0 builds due to the default value of the the `data.frame()` parameter `stringsAsFactors` between older and newer versions of R ### What changes are included in this PR? Update a test using `data.frame()` to manually specify the value of `stringsAsFactors` as `FALSE`. ### Are these changes tested? No ### Are there any user-facing changes? No * Closes: apache#37950 Authored-by: Nic Crane <thisisnic@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>
…ame() without specifying stringsAsFactors=FALSE (apache#37951) ### Rationale for this change Tests failing on R < 4.0 builds due to the default value of the the `data.frame()` parameter `stringsAsFactors` between older and newer versions of R ### What changes are included in this PR? Update a test using `data.frame()` to manually specify the value of `stringsAsFactors` as `FALSE`. ### Are these changes tested? No ### Are there any user-facing changes? No * Closes: apache#37950 Authored-by: Nic Crane <thisisnic@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>
…ame() without specifying stringsAsFactors=FALSE (apache#37951) ### Rationale for this change Tests failing on R < 4.0 builds due to the default value of the the `data.frame()` parameter `stringsAsFactors` between older and newer versions of R ### What changes are included in this PR? Update a test using `data.frame()` to manually specify the value of `stringsAsFactors` as `FALSE`. ### Are these changes tested? No ### Are there any user-facing changes? No * Closes: apache#37950 Authored-by: Nic Crane <thisisnic@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>
Rationale for this change
Tests failing on R < 4.0 builds due to the default value of the the
data.frame()
parameterstringsAsFactors
between older and newer versions of RWhat changes are included in this PR?
Update a test using
data.frame()
to manually specify the value ofstringsAsFactors
asFALSE
.Are these changes tested?
No
Are there any user-facing changes?
No
data.frame()
without specifyingstringsAsFactors=FALSE
#37950