<@U01PZK60W2F>: do you have things you need picked...
# development
w
@curved-television-6568: do you have things you need picked to
2.7.x
?
if so, definitely mark
needs-cherrypick
and/or let us know
👍 1
c
Ah, yes, marked #12758 for cherry picking, then..
Marked #12747 too, to bump the integration test timeout for docker to avoid flaky tests
👍 1
h
Oh hm @witty-crayon-22786, I'm still seeing
395.80s 	Scheduling:
showing up a lot in CI logs. Thoughts on a fix before 2.7 is stabilized? Not sure how hard it will be
w
it’s not a pants side bug… it’s related to the remote cache.
although i could imagine making a visible remote cache lookup workunit to make that more obvious.
@enough-analyst-54434: will you have time to make the deprecation change for https://github.com/pantsbuild/pants/pull/12808 this afternoon? if not, i’d be happy to to pipeline getting the next 2.7.0 rc out
e
I'm working on it.
👍 1
This was what prompted my in-progress discussion - I went to add that label an hour ago and it was gone.
w
oh, hah. then i think i misinterpreted how it was being used anyway… thought it was for issues rather than PRs
h
Thanks, John. @witty-crayon-22786 I'd like to try to land https://github.com/pantsbuild/pants/pull/12807 after and cherry-pick. Then I think I'm good
e
Stu - it is for issues. I had an issue filed already in the early am that my PR Todo linked for deprecations.
w
maybe redundant work: if so, sorry: https://github.com/pantsbuild/pants/pull/12833
e
Urg, yes.
You don't mention a non-clean pick. I assume you'rs was also non-clean?
w
it was non-clean, correct. almost entirely in lockfiles, but also related to #12734 on main. will comment.
e
Thank you. I like to have that written down when things go wrong.
👍 1
w
ok, sounds like everything bound for 2.7.x will be landed by tomorrow, so can do another rc then. not sure who is on the calendar, but if they don’t get to it first i’d be happy to.
👍 1
e
I'm calendared and happy to do it. I've been missing my share as of late.
👍 1