Channels
announcements
ask-marvin
best-practices-coordination-plane
data-ecosystem
data-tricks-and-tips
events
find-a-prefect-job
geo-bay-area
geo-berlin
geo-boston
geo-chicago
geo-colorado
geo-dc
geo-israel
geo-japan
geo-london
geo-nyc
geo-seattle
geo-texas
gratitude
introductions
marvin-in-the-wild
pacc-clearcover-june-12-2023
pacc-may-31-2023
ppcc-may-16-2023
prefect-ai
prefect-aws
prefect-azure
prefect-cloud
prefect-community
prefect-contributors
prefect-dbt
prefect-docker
prefect-gcp
prefect-getting-started
prefect-integrations
prefect-kubernetes
prefect-recipes
prefect-server
prefect-ui
random
show-us-what-you-got
Powered by
Title
a
ale
12/30/2021, 4:36 PM
Hey folks 😊 👋 I have these two open PRs: •
https://github.com/PrefectHQ/prefect/pull/5276
•
https://github.com/PrefectHQ/prefect/pull/5278
where some core tests fails on Windows. To me, it is not clear if they are related to the new Prefect tasks introduced by each PR… Is there someone willing to take a look to help me understand how to fix? Thanks! 🙌
z
Zanie
12/30/2021, 4:40 PM
Looks like a flaky test on the first one
And the second as well
You can add a flaky marker to
test_flow_dot_run_updates_the_scheduled_start_time_of_each_scheduled_run
or just ignore it
a
ale
12/30/2021, 9:03 PM
Thanks
@Zanie
🙏
4 Views
#prefect-contributors
Join Slack