Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
tnl-dev
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
TNL
tnl-dev
Commits
a911332c
There was an error fetching the commit references. Please try again later.
Commit
a911332c
authored
6 years ago
by
Jakub Klinkovský
Browse files
Options
Downloads
Patches
Plain Diff
CI: build using 8 threads on jlk again
parent
c5736dde
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab-ci.yml
+3
-3
3 additions, 3 deletions
.gitlab-ci.yml
with
3 additions
and
3 deletions
.gitlab-ci.yml
+
3
−
3
View file @
a911332c
...
...
@@ -37,9 +37,9 @@ stages:
export CC=mpicc;
fi
# all cores including hyperthreading
#
- export NUM_CORES=$(grep "core id" /proc/cpuinfo | wc -l)
#
# all pyhsical cores
-
export NUM_CORES=$(grep "core id" /proc/cpuinfo | sort -u | wc -l)
-
export NUM_CORES=$(grep "core id" /proc/cpuinfo | wc -l)
# all pyhsical cores
#
- export NUM_CORES=$(grep "core id" /proc/cpuinfo | sort -u | wc -l)
# ninja does not have -l
# - export MAKEFLAGS="-l$(echo 1.5*$NUM_CORES | bc) -j$NUM_CORES"
-
export NINJAFLAGS="-j$NUM_CORES"
...
...
This diff is collapsed.
Click to expand it.
Jakub Klinkovský
@klinkovsky
mentioned in commit
3d81c3aa
·
6 years ago
mentioned in commit
3d81c3aa
mentioned in commit 3d81c3aacd7b5dcd95c5ea0b0db9304a900e3559
Toggle commit list
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