Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
H
HDL
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
RTSD
HDL
Commits
f0c76f4a
Commit
f0c76f4a
authored
3 months ago
by
Eric Kooistra
Browse files
Options
Downloads
Patches
Plain Diff
Add crontab list of regtest machine.
parent
0f636bec
Branches
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#103880
passed
3 months ago
Stage: linting
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/erko_howto_tools.txt
+35
-0
35 additions, 0 deletions
doc/erko_howto_tools.txt
with
35 additions
and
0 deletions
doc/erko_howto_tools.txt
+
35
−
0
View file @
f0c76f4a
...
@@ -1118,6 +1118,41 @@ crontab -e # edit schedule
...
@@ -1118,6 +1118,41 @@ crontab -e # edit schedule
tail -n 1000 unb2b_modelsim_regression_test_vhdl_cron.log
tail -n 1000 unb2b_modelsim_regression_test_vhdl_cron.log
regtest@dop349:~$ crontab -l
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').
#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
TERM=xterm-256color
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
SHELL=/bin/bash
#
# m h dom mon dow command
# vhdl regressiontest
0 18 * * 1-5 /home/regtest/git/radiohdl/regressiontest/modelsim_regression_test_vhdl_cron.sh /home/regtest/git/radiohdl/regressiontest/modelsim_buildset_list.txt > modelsim_cron.log 2>&1
# firmware regressiontest done on dop386 and connected arts uniboards
0 23 * * 0 /home/regtest/git/sdptr/regressiontest/fw_regressiontest.sh --remote-ip=10.87.0.186 --sdptr-ip=localhost --sdptr-port=4842 --sdptr --flash --rbf=latest --test --test-runs=5 --send-mail > fw_sdptr_cron.log 2>&1
# build images with quartus 1 18 * * 6
1 18 * * 6 /home/regtest/git/radiohdl/regressiontest/quartus_build_images_cron.sh /home/regtest/git/radiohdl/regressiontest/image_build_list.txt > quartus_cron.log 2>&1
*******************************************************************************
*******************************************************************************
* License server
* License server
*******************************************************************************
*******************************************************************************
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment