[BUG] OrcReader benchmark failure

[karthikeyann]

Describe the bug
ORC_READER_BENCH crashes with

 terminate called after throwing an instance of 'cudf::logic_error'
   what():  cuDF failure at: /home/karthikeyan/3cudf/cpp/benchmarks/io/orc/orc_reader.cpp:145: Benchmark did not read the entire table

Steps/Code to reproduce bug
./benchmarks/ORC_READER_BENCH --benchmark_filter=OrcRead/row_selection/0/4/1/3/0

or
Run all OrcRead/row_selection benchmarks.
time ./benchmarks/ORC_READER_BENCH --benchmark_filter=row_selection

Additional context
Discovered while working on #10109

[GregoryKimball]

Looks like a duplicate of #9961

[github-actions]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

[github-actions]

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

[karthikeyann]

Still relevant. The issue is not fixed. The benchmark arg is disabled in #10194
#9963 (comment)

cudf/cpp/benchmarks/io/parquet/parquet_reader.cpp

Lines 187 to 188 in c01a2a4

	// row_selection::ROW_GROUPS disabled until we add an API to read metadata from a parquet file and
	// determine num row groups. https://github.com/rapidsai/cudf/pull/9963#issuecomment-1004832863

[github-actions]

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

[GregoryKimball]

Closing in favor of #11675

[GregoryKimball]

@karthikeyann Did I make a mistake here? It seems like we should probably re-open this.

[vyasr]

I'll reopen for now so that we don't lose track. @karthikeyann feel free to close again if the closing was correct, but I agree that it seems unrelated to the linked issue.

[vyasr]

Looking back, I think this was indeed closed for the wrong reasons, but it can be closed. This issue is no longer relevant after #11611 and #11543