CI: xfail failing parquet test

[jbrockmendel]

No description provided.

[WillAyd]

ok by me

[jreback]

is there an issue ref for this?

[jbrockmendel]

is there an issue ref for this?

no

[jreback]

right is this something we are controlling on pandas side? or pyarrow / fastparquet?

[jbrockmendel]

No idea cc @jorisvandenbossche ?

[jreback]

ahh i c this is failing PRs ok let'e merge and can always come back to this (@jbrockmendel if you can make an issue about this)

[simonjayhawkins]

@meeseeksdev backport 1.1.x

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

$ git checkout 1.1.x
$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 dc1c849f0cf4f1b8c5602a54f5231f6b57d1d913

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

$ git commit -am 'Backport PR #36272: CI: xfail failing parquet test'

4. Push to a named branch :

git push YOURFORK 1.1.x:auto-backport-of-pr-36272-on-1.1.x

5. Create a PR against branch 1.1.x, I would have named this PR:

"Backport PR #36272 on branch 1.1.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free to suggest an improvement.

[simonjayhawkins]

@WillAyd changing the milestone and not backporting. this test is not failing on 1.1.x

[WillAyd]

@jbrockmendel OK by you?

[jbrockmendel]

yep

[TomAugspurger]

Do we have an issue to track this? Could anyone debug if it just the test setup (moto or something?) that was causing us to return empty dataframes, or do we have an actual issue?