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

The reportTestStart method called before the reportFixtureStart if Concurrency is enabled #4951

Closed
AlexKamaev opened this issue Apr 6, 2020 · 4 comments
Closed

The reportTestStart method called before the reportFixtureStart if Concurrency is enabled #4951

AlexKamaev opened this issue Apr 6, 2020 · 4 comments
Labels
FREQUENCY: level 1 STATE: Stale An outdated issue that will be automatically closed by the Stale bot. TYPE: enhancement The accepted proposal for future implementation.
Milestone
Planned

Comments

@AlexKamaev
Copy link
Contributor

Run the example from #4787 with concurrency enabled
@AlexKamaev AlexKamaev added this to the Planned milestone Apr 6, 2020
@AlexKamaev AlexKamaev added the TYPE: enhancement The accepted proposal for future implementation. label Apr 6, 2020
This was referenced Apr 6, 2020
Closed
Merged
@IssacH
Copy link

IssacH commented Mar 16, 2021

Hi @AlexKamaev, I encountered this issue using the latest testcafe version. I logged a bug with my test cases in testcafe repository, would you please take a look? Thanks!

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Mar 16, 2021
@Farfurix Farfurix mentioned this issue Mar 17, 2021
Closed
@Farfurix
Copy link
Contributor

@IssacH

Hello,

Yes, this is the same issue. Currently, we cannot give you any time estimates on when it can be resolved.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Mar 17, 2021
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

@github-actions github-actions bot added the STATE: Stale An outdated issue that will be automatically closed by the Stale bot. label Mar 18, 2022
@github-actions
Copy link

We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
FREQUENCY: level 1 STATE: Stale An outdated issue that will be automatically closed by the Stale bot. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Milestone
Planned
Development

No branches or pull requests
3 participants
@AlexKamaev @IssacH @Farfurix