8000 Flaky timeout on SchedulerTests · Issue #8497 · intel/llvm · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Flaky timeout on SchedulerTests #8497

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.

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
Closed
aelovikov-intel opened this issue Feb 28, 2023 · 1 comment
Closed

Flaky timeout on SchedulerTests #8497

aelovikov-intel opened this issue Feb 28, 2023 · 1 comment
Labels
bug Something isn't working confirmed

Comments

@aelovikov-intel
Copy link
Contributor
aelovikov-intel commented Feb 28, 2023 •
edited by bader
Loading

From #8494 (comment)

The failure (https://github.com/intel/llvm/actions/runs/4296187940) on

Timed Out Tests (1):
  SYCL-Unit :: scheduler/./SchedulerTests/17/19

TIMEOUT: SYCL-Unit :: scheduler/./SchedulerTests/17/19 (465 of 465)
******************** TEST 'SYCL-Unit :: scheduler/./SchedulerTests/17/19' FAILED ********************
Script(shard):
--
GTEST_OUTPUT=json:/__w/llvm/llvm/build/tools/sycl/unittests/scheduler/./SchedulerTests-SYCL-Unit-291055-17-19.json GTEST_SHUFFLE=0 GTEST_TOTAL_SHARDS=19 GTEST_SHARD_INDEX=17 /__w/llvm/llvm/build/tools/sycl/unittests/scheduler/./SchedulerTests
--

Note: This is test shard 18 of 19.
[==========] Running 2 tests from 2 test suites.
[----------] Global test environment set-up.
[----------] 1 test from SchedulerTest
[ RUN      ] SchedulerTest.QueueFlushing
[       OK ] SchedulerTest.QueueFlushing (0 ms)
[----------] 1 test from SchedulerTest (0 ms total)

[----------] 1 test from DependsOnTests
[ RUN      ] DependsOnTests.EnqueueNoMemObjDoubleKernelDepHost
[       OK ] DependsOnTests.EnqueueNoMemObjDoubleKernelDepHost (1 ms)
[----------] 1 test from DependsOnTests (1 ms total)

[----------] Global test environment tear-down
[==========] 2 tests from 2 test suites ran. (1 ms total)
[  PASSED  ] 2 tests.

--
exit: -9
--
Reached timeout of 600 seconds

can't be related but failing check-sycl results in llvm-test-suite not being run at all, so restarting the whole testing. Writing this comment so that a future github search on the test (if it will fail elsewhere sometime) would point to this run.
@aelovikov-intel aelovikov-intel added the bug Something isn't working label Feb 28, 2023
@aelovikov-intel
Copy link
Contributor Author

I haven't seen this for a long time. Also, CI has been refactored so that failing unittest won't prevent e2e from running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working confirmed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KornevNikita @aelovikov-intel
0