Intel® DevCloud
Help for those needing help starting or connecting to the Intel® DevCloud
Announcements
The Intel sign-in experience has changed to support enhanced security controls. If you sign in, click here for more information.
1275 Discussions

Timeout in devcloud

amadou
Beginner
827 Views

Do you know why after using devcloud for a moment everyday then you cannot compile/run anything anymore and not just my code but all the codes of the training modules for oneAPI base toolkit  have this kind of output as well when you compile/run: "

TimeOut 60 seconds: Job is still queued for execution, check for output file later (run_buffer_destruction.sh.o1015610)

". 

0 Kudos
6 Replies
AdrianM_Intel
Moderator
817 Views

Hello amadou,


Thank you for posting on the Intel® communities. 


To better assist you, we have moved your question to another forum.


Regards,


Adrian M.

Intel Customer Support Technician 



JaideepK_Intel
Moderator
773 Views

Hi,

We are able to run the Basetool kit samples. Please follow the below steps for vector-add sample.

 

Connect to the Devcloud:

 

ssh devcloud

 

Currently you are in login node then connect to compute node :

 

qsub -I

 

Download the samples.

 

git clone https://github.com/oneapi-src/oneAPI-samples.git

 

Go to the vector-add sample

 

cd oneAPI-samples/DirectProgramming/DPC++/DenseLinearAlgebra/vector-add/

 

Build and run the sample in batch mode

Create the job scripts

 

vi build.sh

 

Paste the following contents in build.sh script

 

#!/bin/bash
source /opt/intel/inteloneapi/setvars.sh
make clean
make all

 

Create a run.sh script

 

vi run.sh

 

Paste the following contents in run.sh script

 

#!/bin/bash
source /opt/intel/inteloneapi/setvars.sh
make run

 

Build the sample on a gpu node.

 

qsub -l nodes=1:gpu:ppn=2 -d . build.sh

 

To inspect the job progress

 

watch -n 1 qstat -n -1

 

Run the sample on a gpu node after the build job completes successfully.

 

qsub -l nodes=1:gpu:ppn=2 -d . run.sh

 

After running the above command the out put is going to save in file (eg: run.sh.o1018851)

Note:

How to change job timeout (max = 24h)

By default, any jobs will be terminated automatically at the 6h mark. Use the following syntax if your job requires more than 6h to complete.

 

qsub -I -l walltime=hh:mm:ss

 

eg: qsub -I -l walltime=10:00:00

 

Please share your Devcloud id if you are facing same issue after running the above steps. 

 

Thanks,

Jaideep

 

 

 

JaideepK_Intel
Moderator
723 Views

Hi,


If this resolves your issue, make sure to accept this as a solution. This would help others with similar issue. Thank you!


Thanks,

Jaideep


JaideepK_Intel
Moderator
654 Views

Hi,


I assume that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.


Thanks,

Jaideep


RitaChu
Employee
582 Views

I also have this problem when using jupyter notebook.  

I try following the solution described above but I got stuck at ssh.  I waited and there is no response.

RitaChu
Employee
581 Views

oop! user error.  I can ssh now.  Please ignore my previous comment.

 

Reply