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

Investigate APITest_AsynchronousTest #37760

Open
sf1919 opened this issue Aug 7, 2024 · 2 comments · May be fixed by #38689
Open

Investigate APITest_AsynchronousTest #37760

sf1919 opened this issue Aug 7, 2024 · 2 comments · May be fixed by #38689
Assignees
@jclarkeSTFC
Labels
ISIS Team: Core Issue and pull requests managed by the Core subteam at ISIS Maintenance Unassigned issues to be addressed in the next maintenance period.

Comments

@sf1919
Copy link
Contributor

sf1919 commented Aug 7, 2024

Describe the outcome that is desired.
This has proved an unreliable test recently on both PRs and the nightly pipeline. The desired outcome is to review the test to see if it can be improved to make it more stable.

Describe any solutions you are considering
Understand what the test is doing and why it is failing on asserts.

Additional context
Relevant console log from Linux nightly build

00:38:01  1645/2723 Test  #490: APITest_AsynchronousTest .....................................................................................................................***Failed    4.92 sec
00:38:01  FrameworkManager-[Notice] Welcome to Mantid 6.10.20240724.1558.dev135
00:38:01  FrameworkManager-[Notice] Please cite: http://dx.doi.org/10.1016/j.nima.2014.07.029 and this release: http://dx.doi.org/10.5286/Software/Mantid
00:38:01  Running 6 testsAsyncAlgorithm-[Notice] AsyncAlgorithm started
00:38:01  AsyncAlgorithm-[Notice] AsyncAlgorithm successful, Duration 0.02 seconds
00:38:01  
00:38:01  16AsynchronousTest
00:38:01  In AsynchronousTest::testExecution:
00:38:01  /jenkins_workdir/workspace/main_nightly_deployment/source/Framework/API/test/AsynchronousTest.h:101: Error: Assertion failed: !result.available()
00:38:01  AsyncAlgorithm-[Notice] AsyncAlgorithm started
00:38:01  AsyncAlgorithm-[Warning] AsyncAlgorithm: Execution cancelled by user.
00:38:01  .AsyncAlgorithmThrows-[Notice] AsyncAlgorithmThrows started
00:38:01  AsyncAlgorithmThrows-[Error] Error in execution of algorithm AsyncAlgorithmThrows:
00:38:01  AsyncAlgorithmThrows-[Error] Exception thrown
00:38:01  .AsyncAlgorithm-[Notice] AsyncAlgorithm started
00:38:01  AsyncAlgorithm-[Notice] AsyncAlgorithm started (child)
00:38:01  AsyncAlgorithm-[Notice] AsyncAlgorithm successful, Duration 0.01 seconds
00:38:01  AsyncAlgorithm-[Notice] AsyncAlgorithm started (child)
00:38:01  AsyncAlgorithm-[Notice] AsyncAlgorithm successful, Duration 0.01 seconds
00:38:01  AsyncAlgorithm-[Notice] AsyncAlgorithm successful, Duration 0.02 seconds. Processed as a workspace group
00:38:01  .AsyncAlgorithm-[Notice] AsyncAlgorithm started
00:38:01  AsyncAlgorithm-[Notice] AsyncAlgorithm started (child)
00:38:01  AsyncAlgorithm-[Warning] AsyncAlgorithm: Execution cancelled by user.
00:38:01  .AsyncAlgorithmThrows-[Notice] AsyncAlgorithmThrows started
00:38:01  AsyncAlgorithmThrows-[Notice] AsyncAlgorithmThrows started (child)
00:38:01  AsyncAlgorithmThrows-[Error] Error in execution of algorithm AsyncAlgorithmThrows:
00:38:01  AsyncAlgorithmThrows-[Error] Exception thrown
00:38:01  .
00:38:01  Failed 1 of 6 tests
00:38:01  Success rate: 83%
00:38:01
@sf1919 sf1919 added Maintenance Unassigned issues to be addressed in the next maintenance period. ISIS Team: Core Issue and pull requests managed by the Core subteam at ISIS labels Aug 7, 2024
@sf1919 sf1919 added this to ISIS Core Aug 7, 2024
@sf1919 sf1919 moved this from Icebox to Backlog in Mantid Maintenance Sep 12, 2024
@jclarkeSTFC
Copy link
Contributor

It would be good to see more examples of this happening, because I can't reproduce it on my local Linux

@peterfpeterson
Copy link
Member

Maybe this can be made a little easier to explore using ctest --repeat-until-fail <n> ....

@jclarkeSTFC jclarkeSTFC linked a pull request Jan 24, 2025 that will close this issue
Open
@jclarkeSTFC jclarkeSTFC moved this from Assigned to In progress in Mantid Maintenance Jan 24, 2025
@sf1919 sf1919 moved this from In progress to Ready for Review in Mantid Maintenance Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jclarkeSTFC jclarkeSTFC

Labels
ISIS Team: Core Issue and pull requests managed by the Core subteam at ISIS Maintenance Unassigned issues to be addressed in the next maintenance period.
Projects
ISIS Core
Status: No status
Mantid Maintenance
Status: Ready for Review
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Increase sleep in test algorithm mantidproject/mantid
3 participants
@peterfpeterson @sf1919 @jclarkeSTFC