-
Notifications
You must be signed in to change notification settings - Fork 601
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
tests: add external spread backend #1918
Changes from 1 commit
0ebb109
2e3c769
1717ec7
9d65377
bf6a27e
f7f4262
c36777f
af2a6fe
4730fc0
1c9d3eb
c96d078
9e59ea7
3f69cbc
7a350e0
20b0c89
1ad3d3b
62916e2
ac93668
7a0402b
426af6f
e926560
0ef8db1
8dd3470
e9decf3
317f5d1
a64280b
0792643
de059b4
bc9a45c
804382e
4afba8e
3ba99b3
46ca6fa
2e06506
1deddf0
16cf045
bdb32f1
570efbd
898add2
919b2c1
ed17fbf
0c20edd
c95e0c1
fffc48b
81875ed
3966250
8d2b9e8
7984751
83f7696
a716f4e
d87fbdc
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -65,6 +65,8 @@ backends: | |
ADDRESS $SPREAD_ADHOC_UC_ADDRESS:$SPREAD_ADHOC_UC_PORT | ||
discard: | | ||
echo "Discarding ad-hoc $SPREAD_SYSTEM" | ||
restore: | | ||
rm -rf $GOPATH/src | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why? It doesn't smell quite right. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Without this, when i try to run the suite again on the same instance after an execution i get:
If I try There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, there's a problem indeed. When you provide reuse, spread doesn't know which machine the address belongs to. It finds that out by connecting to it and reading the data it wrote there previously. If it cannot connect, it cannot read the data, and cannot tell how to connect. Oops. Let me think about that one. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Spread has been improved to support reuse properly and nicely with this case (and every other, actually). Please let me know how it goes @fgimenez. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Totally fine! Thanks :) I've removed that restore step. |
||
systems: | ||
- ubuntu-core-16.04-64: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What's the comment above about? This system is a bit awkward, as there's no such thing as an ubuntu-core-16.04. Happy to fix Spread if that's what the comment implies. Not sure about what's broken, though. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, we need changes in spread, currently if you have a backend with specific systems and there's one task that excludes all of them, then you get an error, for instance, if we remove the dummy system above and try to execute the suite you get:
The erroring task is different with each execution, probably related to the random ordering of tasks. Adding the dummy systems allow to execute the suite, There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see, thanks. Spread was fixed in snap and github. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks a lot, works great |
||
username: test | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,7 +9,6 @@ execute_remote(){ | |
ssh -q -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p $INSTANCE_PORT $USER@$INSTANCE_IP "$@" | ||
} | ||
|
||
execute_remote "sudo rm -rf /home/gopath/src" | ||
execute_remote "sudo adduser --extrausers --quiet --disabled-password --gecos '' test" | ||
execute_remote "(echo test:ubuntu | sudo chpasswd)" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No need for the extra subshell via There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You are right, the quotes are enough for managing the pipes properly, fixed |
||
execute_remote "(echo 'test ALL=(ALL) NOPASSWD:ALL' | sudo tee /etc/sudoers.d/create-user-test)" |
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 can be dropped as it's not doing anything.
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.
Done