-
Notifications
You must be signed in to change notification settings - Fork 459
New issue
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
Fix DeviceId collision in LH and Stress tests #3028
Fix DeviceId collision in LH and Stress tests #3028
Conversation
…eIdCollisionLhNStress
scripts/linux/runE2ETest.sh
Outdated
@@ -698,7 +698,10 @@ function run_longhaul_test() { | |||
print_highlighted_message "Run Long Haul test for $image_architecture_label" | |||
test_setup | |||
|
|||
local device_id="$RELEASE_LABEL-Linux-$image_architecture_label-longhaul" | |||
# Import test-related functions | |||
. $(dirname "$0")/testHelper.sh |
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.
testHelper.sh is not in the same folder as runE2ETest.sh in the iotedge repo. It is in the same folder only in the artifact. To simplify, just clone that method and put a TODO to share.
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.
LGTM. Please create a PBI to clean up device for LH and stress test by a scheduled job, and share the link with Varun. thanks.
Update 1.0.9 to have unique device ID in LH and Stress tests Note: porting the changes from #3028 (master) to` release/1.0.9` branch
) Update 1.0.9 to have unique device ID in LH and Stress tests Note: porting the changes from Azure#3028 (master) to` release/1.0.9` branch
… put in master (#3166) * Update 1.0.9 to have unique device ID in LH and Stress tests (#3033) Update 1.0.9 to have unique device ID in LH and Stress tests Note: porting the changes from #3028 (master) to` release/1.0.9` branch * Phlin/edge agent get twin fix (#3075) When Edge agent calling GetTwinAsync method throws exception after retry policy, if the exception is not timeout exception it will trigger to close module client and retry again. * Upgrade Microsoft.Azure.Devices.Client from 1.23.1 to 1.23.2 (#3098) Upgrade Microsoft.Azure.Devices.Client NuGet package from 1.23.1 to 1.23.2, which contains AMQP Safely close fix. * Disable this test, same as what we did in master branch. (#3102) disable edge agent connection status test to fix CI build. This is already disabled in master branch and needs investigation from IoT hub team. * Allow environment variables to be empty or whitespace. (#2777) Environment variable values may be empty or whitespace. Docker allows these values for environment variable: "key1=" "key2= " * Add "(Kubernetes)" to ProductInfo. (#2811) * [k8s] Default Service protocol to "TCP" (#2929) If you create a module with Docker createOptions like so: ```json { "ExposedPorts":{ "35000":{} }, "HostConfig":{ "PortBindings":{ "35000":[{"HostPort":"35000"}] } } } ``` The Docker API will default the port to be "TCP". Therefore, the Docker->K8s translation should do the same. * [k8s] throw exception on watch error. (#2928) When we actually got an error from the watch, the watch stops and does not restart. Throw an error and let Agent recover from crash. * Fix unit test build. Co-authored-by: yophilav <54859653+yophilav@users.noreply.github.com> Co-authored-by: Philip Lin <philipktlin@live.com>
Fix DeviceId collision in LH and Stress tests