Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[CT-2335] [Follow-up] Inspect why the length of Agate table in results is wrong in tests #7234

Closed
aranke opened this issue Mar 28, 2023 · 3 comments
Closed

[CT-2335] [Follow-up] Inspect why the length of Agate table in results is wrong in tests #7234

aranke opened this issue Mar 28, 2023 · 3 comments
Assignees
@aranke
Labels
tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality

Comments

@aranke
Copy link
Member

aranke commented Mar 28, 2023 •
edited by dbeatty10
Loading

Follow-up from #7208

See comment here: #7208 (comment)

See examples of some removed flaky tests: e20af84
@aranke aranke added bug Something isn't working triage labels Mar 28, 2023
@github-actions github-actions bot changed the title [Bug] Inspect why the length of Agate table in results is wrong in tests [CT-2335] [Bug] Inspect why the length of Agate table in results is wrong in tests Mar 28, 2023
@aranke aranke mentioned this issue Mar 28, 2023
Merged
6 tasks
@dbeatty10 dbeatty10 removed the triage label Mar 28, 2023
@jtcohen6 jtcohen6 added tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality Team:Execution and removed bug Something isn't working labels Apr 14, 2023
@jtcohen6 jtcohen6 changed the title [CT-2335] [Bug] Inspect why the length of Agate table in results is wrong in tests [CT-2335] [Follow-up] Inspect why the length of Agate table in results is wrong in tests Apr 14, 2023
@iknox-fa
Copy link
Contributor

Per BLG -- assigned to @aranke to check if that was fixed by other work.

@peterallenwebb
Copy link
Contributor

@aranke Fixed?

@aranke
Copy link
Member Author

aranke commented Nov 6, 2023

I wasn't able to reproduce this issue, don't think it's worth investigating further.

If it re-occurs, we can re-open this ticket.

@aranke aranke closed this as not planned Won't fix, can't repro, duplicate, stale Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aranke aranke

Labels
tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@peterallenwebb @jtcohen6 @dbeatty10 @aranke @iknox-fa