We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Describe your environment For example, when run ./ci/do_ci.sh cmake.maintainer.test on my local machine, it takes too much time to build from scratch.
./ci/do_ci.sh cmake.maintainer.test
Steps to reproduce run ./ci/do_ci.sh cmake.maintainer.test
What is the expected behavior? Target should be built with parallel option of make command if possible.
What is the actual behavior? Some of targets in CI pipeline does not have any parallel options which takes too much time to build from scratch.
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
We need to check if make -k works with -j.
make -k
-j
Sorry, something went wrong.
In my local environment, without parallel option it takes almost 9 minutes to build cmake.maintainer.test target.
cmake.maintainer.test
With help of parallel build mechanism, it takes only around 2 minutes to build. So, in my opinion it works.
Do you think that should we also run tests in parallel?
Successfully merging a pull request may close this issue.
Describe your environment For example, when run
./ci/do_ci.sh cmake.maintainer.test
on my local machine, it takes too much time to build from scratch.Steps to reproduce
run
./ci/do_ci.sh cmake.maintainer.test
What is the expected behavior?
Target should be built with parallel option of make command if possible.
What is the actual behavior?
Some of targets in CI pipeline does not have any parallel options which takes too much time to build from scratch.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: