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)
Thank you for posting on the Intel® communities.
To better assist you, we have moved your question to another forum.
Intel Customer Support Technician
We are able to run the Basetool kit samples. Please follow the below steps for vector-add sample.
Connect to the Devcloud:
Currently you are in login node then connect to compute node :
Download the samples.
git clone https://github.com/oneapi-src/oneAPI-samples.git
Go to the vector-add sample
Build and run the sample in batch mode
Create the job scripts
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
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)
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.
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.