Skip to content

Replacement deprecated method #2079

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
Merged
merged 1 commit into from
Jul 22, 2020
Merged

Replacement deprecated method #2079

merged 1 commit into from
Jul 22, 2020

Conversation

MochalovaAn
Copy link
Contributor

368a5e3

Signed-off-by: amochalo [email protected]

@MochalovaAn MochalovaAn requested a review from bader as a code owner July 9, 2020 15:07
@bader
Copy link
Contributor

bader commented Jul 10, 2020

@romanovvlad, do you know if this is a known issue?
This failure doesn't seem to be related to the patch.

******************** TEST 'SYCL :: scheduler/DataMovement.cpp' FAILED ********************
Script:
--
: 'RUN: at line 1';   d:\buildbot\product_worker_intel\sycl-win-x64-pr\llvm.obj\bin\clang.exe --driver-mode=g++ -fsycl -fsycl-targets=spir64-unknown-linux-sycldevice -I D:/BuildBot/Product_worker_intel/sycl-win-x64-pr/llvm.src/sycl/source D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.src\sycl\test\scheduler\DataMovement.cpp -o D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out -g
: 'RUN: at line 2';   env SYCL_DEVICE_TYPE=CPU SYCL_BE=PI_OPENCL  D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out
: 'RUN: at line 3';    env SYCL_DEVICE_TYPE=GPU SYCL_BE=PI_OPENCL  D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out
: 'RUN: at line 4';   true D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out
--
Exit Code: 3221225477
Command Output (stdout):
--
$ ":" "RUN: at line 1"
$ "d:\buildbot\product_worker_intel\sycl-win-x64-pr\llvm.obj\bin\clang.exe" "--driver-mode=g++" "-fsycl" "-fsycl-targets=spir64-unknown-linux-sycldevice" "-I" "D:/BuildBot/Product_worker_intel/sycl-win-x64-pr/llvm.src/sycl/source" "D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.src\sycl\test\scheduler\DataMovement.cpp" "-o" "D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out" "-g"
$ ":" "RUN: at line 2"
$ "env" "SYCL_DEVICE_TYPE=CPU" "SYCL_BE=PI_OPENCL" "D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out"
$ ":" "RUN: at line 3"
$ "env" "SYCL_DEVICE_TYPE=GPU" "SYCL_BE=PI_OPENCL" "D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out"
note: command had no output on stdout or stderr
error: command failed with exit status: 3221225477
--
********************

@romanovvlad
Copy link
Contributor

@romanovvlad, do you know if this is a known issue?
This failure doesn't seem to be related to the patch.

******************** TEST 'SYCL :: scheduler/DataMovement.cpp' FAILED ********************
Script:
--
: 'RUN: at line 1';   d:\buildbot\product_worker_intel\sycl-win-x64-pr\llvm.obj\bin\clang.exe --driver-mode=g++ -fsycl -fsycl-targets=spir64-unknown-linux-sycldevice -I D:/BuildBot/Product_worker_intel/sycl-win-x64-pr/llvm.src/sycl/source D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.src\sycl\test\scheduler\DataMovement.cpp -o D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out -g
: 'RUN: at line 2';   env SYCL_DEVICE_TYPE=CPU SYCL_BE=PI_OPENCL  D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out
: 'RUN: at line 3';    env SYCL_DEVICE_TYPE=GPU SYCL_BE=PI_OPENCL  D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out
: 'RUN: at line 4';   true D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out
--
Exit Code: 3221225477
Command Output (stdout):
--
$ ":" "RUN: at line 1"
$ "d:\buildbot\product_worker_intel\sycl-win-x64-pr\llvm.obj\bin\clang.exe" "--driver-mode=g++" "-fsycl" "-fsycl-targets=spir64-unknown-linux-sycldevice" "-I" "D:/BuildBot/Product_worker_intel/sycl-win-x64-pr/llvm.src/sycl/source" "D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.src\sycl\test\scheduler\DataMovement.cpp" "-o" "D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out" "-g"
$ ":" "RUN: at line 2"
$ "env" "SYCL_DEVICE_TYPE=CPU" "SYCL_BE=PI_OPENCL" "D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out"
$ ":" "RUN: at line 3"
$ "env" "SYCL_DEVICE_TYPE=GPU" "SYCL_BE=PI_OPENCL" "D:\BuildBot\Product_worker_intel\sycl-win-x64-pr\llvm.obj\tools\sycl\test\scheduler\Output\DataMovement.cpp.tmp.out"
note: command had no output on stdout or stderr
error: command failed with exit status: 3221225477
--
********************

Haven't seen it before.

@romanovvlad romanovvlad merged commit 4cc1da1 into sycl Jul 22, 2020
@bader bader deleted the LowerDepr branch July 22, 2020 11:31
@sergey-semenov
Copy link
Contributor

The failure should be fixed by #2157

jsji pushed a commit that referenced this pull request Jul 17, 2023
@svenvh @sys-ce-bb
Update DebugInfo tests for op-index addition (#2079)
4c82652 
Update tests for llvm-project commit 6aa94c6 ("[DWARF] Add
printout for op-index", 2023-07-12).

Original commit:
KhronosGroup/SPIRV-LLVM-Translator@81ffaaf
jsji pushed a commit that referenced this pull request Aug 2, 2023
@svenvh @jsji
Update DebugInfo tests for op-index addition (#2079)
e932c8b 
Update tests for llvm-project commit 6aa94c6 ("[DWARF] Add
printout for op-index", 2023-07-12).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bader bader bader approved these changes

@againull againull againull approved these changes

@AlexeySachkov AlexeySachkov Awaiting requested review from AlexeySachkov

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@MochalovaAn @bader @romanovvlad @sergey-semenov @againull