-
Notifications
You must be signed in to change notification settings - Fork 95
Turnoff misleading error/warning messages #1554
Turnoff misleading error/warning messages #1554
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good. See a couple of minor points inside. Thanks for the fix !
Constants.mk
Outdated
# This Makefile's purpose is to hold common variables to reuse across | ||
# Makefiles for vDVS. | ||
|
||
export |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does 'export' here do
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
exporting all the variables resided in this file.
Constants.mk
Outdated
@@ -0,0 +1,78 @@ | |||
# Copyright 2016 VMware, Inc. All Rights Reserved. | |||
# |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not really constants. More.like vars
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct! My bad, I will rename it.
How about Commonvars.mk
or EnvVars.mk
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
commonvars sounds good. At any rate, this is minor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will push the change shortly to avoid future confusion with naming.
# developer builds use last tagged release and sha1 of the most recent commit. | ||
# Format: <last tagged release>.<last commit hash> | ||
PKG_VERSION ?= $(shell \ | ||
git describe --tags `git rev-list --tags --max-count=1` \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not used anymore , right ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is being referred from Constants.mk
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you mean set in
? Yes, I see it now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah!
dc2f849
to
49f2190
Compare
Constants.mk
Outdated
# developer builds use last tagged release and sha1 of the most recent commit. | ||
# Format: <last tagged release>.<last commit hash> | ||
PKG_VERSION ?= $(shell \ | ||
git describe --tags `git rev-list --tags --max-count=1` \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it uses git so I think it may fail exactly the same GIT_SHA calculation used to fail during managed plugin build unless it is pre-defened from upstairs. Please check the logs.
# developer builds use last tagged release and sha1 of the most recent commit. | ||
# Format: <last tagged release>.<last commit hash> | ||
PKG_VERSION ?= $(shell \ | ||
git describe --tags `git rev-list --tags --max-count=1` \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you mean set in
? Yes, I see it now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Actually,
I take the "approval" back. Per CI, (1) the managed plugin make
is broken, and (2) CI itself ignores serious error in plugin build:
(1)
rm -f
docker plugin rm : -f
Error response from daemon: plugin ":" not found
make: [clean] Error 1 (ignored)
Makefile:51: recipe for target 'clean' failed
docker rm -vf tempContainer
Error response from daemon: No such container: tempContainer
make: [clean] Error 1 (ignored)
Error response from daemon: invalid reference format
make: [clean] Error 1 (ignored)
cp: omitting directory '/'
make: *** [plugin] Error 1
Makefile:51: recipe for target 'clean' failed
docker rmi :rootfs
Makefile:51: recipe for target 'clean' failed
== building Docker image, unpacking to ./rootfs and creating plugin...
cp / .
Makefile:59: recipe for target 'plugin' failed
plugin_sanity_test: [INFO] Running plugin_sanity_test on the clean test setup...
plugin_sanity_test: [INFO] Installed plugin name is:
plugin_sanity_test: [ERROR] error has occurred while fetching created plugin name..
please make sure plugin is built correctly or not
Pushing : to dockerhub.io...
invalid reference format
- despite the above, the CI did not stop and did not report error
Thanks @msterin! For (1) I have a local fix (missed a commit) and waiting for the file rename to push new commit. Sure I will for (2) I need to investigate why
|
49f2190
to
6d39c67
Compare
6d39c67
to
4269c19
Compare
fixes #1356
This PR cleans up following misleading error/warning message from CI test run.
warning: overriding commands for target
clean'`Not a git repository (or any of the parent directories): .git
when theVERSION_TAG
is set no need to invoke remote call to fetchGIT_SHA
orGIT_TAG
.. in case of vm on the CI where repo is not checked out; it prints such fatal message that creates some distraction while debugging the failure.e.g. https://ci.vmware.run/vmware/docker-volume-vsphere/949
Testing done: yes
CI output https://ci.vmware.run/vmware/docker-volume-vsphere/968
/CC @msterin